...

2023-10-10

...

Recording: TODO

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on 2023-09-26
      
      1. https://gerrit

...

1. 1. 1. .o-ran-sc.org

...

1. 1. 1. /r/c/ric-plt/alarm-go/+/11149 OK, go version update only
      2. https://gerrit.o-ran-sc

...

1. 1. 1. .org/r/c/ric-plt/lib/rmr/+/11234 OK, test case added for IPv6 tests

1. 1. 1. https://gerrit.o-ran-sc.org/r/

...

1. 1. 1. c/

...

1. 1. 1. ric-plt/

...

1. 1. 1. a1/+/11324 PK, test case updated
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11733 OK, generated code from API
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-05-23:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
   2. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   3. RIC-1001 RMR service should verify route tables - Alexandre will take a look
   4. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
   5. RIC-989 RMR (minor) security issue - Alexandre will take a look
   6. RIC-972 (Naman) URL for A1 mediator to align with spec.
   7. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   8. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   9. RIC-915 dms_cli for installing xapp not working (raised by James)
   10. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   11. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   12. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   13. RIC-894 long idle period (days) causes RMR connection breaks
   14. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   15. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   16. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
       1. 2021-12-21: Trying to get bandwidth for this during F release.
   17. RIC-837 RMR is not forwarding messages from E2T to E2M
   18. RIC-835 → 2021-12-07 no news from Viktor
   19. fixed: RIC-1011, RIC-979
4. James: updates?
   1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
   2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
      1. ODU-high and near-RT RIC (currently using stub).
      2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
      3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
      4. James will check with Sunil on issues he has with the test cases
      5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar coudl be done with OSC.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26 : could not participate
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-08-29: no news, other than Naman working on the operator implementation.
   2. 2023-09-12:
      1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
      2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
         1. Thoralf sent instructions to John → DONE
      3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
      4. Naman also works on the operator implementation
   3. 2023-09-26:
      
      1. kubernetes operator new repo needed or not?
         1. xapp deployment → appmgr or ricdms
         2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
      2. What happened to kserve adapter? → Subhash can check.
8. Abhijit updates (subteam-ag) ?
   1. 2023-08-22: next release item discussed and RIC-979
   2. 2023-08-29:
      1. created RIC-1004 for release I item.
      2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
         1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
   3. 2023-09-12:
      1. changes related to registration API needed in xapp-frame (problem still to be thought of)
      2. something not working in github: IT-25974 - again related to github replication.
   4. 2023-09-26
      1. Abhijit presented his work on a single near RT RIC helm chart and bringing up the platform on minikube on Ubuntu 22.04. We decided to proceed with this.
         
      2. github action problem with master vs g release for replication → ticket.
      3. Abhijit wanted to provide a video for new way of ric deployment
   5. 2023-10-10:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0
9. Cap Gemini updates (subteam-cg)? 
   1. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
      
      1. Ashish S. (CapGemini) presented this.
      2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
         
         1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
         2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
         3. additional latency comes only from guidance request
         4. xapp-framework could be extended to automatically do E2 guidance requests
   2. 2023-09-26:
      1. first step of new repo created, but still issues with initial files in repo. Thoralf raised request to LF: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26015 
   3. 2023-10-10:
      1. conflictmgr repo is now ready for commits: https://gerrit.o-ran-sc.org/r/admin/repos/ric-plt/conflictmgr,general
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
11. Dhiraj (subteam-r)
    
    1. 2023-08-22:
       1. checking compliance/license issues
       2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
    2. 2023-08-29:
       1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes
12. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
13. Nokia (subteam-n)
    1. Thoralf on holiday on Oct-10. Sunil?
14. I release content

1. 1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
   2. input for release candidates: left overs and generally open items, RSAC
   3. Sprint dates
      1. Sprint I release dev sprint 1: Aug-21 to Sep-10
      2. Sprint I release dev sprint 2: Sep-11 to Oct-1
      3. Sprint I release dev sprint 3: Oct-2 to Oct-22
      4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
   4. Plan (v03 as of 2023-08-18):
      1. I release plan moved to I release page.
2. RICAPP agenda: RICAPP Meetings.

2023-09-26

Recording: link to zoom recording

...