Page History

...

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-02-28
      
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/10666 OK
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/10287 OK
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10405 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
         1. 2023-02-28: Abhijit worked with Matt and Sridhar from LF on this. Jobs are now running, but they fail. There's a credential issue. Abhijit to remind Sridhar. Once this is fixed, we can change Dockerfile to install prerequisites.
         2. 2023-03-28: OK?This is OK and is now closed.
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 2022-05-27, 2022-11-22, 2023-03-28:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link

   1. new bug report RIC-962

   2. RIC-961 (fixed already)

   3. RIC-964 (fixed already)

   4. RIC_966 (fixed already)

   5. RIC-968 (fixed already)

   6. RIC-940 sdlpy missing whitespace → Timo
   7. RIC-939 race conditions in RMR → Abdulwahid
   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-897 SCTP connection fails with Viavi // update with workaround
   13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   14. RIC-894 long idle period (days) causes RMR connection breaks
   15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   17. 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.
   18. RIC-837 RMR is not forwarding messages from E2T to E2M
   19. RIC-835 → 2021-12-07 news from Viktor
   20. fixed: no new fixes
       
   21. anybody would like to get more familiar with RMR?

4. 2022-12-13, 2023-01-17: Bin Yang asked about O2 for RIC platform deployment and xapp deployment. Need to discuss on this topic. O-cloud is deployed in AT&T and Taiwan lab.

   1. The current platform deployment scripts might not be in line with O2 envisions
   2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
   3. O2-D(MS) is relevant to RIC platform.
   4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
   5. 2023-01-31: No news yet
   6. 2023-02-14 No news yet, Thoralf received e-mail on this from James. Still to check.
   7. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
   8. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.
   9. 2023-03-28: no news
5. James:updates?
   1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
         1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
         2. Tacker-based deployment needs to be checked.
   2. 2023-03-14, 2023-03-28: : no news
6. Sunil updates?
   1. 2023-03-14, 2023-03-28: : no news
7. Subhash/Naman updates?
   1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
      
      1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
         1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
            1. Thoralf to create JIRA item for this
            2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
            3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
            4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
         2. Integration with AI/ML project: kserve_adapter
            1. data pipeline (Hoejoo's e-mail)
               1. 2023-01-31 not discussed in today's meeting
   2. 2023-03-14:
      1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
      2. A1 mediator nanobot integration still under work.
   3. 2023-03-28: work continues
      
8. Abhijit updates?
   1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
      1. Thoralf raised support request to LF. Reminders sent. Still no solution.
   2. 2023-03-14:now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.
      
   3. 2023-03-28: working on RIC-969 and part of RIC-957
9. Cap Gemini updates?
   1. 2023-03-14
      1. RIC-851 done
      2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.
   2. 2023-03-28: no news.
10. H release content
    
    1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H 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. Sprint dates
       1. Sprint H release dev sprint 1: Feb-20´to Mar-12
       2. Sprint H release dev sprint 2: Mar-13 to Apr-2
       3. Sprint H release dev sprint 3: Apr-3 to Apr-23
       4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
       5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
11. GRPC vs RMR
    1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14, 2023-03-28 : no update
    Integration with AI/ML project: kserve_adapter
    1. data pipeline (Hoejoo's e-mail)2023-01-31 not discussed in today's meeting
12. RICAPP agenda: RICAPP Meetings.

...