...

RIC project meetings are open to the public and held on Tuesdays at 2pm UTC (winter) and 1pm UTC (summer).  World Time Zone Map

Zoom 1 Info:

...

...

2024-

...

04-

...

23

Recording: link to zoom recording zoom link

1. Anybody new who wants to introduce him/herself?
   1. LoreLei - PlugFests, RIC in PowderLab, proof of concept - AT&T
   2. Yasmin, Joyce, Mirette - Dell
   3. Wasi, Nitin, Praneeth - Mavenir
   4. David Allabaugh - Fujitsu - WG-10 - info modelling
2. 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 (end of I release)
      1. TODO
      ...
3. 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)
   ...
   1. Anybody willing to work on them?Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
4. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-836 → Done1057gNB unable to connect during high amount of Subscription Requests
   2. RIC-8371056Crashing e2mgr after sending high amount of Subscription Requests
   3. RIC-840
5. Action items
   1. SCCL update - Matti will check with Tracy
   2. RIC tester: Wiki page updated but no word from Nokia - trying 100 subscriptions - testing still in progress, will check with Amit if bug has been filed (nokia waiting for test case being run in newer cloud environment)
   3. James (INT PTL): Sent email to PTLs on what is needed. Need automation of testing for all projects.
6. Thoralf recorded a 24min step-by-step video on how to deploy the Dawn release: 2021-11-05 Demo video release Dawn
7. Preliminary planning for the F release
   1. likely not completed in E release (spill over into F): RIC-647
8. Do we update to golang 1.16 (in go.mod) in all repos? Juha now updated golang version in Ubuntu base image along with Ubuntu image update to 20.04.
   1. A1-Med is using 1.16; others need to be checked
9. RICAPP agenda: RICAPP Meetings.

2021-10-26

Recording: link to zoom recording

1. Note that originally we wanted to do some preliminary planning for the F release, but I did not have time to prepare for this, So we can handle this only on Nov-9
2. Anybody new who wants to introduce him/herself?
   1. LoreLei - PlugFests, RIC in PowderLab, proof of concept - AT&T
   2. Yasmin, Joyce, Mirette - Dell
   3. Wasi, Nitin, Praneeth - Mavenir
   4. David Allabaugh - Fujitsu - WG-10 - info modelling
3. 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. ...
4. 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. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   ...
   1. Anybody willing to work on them?
5. Every time: Check if there are new bug reports in JIRA: link
   1. no new items
6. Do we update to golang 1.16 (in go.mod) in all repos? Juha now updated golang version in Ubuntu base image along with Ubuntu image update to 20.04.
   1. A1-Med is using 1.16; others need to be checked
7. Subhash:
   1. RIC-CTL repo created, RIC-DMS repo created for O2 related interfaces; no blockers
   2. SCCL update - Matti will check with Tracy
8. RIC tester: Wiki page updated but no word from Nokia - trying 100 subscriptions - testing still in progress, will check with Amit if bug has been filed.
9. Nitin: Can RIC be installed on anything but Ubuntu? See ric-dep folder.
10. James (INT PTL): Sent email to PTLs on what is needed. Need automation of testing for all projects.
11. RICAPP agenda: RICAPP Meetings.

2021-10-12

Recording: link to zoom recording

1. Anybody new who wants to introduce him/herself (michel p (from NU working with Mavenir))
2. 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. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6795 ok
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6806 ok
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6807 ok
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/6705 ok
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/6810 ok
   6. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6814 ok
   7. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/6832 ok
3. 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. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. ric-plt/alarm-go 0,0 // no bugs (2021-01-31 → 2021-09-30)
   4. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31 → 2021-09-30)
   5. ric-plt/e2mgr 88,0 // no bugs (2021-01-30 → 2021-09-28)
   6. ric-plt/sdlgo 47,4 // no bugs (2021-09-28 → 2021-09-30)
   7. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31 → 2021-09-30)
   8. ric-plt/submgr 33,4 → 44,8 // no bugs (2021-01-31 → 2021-09-30 (fail) )
   9. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31 → 2021-09-30)
   10. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31 → 2021-09-30 (fail)) - same as before.
   11. Anybody willing to work on them?
4. Every time: Check if there are new bug reports in JIRA: link
   1. no new items
5. A reminder related to the visibility of LF IT support requests: "If you raise issues to LF support that are sensible to make visible to others, pls. first raise a ticket to join "ORAN" organization in the support tool: "When these organizations (ORAN) were created in the beginning, we added by default all members from the committer groups into the organization. If at that time a particular user was not part of any group or just joined the community, then they will not be automatically added into the oran organization. Going forward, the new user will need to create a support ticket to be added to the organization."
6. https://gerrit.o-ran-sc.org/r/admin/repos/ric-plt/ricctl now exists. Also added in Scope of the near-RT RIC platform and its components (summary)
7. F release is coming. Need to start some planning on F release. Anything you would like to work on? Anything we should be working on. Let's do a bit of planning in the meeting two weeks from now.
8. Subhash: shared updates from Samsung
   
   1. E2APv1.1 using simulator from sim/... This project also requires some cleanup. Ron Shacham 
      1. there are more changes coming in this simulator area (not further elaborated here)
      2. let's come back to this in F release planning
   2. A1 reimplementation. A1-P one read-like ifc now ported. Rest of work still remaining.
   3. O2 (dmscli). Thoralf to schedule meeting for Thursday.
   4. ricctl repo exists. work can start.
9. Alexandre raised RIC-826
   1. thoralf to double-check ric-dep using helm3.
   2. original bug in RIC-826 was acatully fixed and conifirmed by Alexandre. Thoralf to clsoe.
   3. Alexandre to write e-mail to Thoralf about the local image problem.
10. SCCL: https://www.o-ran.org/sccl
11. Post-meeting there was a discussion on a new xApp with Mavenir and various others: link
12. RICAPP agenda: RICAPP Meetings.

2021-09-28

Recording: link to zoom recording

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. https://gerrit.o-ran-sc.org/r/c/ric-plt/vespamgr/+/6638 ok, only counter definitions.
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6704 ok
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6712 ok, Thoralf asked authors for more info. Feedback: The change is done for sdltool that is used for testing (robot testing etc.). We do not have any unit tests for this test tool in "src/cli/*"
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/6705 ok
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6766 ok
2. Skipped today: 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. Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Only a few components where code coverage reports work:

   4. ric-plt/e2mgr 88,4 → 88,0 // no bugs (2021-01-30 → 2021-09-28) there was a minor code addition

   5. ric-plt/lib/rmr 86,1 // no bugs (2021-08-17 → 2021-09-07)

   6. ric-plt/sdlgo 45,5 → 47,4 // no bugs (2021-02-01 → 2021-09-28)

   7. ric-plt/xapp-frame-cpp 95,6 // still 2 blocker bugs (2021-08-04 → 2021-09-22) - same as before. Anybody willing to work on them?

3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-828 (some security issue in DBAAS container)  → already fixed.
   2. RIC-830 (raised by Subhash after discussion): unless someone has an idea how to do auto-tagging for go modules that are in the same repo, Thoralf suggests to close this as "not fixed" and we continue with manual labelling of each module.
4. discuss RIC-184 and why we still have helm2 as in RIC-826. To me it seems RIC should be deployed using helm3, but Nune, for example says still, "You should use helm3 only for xApp deployment. For the deployment of platform components, you still need to use helm2".
   1. old report (checked already two weeks ago): RIC-826 discusses issue around helm3 usage in app manager. Anybody volunteering (HCL?) to check  if we still have helm2 instructed somewhere in it/dep or ric-plt/ric-dep?
   2. Sunil & Sangeetha to check if we still have any helm2 references in code or in wiki pages for Dawn.
   3. Onboarding (provided by xApp manager) is already using helm3, but the helm2 question is about deploying the base RIC platform.
5. E2 simulator? Which we is still maintained:
   

   1. https://gerrit.o-ran-sc.org/r/gitweb?p=sim%2Fe2-interface.git;a=summary

      1. originally developed by AT&T and managed by Alex. Not sure if V... is still maintaining.

   2. https://gerrit.o-ran-sc.org/r/gitweb?p=it/test.git;a=blob;f=ric_benchmarking/e2-interface/e2sim/src/ASN1c/E2AP-PDU.h

      1. used by HCL for e2sim deployment and bouncer xapp communication. Here the version which we are using in E2AP-PDU.h is E2APv1.01 (ok to use).

   3. https://gerrit.o-ran-sc.org/r/gitweb?p=it/test.git;a=blob;f=simulators/e2sim/ASN1c/E2AP-PDU.h

   4. Summary Ask Alex to continue supporting/working in sim repo's e2 simulator. The other one that should be continued is it/test's ric_benchmarking (as it works wityh bouncer xApp). (b) was taken from (a) and further enhanced.
   5. Summary Delete the simulator in it/test's simulators/e2sim subdirectory. Thoralf to file a JIRA case for this towards the infra project. Thoralf filed: INT-144
6. HCL needs access to it/test (still open, Sunil to check)
7. Samsung items
   
   1. RIC-653 A1 image in deplooyment is now updated.
   2. RIC-812 thoralf to mark thjis item as dropped from E release
   3. RIC-647 needs to have UTR from the beginning
   4. RIC-445 new repo is requested from TOC: "ricctl"
   5. RIC-714 Subhash to schedule meeting with Nune (=Abukar) and Thoralf
8. SDRAN (ONF) implementation now is open-sourcing the 1.1 version. If there's re-use potential (e.g. in simulator), let's do that.
9. RICAPP agenda: RICAPP Meetings.

2021-09-14

1. 1. 1055Unrestricted Registration of RMR Routing Information by xApp
   2. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation
   3. RIC-1052 Not able to install k8s and helm with Existing Ric installation shell script in document - Done, still some issues are seen, to further check and report issue.
   4. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
   5. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04 - To be assigned to Sunil, duplicate of 1052(DONE)
      
   6. RIC-1047 crash in E2T metric increment code - WIP
   7. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   8. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   9. RIC-1043 Crash in E2T buildPrometheusList Function  - WIP
   10. RIC-1042 Can't register xApp
   11. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation - Mostly fixed, To be confirmed by Abhijit.
   12. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   13. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   14. RIC-1025 memory leak in routing manager
   15. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   16. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   17. RIC-1015 e2t too High default message size. → Nokia

   18. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   19. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   20. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   21. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   22. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   23. 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)
   24. RIC-915 dms_cli for installing xapp not working (raised by James)
   25. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   26. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   27. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   28. RIC-894 long idle period (days) causes RMR connection breaks
   29. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   30. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   31. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   32. RIC-837 RMR is not forwarding messages from E2T to E2M
   33. RIC-835 → 2021-12-07 no news from Viktor
   34. fixed: 
       
2. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
   5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
   6. 2024-03-26: Unavailable today.
   7. 2024-04-23:
3. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09,2024-04-23: no news
4. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
   8. 2024-03-12: Implementation completed, facing issues in code submission.
   9. 2024-03-26: Working on RIC-1049, documentation will also be made - Done
      
   10. 2024-03-09: Absent
   11. 2024-04-23: Not much updates.
       
5. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
   4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
   5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
   6. 2024-03-09,2024-04-23: Not available
6. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      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 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
   4. 2024-03-12: No news.
   5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
   6. 2024-03-09: Not available.
      
   7. 2024-03-23: Interested to work on 1056,1057 in coming weeks, after rust framework is tested. RIC-1006 done, RIC-1007 move to K, RIC-1028- will be taken up next. To give demo on rust-framework 07-05-2024.
7. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
   3. 2024-03-26,2024-03-09,2024-04-23: unavailable.
8. Himanshu (subteam-gs) would like to work on RIC-963
   
   1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
   2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
   3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
   4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
   5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
   6. 2024-04-23: Not present
9. Dhiraj (subteam-r)
   
   1. 2023-12-05: moved the IPv6 item  to J release
   2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
   3. 2024-01-26,2024-04-09,2024-04-23: no news.
10. 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
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09,2024-04-23: No news.
11. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
12. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
13. J release
    
    1. 2024-02-13: Naman's input
       1. no Jira tickets yet, but woudl like to focus on 
          1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
       1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J 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.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link,  to include k8s version upgrade, clean up of pending issues.
14. 1. input for release candidates: leftovers and generally open items, RSAC
    2. Sprint dates
       1. Sprint J release dev sprint 1: Feb-19 to Mar-10
       2. Sprint J release dev sprint 2: Mar-11 to Mar-31
       3. Sprint J release dev sprint 3: Apr-1 to Apr-21
       4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
       5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
15. RICAPP agenda: RICAPP Meetings.

2024-04-09

Recording: near_rt_ric_09_04-2024.mp4Recording: link to zoom recording

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. (Thoralf checked on 2021-09-10 no large commits)
   2. Last checked on (end of I release)
      1. TODO
2. Skipped today: 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. Not done this time The list below is only working reports // anybody 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-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. old report RIC-826 discusses issue around helm3 usage in app manager. Anybody volunteering (HCL?) to check  if we still have helm2 instructed somewhere in it/dep or ric-plt/ric-dep?
   2. (Thoralf checked on 2021-09-10 no new items)
4. Nokia had to move O1-related JIRA items to post-E release: RIC-655, RIC-656, RIC-497 and RIC-798. Also there are still legal issues around the copyright of definitions from 3GPP specs that are needed when implementing O1.
5. Subhash:
   1. RIC-653: A1 Mediator image old - has been corrected. Another issue with helm - has also been resolved. Needs to be reviewed. Somebody from Nokia need to update RIC deployment.
   2. New repo requested for RIC CLI - still pending Thoralf. A1 Mediator go version will use the existing repo (replacing python version)
   3. Naman pushed an update to python xapp framework - under review.
6. HCL:
   1. Continue on RIC benchmarking.
7. Can we share ONeS slides to Subhash now?
8. RICAPP agenda: RICAPP Meetings.

2021-08-31

Exceptionally, we did not have a meeting today.

2021-08-17

Recording: link to zoom recording

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. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6584  OK
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/6551 OK (move of implementation from one repo to another)
2. Skipped today: 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
      1. ric-plt/a1 85,3 // no bugs (2021-01-26)

      1. ric-plt/alarm-go 0,0 // no bugs (2021-01-31)

      2. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31)

      3. ric-plt/asn1-documents not applicable

      4. ric-plt/dbaas 0,0 // 2 blocker bugs in UT code (2021-01-27) - seems not to be anymore in latest version of source code.

      5. ric-plt/e2 0,0 // 2 blocker bugs (2021-06-18) - Thoralf raised RIC-802 and send e-mail to Dhiraj, Subhash and Naman. 2021-08-17: RIC-802 is for subteam-n in E. No other news

      6. ric-plt/e2mgr 88,4 // no bugs (2021-01-30)

      7. ric-plt/lib/rmr 86,1 // no bugs (2021-08-17)

      8. ric-plt/rtmgr 77,8 // no bugs (2021-01-31)

      9. ric-plt/sdl  66,6 // 1 minor vulnerability bug (2021-01-29)

      10. ric-plt/sdlgo 45,5 // no bugs (2021-02-01)

      11. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31)

      12. ric-plt/submgr 33,4 // no bugs (2021-01-31)

      13. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-08-10)

      14. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31)

      15. ric-plt/vespamgr 79,0 // no bugs (2020-12-07)

      16. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31)

      17. ric-plt/xapp-frame-cpp 95,6 // still 2 blocker bugs (2021-08-04) - same as before. Anybody willing to work on them?

      18. ric-plt/xapp-frame-py 96,3 // 0 blocker bugs (2021-01-26)

      19. com/golog 80,7 // no bugs (2021-01-31)
      20. com/log 73,5 // 1 blocker bug and 8 minor ones (2021-01-27) - same as before. Need to fix Sonarcube issues (with Java version) first.
      21. com/pylog 33,7 // 11 major and minor bugs (2021-01-26)
3. Every time: Check if there are new bug reports in JIRA: link
   1. new: RIC-826 (discussion ongoing)
4. Note the presentation slides and video from "Open Source Conference 2021 (5G, IoT and Edge Computing) (organized by the IEEE ComSoc Bangalore chapter and Samsung SOSCON" is now available here: Overall architecture (not component-specific)
5. E2-related specs are now in IPR approval phase on O-RAN alliance side (O-RAN alliance member only access):

   1. O-RAN.WG3.UCR-v01.00: https://oranalliance.atlassian.net/wiki/download/attachments/2068513840/O-RAN.WG3.UCR-v01.00.docx?api=v2

   2. O-RAN.WG3.E2GAP-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/213254315/O-RAN.WG3.E2GAP-v02.00.docx?api=v2

   3. O-RAN.WG3.E2AP-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/226295809/O-RAN.WG3.E2AP-v02.00.docx?api=v2

   4. O-RAN.WG3.E2SM-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/244318246/O-RAN.WG3.E2SM-v02.00.docx?api=v2

   5. O-RAN.WG3.E2SM-KPM-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/244318246/O-RAN.WG3.E2SM-KPM-v02.00.docx?api=v2

   6. O-RAN.WG3.E2SM-RC-v01.00 https://oranalliance.atlassian.net/wiki/download/attachments/244318246/O-RAN.WG3.E2SM-RC-v01.00.docx?api=v2

6. E release "committed" content: link
7. Design or coordination aspects of some items of the E release
   1. RIC-638 config transfer E2APv1.1 (Subhash)
   2. RIC-445 CLI (demo from subhash as well)
   3. NOT today: RIC-80 and RIC-796 (REST interface for subscriptions only) (Possibly Anssi)
   4. RIC-809 subscription interface (Supreeth)
   5. RIC-805 We are likely moving the "remove old API part" only in the next release, i.e., maintain old and new in parallel for one release. Team needs some more discussion before something can be presented. Namespace in new implementation is given as part of each get/set method. Previously the namespace was given during SDK initialization. During E release we will only deprecate the old interface, but keep it. Only in F release we will remove.
   6. Mavenir thinking about gRPC as communication mechanism (Matti to send e-mail address to Thoralf).
      1. probably for next meeting due to holiday
   7. Discuss disaggregated VES agent use case and impact on RIC. Thoralf
      1. This is O-RAN O1 release 6 work (July-Dec 2021). Thoralf understands it introduces a "VES proxy agent" into the Edge CloudInfra that on the left gets VES events from CNFs (e.g., via REST events, or (the new thing) a CloudInfra Kafka instance) and on the right side forwards these to the SMO (e.g., directly into Kafka). Not sure if left-side injection can also be done via O1 websocket performance data streaming.
      2. There might be some issues around data schema alignment that need to be addressed
      3. Anyway, from CNF point of view seems to be one more way of sending statistics/metrics out towards the SMO. For now let's focus on existing O1 (files or websocket streaming) means. Also note that statistics are currently collected via Prometheus. I.e., if, we'd be talking about a new or update mediator component that takes the data from Prometheus and sends it to that new "VES proxy agent".
      4. Note that performance related there are also activities under the Prometheus umbrella that might be relevant, e.g., https://openmetrics.io/
      5. So this seems not to be relevant for the E release of near-RT RIC.
8. ...
9. RICAPP agenda: RICAPP Meetings.

2021-08-03

Recording: link to zoom recording

1. Skipped today: 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).
2. Skipped today: 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
3. Every time: Check if there are new bug reports in JIRA: link
4. E release timeline: Releases and see §6 in Jira usage conventions
   1. Sprint E release dev sprint 1: Aug-23 to Sep-12

   2. Sprint E release dev sprint 2: Sep-13 to Oct-3

   3. Sprint E release dev sprint 3: Oct-4 to Oct-24

   4. Sprint E release dev sprint 3: Oct-25 to Nov-14 (last planned development sprint)

   5. Sprint E release dev sprint 5: Nov-15 to Dec-3 (only for unplanned last-minute development items)

5. E release planning
6. ...
7. RICAPP agenda: RICAPP Meetings.

2021-07-20 no meeting

2021-07-06

Recording: link to zoom recording

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. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/4880 OK
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/6395 OK
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/6301 OK as helm chart adaptations that just did some same renaming in many files.
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/6447 OK
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
3. New item for every meeting: check if there are new bug reports in JIRA: link
4. Dawn release criteria checklist filled in: Release criteria checklist - Release D

5. Sonarcube jobs are failing because of the same issue it seems (grep for ERROR): https://jenkins.o-ran-sc.org/view/com-log/job/com-log-autotools-sonarqube/55/ and   https://jenkins.o-ran-sc.org/view/ric-plt-e2mgr/job/ric-plt-e2mgr-sonar-prescan-script/ and many more. Chaitanya raised https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22326 for this. It's related to opensdk. No fix yet available, but ideas what to do.

   1. Sunil will check with Chaitanya and Alok
6. thoralf on holiday, matti as well. No meeting in two weeks from now. And next meeting first week of August: On Aug-3.
7. Release E planning. Thoralf to send e-mail as kick-off.
8. RICAPP agenda: RICAPP Meetings.

2021-06-22

1. 1. RIC-1057 gNB unable to connect during high amount of Subscription Requests
   2. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests
   3. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
   4. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation
   5. RIC-1052 Not able to install k8s and helm with Existing Ric installation shell script in document
   6. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
   7. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04 - To be assigned to Sunil
   8. RIC-1047 crash in E2T metric increment code 
   9. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   10. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   11. RIC-1043 Crash in E2T buildPrometheusList Function 
   12. RIC-1042 Can't register xApp
   13. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   14. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   15. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   16. RIC-1025 memory leak in routing manager
   17. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   18. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   19. RIC-1015 e2t too High default message size. → Nokia

   20. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   21. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   22. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   23. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   24. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   25. 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)
   26. RIC-915 dms_cli for installing xapp not working (raised by James)
   27. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   28. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   29. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   30. RIC-894 long idle period (days) causes RMR connection breaks
   31. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   32. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   33. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   34. RIC-837 RMR is not forwarding messages from E2T to E2M
   35. RIC-835 → 2021-12-07 no news from Viktor
   36. fixed: 
       
2. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
   5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
   6. 2024-03-26: Unavailable today.
3. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09: no news
4. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
   8. 2024-03-12: Implementation completed, facing issues in code submission.
   9. 2024-03-26: Working on RIC-1049, documentation will also be made.
   10. 2024-03-09: Absent
5. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
   4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
   5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
   6. 2024-03-09: Not available
6. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      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 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
   4. 2024-03-12: No news.
   5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
   6. 2024-03-09: Not available.
      
7. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
   3. 2024-03-26,2024-03-09: unavailable.
8. Himanshu (subteam-gs) would like to work on RIC-963
   
   1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
   2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
   3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
   4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
   5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
9. Dhiraj (subteam-r)
   
   1. 2023-12-05: moved the IPv6 item  to J release
   2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
   3. 2024-01-26,2024-04-09: no news.
10. 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
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09: No news.
11. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
12. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
13. J release
    
    1. 2024-02-13: Naman's input
       1. no Jira tickets yet, but woudl like to focus on 
          1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
       1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J 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.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link
14. 1. input for release candidates: leftovers and generally open items, RSAC
    2. Sprint dates
       1. Sprint J release dev sprint 1: Feb-19 to Mar-10
       2. Sprint J release dev sprint 2: Mar-11 to Mar-31
       3. Sprint J release dev sprint 3: Apr-1 to Apr-21
       4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
       5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
15. RICAPP agenda: RICAPP Meetings.

2024-03-26

Recording:  link to zoom Recording: link to zoom recording

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. https://gerrit.o-ran-sc.org/r/c/com/asn1c/+/6266 OK
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6132 OK
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6134 OK
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6128 OK
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6014 OK
   6. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6157 OK (existing test case was updated with new attributes)
   7. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlpy/+/6060 OK
   8. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6167 OK
   9. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/6183 OK
   10. https://gerrit.o-ran-sc.org/r/c/ric-plt/libe2ap/+/6131 OK (as per meeting minutes from 2021-05-25)
   11. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/6199 OK (all code copied from other place into 3rdparty subdir)
   12. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/6237 OK (removal)
   13. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6241 OK (test case was adapted to change in data type)
   14. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6242 OK (only documentation)
   15. Last checked on (end of I release)
       1. TODO
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-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
   2. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04 - To be assigned to Sunil
   3. RIC-1047 crash in E2T metric increment code 
   4. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   5. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   6. RIC-1043 Crash in E2T buildPrometheusList Function 
   7. RIC-1042 Can't register xApp
   8. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   9. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   10. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   11. RIC-1025 memory leak in routing manager
   12. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   13. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   14. RIC-1015 e2t too High default message size. → Nokia

   15. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   16. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   17. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   18. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   19. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   20. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlpye2mgr/+/6261 OK
   21. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6211 OK
   22. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6265 OK
   23. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/6301 OK as Influx helm chart changes.
   24. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/6309 OK
   25. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6313 OK
   26. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6322 OK
   27. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6081 OK
   28. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/6345 OK
   29. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/4880 OK (not yet merged)
4. 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
      1. ric-plt/a1 85,3 // no bugs (2021-01-26)

   1. 1. ric-plt/alarm-go 0,0 // no bugs (2021-01-31)

      2. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31)

      3. ric-plt/asn1-documents not applicable

      4. ric-plt/dbaas 0,0 // 2 blocker bugs in UT code (2021-01-27) - seems not to be anymore in latest version of source code.

      5. ric-plt/e2 0,0 // 2 blocker bugs (2021-06-18) - Thoralf raised RIC-802 and send e-mail to Dhiraj, Subhash and Naman.

      6. ric-plt/e2mgr 88,4 // no bugs (2021-01-30)

      7. ric-plt/lib/rmr 86,1 // no bugs (2021-06-22)

      8. ric-plt/rtmgr 77,8 // no bugs (2021-01-31)

      9. ric-plt/sdl  66,6 // 1 minor vulnerability bug (2021-01-29)

      10. ric-plt/sdlgo 45,5 // no bugs (2021-02-01)

      11. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31)

      12. ric-plt/submgr 33,4 // no bugs (2021-01-31)

      13. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-06-22)

      14. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31)

      15. ric-plt/vespamgr 79,0 // no bugs (2020-12-07)

      16. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31)

      17. ric-plt/xapp-frame-cpp 95,6 // 2 blocker bugs (2021-06-23) - Thoralf sent e-mail reminder to Anssi, Ron, Matti.

      18. ric-plt/xapp-frame-py 96,3 // 0 blocker bugs (2021-01-26)

      19. com/golog 80,7 // no bugs (2021-01-31)
      20. com/log 73,5 // 1 blocker bug and 8 minor ones (2021-01-27) - Thoralf sent e-mail to Abdulwahid
      21. com/pylog 33,7 // 11 major and minor bugs (2021-01-26)
5. 1. 8493)
   2. RIC-915 dms_cli for installing xapp not working (raised by James)
   3. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   4. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   5. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   6. RIC-894 long idle period (days) causes RMR connection breaks
   7. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   8. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   9. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   10. RIC-837 RMR is not forwarding messages from E2T to E2M
   11. RIC-835 → 2021-12-07 no news from Viktor
   12. fixed: 
       
6. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
   5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
   6. 2024-03-26: Unavailable today.
7. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13,2024-03-12,2024-03-26: no news
8. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
   8. 2024-03-12: Implementation completed, facing issues in code submission.
   9. 2024-03-26: Working on RIC-1049, documentation will also be made.
9. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
   4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
   5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
10. Abhijit updates (subteam-ag) ?Subhash: pls. merge:
    1. 2023-10-24:
       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 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
          
       2. no progress in review on the plain helm chart based deployment in
    1. 1. https://gerrit.o-ran-sc.org/r/c/ric-plt/
    a1
    1. 1. ric-dep/+/
    6365 and re-release
11. check D-release status: Release criteria checklist template, including e-mail reminder. All components to be handled by Nokia, except A1 → Subhash and RMR → Scott
12. Subhash shared the information about this public anybody-can-attend conference. It also includes a session about O-RAN SC (Subhash and Thoralf speaking): https://opensource.samsung.com/community/blogList
13. RICAPP agenda: RICAPP Meetings.

2021-06-08

We used the timeslot for demos: link

2021-05-25

Recording: link to zoom recording

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. https://gerrit.o-ran-sc.org/r/c/ric-plt/rtmgr/+/5990 ok (Abdulwahid checked this. It's only M size as the commit incorrectly replace many lines with spaces to tabs. Also review 6105 actually fixes some test cases in this area: This should be sufficient as the underlying functionality wasn't changed)
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6132 ok
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/vespamgr/+/5987 ok
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6014 ok
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/5826 (ok, even if no test cases as this is yaml files (Helm chart) repackaged.)
   6. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlpy/+/6060 ok
   7. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/6061 ok
   8. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/6062 ok
   9. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6082 ok
   10. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6109 ok
   11. https://gerrit.o-ran-sc.org/r/c/ric-plt/rtmgr/+/6112 ok
   12. https://gerrit.o-ran-sc.org/r/c/ric-plt/libe2ap/+/6131 (still in review, Thoralf commented that unit test cases to be added // we can compromise and extract this into separate item for E)
   13. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6081ok  (replaced by other review, anyway contains test cases, but will likely be abandoned anyway)
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

      1. ric-plt/a1 85,3 // no bugs (2021-01-26)

      2. ric-plt/alarm-go 0,0 // no bugs (2021-01-31)

      3. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31)

      4. ric-plt/asn1-documents not applicable

      5. ric-plt/dbaas 0,0 // 2 blocker bugs in UT code (2021-01-27) - seems not to be anymore in latest version of source code.

      6. ric-plt/e2 0,0 // 2 blocker bugs (2021-06-18)

      7. ric-plt/e2mgr 88,4 // no bugs (2021-01-30)

      8. ric-plt/lib/rmr 86,1 // no bugs (2021-06-22)

      9. ric-plt/rtmgr 77,8 // no bugs (2021-01-31)

      10. ric-plt/sdl  66,6 // 1 minor vulnerability bug (2021-01-29)

      11. ric-plt/sdlgo 45,5 // no bugs (2021-02-01)

      12. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31)

      13. ric-plt/submgr 33,4 // no bugs (2021-01-31)

      14. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-06-22)

      15. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31)

      16. ric-plt/vespamgr 79,0 // no bugs (2020-12-07)

      17. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31)

      18. ric-plt/xapp-frame-cpp 95,6 // 2 blocker bugs (2021-06-23) - Thoralf sent e-mail to Anssi, Ron, Matti.

      19. ric-plt/xapp-frame-py 96,3 // 0 blocker bugs (2021-01-26)

   2. As of 2021-05-25 the following components are missing in the report: ric-plt/alarm-cpp, ric-plt/libe2ap, ric-plt/nodeb-rnib, ric-plt/o1, ric-plt/ric-dep, ric-plt/ric-test, ric-plt/sdlpy, ric-plt/utils. Also ric-plt/jaegeradapter is missing, but we probably abandon that component. So no need to spend time on it.
      1. AP-Sunil: check this with HCL team
   3. How to get reports more frequently and up to date?
      1. AP-Sunil: check this with HCL team
   4. check why some have zero code coverage
      1. AP-Sunil: check this with HCL team
   5. ric-plt/e2 is already being handled via RIC-731 (expected to complete in Dawn)
3. Thoralf updated the CII evaluation criteria. We are now marked as "passed": Core Infrastructure Initiative (CII) Badging and https://bestpractices.coreinfrastructure.org/en/projects/4605
   
   1. Note I added RC-5 in Release criteria checklist template  "RC-5: Check that "blocker" code smells in Sonartype have been addressed"
4. Status check of D release items.
5. Subhash's mail - we went through the D release status of various items Samsung was planning to work on.
6. Sunil. RIC-723 further input needed from Thoralf
   1. Chaitanya (taking over from Alok): discuss in Wednesday's call.

7. Sunil:

   1. RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - completed  //  Subtask RIC-746 (Testing nanobot on top of helm 3 and k8s v1.18 version): Closed // Subtask RIC-747( Study how nanobot tests can be extended to Xapp) - Closed // Subtask RIC-748(Study OTF & Xtesting as a prospective test framework candidate to draw from for ORAN Near RT RIC) : Attached the ppt to the ticket. Given presentation to Thoralf and Matti.  As suggested we need some hands-on experience with OTF to confirm on this. OTF installation on local setup - Moved to Next release. // Subtask RIC-779(Xapp Testing Enhancement like Subscription deletion need to be handled using nanobot): Newly created ticket for handling subscription deletion using nanobot automation. Next Release. // Subtask RIC-775(Run nanobot based test automation from - it/test repository on RIC with k8 1.18/helm3 in OSC lab) Working on the vpn client connectivity (Softether). - In-progress // Ticket RIC-791:
      Raised for updating the container tag and pushing in to staging nexus repo.

   2. RIC-723 - [Study performance overhead of latest opentracing solutions] - InProgress Able to generate sampling data after getting some help from Thoralf. Continue to work with other scenarios to compare with previous results.

   3. RIC-731- [Static code and test coverage for E2] - 90% Completed. // Blocked on RIC-760 for test coverage.HCL working actively on RIC-731

   4. RIC-743 Create multiple e2sim for RIC benchmarking // Thoralf created RIC-790 and moved the two remaining subtasks from RIC-150 to it. I closed RIC-150 as DONE

8. demos again? Yes. On Jun-8 same time slot as this meeting, but 2 hours. Organizational issues after the demo.
   
   1. From last meeting:
      1. Thoralf to discuss demos for Nokia features, e.g. REST subscriptions, O2 CLI (DMS CLI - Subhash wished for this as REST API is the next step)
      2. Possible influxDB demo to show how to use from xApps
      3. Possible demos in devops areas (e.g. RIC-754)
      4. RIC-129 as slideset demo as real data cannot be used in public demo
      5. RIC-773 if ready by demo
      6. demo for RIC-747/RIC-748 slidesets
9. Remove Scott as committer - AP Thoralf to start mail thread
10. Replace Rahul with Naman - AP Thoralf to start approval mail on this.
11. RICAPP agenda: RICAPP Meetings.

2021-05-11

Recording: link to zoom recording

1. Every time: Check 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. TODO-check in next meeting only
   2. not yet merged: https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/5933 - abandoned
   3. not yet merged: https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/5826 (conclusion: no unit testing equivalent for YAML files in helm charts). - need to coordinate with Felix - decide to get rid of the 3rdpart directory because files will be slightly modified to refer to common template.
2. every second time: Review code coverage stats. (Sunil checks if this next step (overview page) is on HCL or on Thoralf's side as next action) - will discuss with Thoralf next time or by email.
   
   1. https://sonarcloud.io/organizations/o-ran-sc/projects?search=ric&sort=coverage
   2. NExt Sstep: Thoralf to create some way to maintain history data
3. When does Dawn end? As per release calendar, normally May-14. However I think we will start late with integrating everything together. So the 3-week sprint that is normally reserved for integration (May-17 – Jun-4) is likely still ok for additions. Based on this I would set a deadline for last commits to Jun-4.
4. Thoralf still to update or CII evaluation
   1. I added RC-5
5. Heewon's xApp python framework issue related to RIC-773 - some issues still
6. Update on A1-EI interface implementation.- Able to query A1-EI types from non RT RIC- Issue is clarified from nonRT RIC team to create EI-JOB
7. No progress done on E2APv1.1 support as Naman cannot work on it yet.
   

8. HCL updates;

   1. RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - completed

      1. Subtask RIC-747( Study how nanobot tests can be extended to Xapp)  - Had discussion with Thoralf and prioritize the testing scenarios for the next release. – Closed this ticket,

      2. Subtask RIC-748(Study OTF & Xtesting as a prospective test framework candidate to draw from for ORAN Near RT RIC) :  Attached the ppt to the ticket. Given presentation to Thoralf and Matti. 

         As suggested we need some hands-on experience with OTF to confirm on this. OTF installation on local setup - Ongoing.

      3. Subtask RIC-779(Xapp Testing Enhancement like Subscription deletion need to be handled using nanobot): Newly created ticket for handling subscription deletion using nanobot automation.

   2. RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress

      1. Able to generate sampling data after getting some help from Thoralf. Continue to work with other scenarios to compare with previous results. Same status as in last meeting. work on it this week.

   3. RIC-731- [Static code and test coverage for E2] -  90% Completed.

      1. Blocked on RIC-760 for test coverage.

      2. Same status as in last meeting

   4. RIC-671 [Achieve level "passing" in CII]

      1. Requested Thoralf for submitting application for ORAN project onboarding on LFN security.

      2. Same status as in last meeting

   5. RIC-150 - Perform e2e RIC benchmarking

                Subtask RIC-741(Verify Subcription flow using nanobot): Closed. Code merged

                Subtask RIC-742(Verify Indication flow using nanobot): Closed. Code merged

                Subtask RIC-750: (Bouncer to E2sim E2E Testing using nanobot) : Closed. Code merged

                Subtask RIC-754: (Kpimon to E2sim E2E testing using nanobot) : Closed. Code merged

.RIC-743 Create multiple e2sim for RIC benchmarking

                Same status as in last meeting - some indications are still dropping

 RIC-744 Verify the E2E communication for multiple e2sim

                Had debug session with Nokia team on E2term pod restart issue. Working further on this.

• demos again?
  1. From last meeting:
     1. Thoralf to discuss demos for Nokia features.
     2. Possible influxDB demo to show how to use from xApps
     3. Possible demos in devops areas (e.g. RIC-754)
     4. demo for RIC-747/RIC-748 slidesets
• RICAPP agenda: RICAPP Meetings.

2021-04-27

Recording: link to zoom recording

1. 1. 1. 11743 → to be merged by Thoralf Czichy 
         
      2. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      3. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
   4. 2024-03-12: No news.
   5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
2. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
   3. 2024-03-26: unavailable.
3. Himanshu (subteam-gs) would like to work on RIC-963
   
   1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
   2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
   3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
   4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
4. Dhiraj (subteam-r)
   
   1. 2023-12-05: moved the IPv6 item  to J release
   2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
   3. 2024-01-26: no news.
5. 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
   3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
   4. 2024-03-26: No news.
6. Nokia (subteam-n)
   1. RIC-997 postponed to J
   2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
7. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
   1. 2024-03-26: New nomination awaited from TOC.
8. J release
   
   1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
         1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
   2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
   3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J 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.
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
         
      2. committed items only: all teams (committed) and all teams (committed + tentative).
         
      3. items that are known to require work, but are currently not in J release: link

1. 1. input for release candidates: leftovers and generally open items, RSAC
   2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
2. RICAPP agenda: RICAPP Meetings.

2024-03-12

Recording:  link to zoom meeting

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 (end of I release)
      1. TODO
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-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04
   2. RIC-1047 crash in E2T metric increment code 
   3. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   4. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   5. RIC-1043 Crash in E2T buildPrometheusList Function 
   6. RIC-1042 Can't register xApp
   7. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   8. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   9. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   10. RIC-1025 memory leak in routing manager
   11. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   12. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   13. RIC-1015 e2t too High default message size. → Nokia

   14. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   15. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   16. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   17. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   18. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   19. 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)
   20. RIC-915 dms_cli for installing xapp not working (raised by James)
   21. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   22. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   23. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   24. RIC-894 long idle period (days) causes RMR connection breaks
   25. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   26. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   27. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   28. RIC-837 RMR is not forwarding messages from E2T to E2M
   29. RIC-835 → 2021-12-07 no news from Viktor
   30. fixed: 
       
4. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
   5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13,2024-03-12: no news
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
   8. 2024-03-12: Implementation completed, facing issues in code submission.
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
   4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      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 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
   4. 2024-03-12: No news.
9. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr.Good to raise JIRA.
11. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
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
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
13. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
14. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
15. J release
    
    1. 2024-02-13: Naman's input
       1. no Jira tickets yet, but woudl like to focus on 
          1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
       1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J 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.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link

1. 1. input for release candidates: leftovers and generally open items, RSAC
   2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
2. RICAPP agenda: RICAPP Meetings.

2024-02-13

Recording: link to zoom recording

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 (end of I release)
      1. TODO
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-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. new RIC-1047 crash in E2T metric increment code 
   2. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   3. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   4. RIC-1043 Crash in E2T buildPrometheusList Function 
   5. RIC-1042 Can't register xApp
   6. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   7. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   8. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   9. RIC-1025 memory leak in routing manager
   10. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   11. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   12. RIC-1015 e2t too High default message size. → Nokia

   13. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   14. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   15. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   16. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   17. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   18. 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)
   19. RIC-915 dms_cli for installing xapp not working (raised by James)
   20. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   21. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   22. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   23. RIC-894 long idle period (days) causes RMR connection breaks
   24. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   25. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   26. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   27. RIC-837 RMR is not forwarding messages from E2T to E2M
   28. RIC-835 → 2021-12-07 no news from Viktor
   29. fixed: 
       
4. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
   4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-02-13: no news
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
   7. 2024-02-13: working on RIC subscription delete testing 
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      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 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
   3. 2024-02-13: continues work on xapp framework rust, incl. metric support
9. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
11. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over teh next weeks.
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. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
14. J release
    
    1. 2024-02-13: Naman's input
       1. no Jira tickets yet, but woudl like to focus on 
          1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
       1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J 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.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link

1. 1. input for release candidates: leftovers and generally open items, RSAC
   2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
2. RICAPP agenda: RICAPP Meetings.

2024-01-30

Recording: link to zoom recording

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. TODO
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-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix 
   2. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr 
   3. RIC-1043 Crash in E2T buildPrometheusList Function 
   4. RIC-1042 Can't register xApp
   5. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   6. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   7. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   8. RIC-1025 memory leak in routing manager
   9. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   10. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   11. RIC-1015 e2t too High default message size. → Nokia

   12. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   13. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   14. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   15. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   16. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   17. 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)
   18. RIC-915 dms_cli for installing xapp not working (raised by James)
   19. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   20. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   21. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   22. RIC-894 long idle period (days) causes RMR connection breaks
   23. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   24. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   25. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   26. RIC-837 RMR is not forwarding messages from E2T to E2M
   27. RIC-835 → 2021-12-07 no news from Viktor
   28. fixed: 
       
4. James: updates?
   1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
   3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: 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.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
   6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
7. Naman updates (subteam-s) ?
   1. 2023-12-05: Naman gave an update on status of Samsung items
   2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
   3. 2024-01-30: no news
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      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 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16, 2024-01-30: No news.
9. Cap Gemini updates (subteam-cg)? 
   1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
11. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be commited now obtained. IPv6-related commits expected over teh next weeks.
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. RIC-997 postponed to J
14. J release
    
    1. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
    2. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J 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.
       1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-p, subteam-s, subteam-utfpr, subteam-ag, subteam-cg, subteam-r, subteam-gs
          
       2. committed items only: all teams (committed) and all teams (committed + tentative).
          
       3. items that are known to require work, but are currently not in J release: link

1. 1. input for release candidates: leftovers and generally open items, RSAC
   2. Sprint dates
      1. Sprint J release dev sprint 1: Feb-19 to Mar-10
      2. Sprint J release dev sprint 2: Mar-11 to Mar-31
      3. Sprint J release dev sprint 3: Apr-1 to Apr-21
      4. Sprint J release dev sprint 4: Apr-22 to May-12 (last planned development sprint)
      5. Sprint J release dev sprint 5: May-13 to Jun-2 (only for unplanned last-minute development items)
2. RICAPP agenda: RICAPP Meetings.

2024-01-16

Recording: link to zoom recording

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. TODO
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-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   2. RIC-1031Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   3. RIC-1032 → RIC-1035 - we cpontinue with this under RIC-1035 (discussed with Abhijit in the project meeting)
   4. RIC-1025 memory leak in routing manager
   5. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   6. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   7. RIC-1015 e2t too High default message size. → Nokia

   8. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   9. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   10. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   11. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look
   12. RIC-991 CVE-2023-40997 RMR related (not a duplicate) - Alexandre will take a look → DONE
   13. RIC-989 CVE-2023-40998 RMR (minor) security issue - Alexandre will take a look → DONE
   14. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   15. 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)
   16. RIC-915 dms_cli for installing xapp not working (raised by James)
   17. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   18. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   19. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   20. RIC-894 long idle period (days) causes RMR connection breaks
   21. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   22. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   23. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   24. RIC-837 RMR is not forwarding messages from E2T to E2M
   25. RIC-835 → 2021-12-07 no news from Viktor
   26. fixed: RIC-991, RIC-989
       
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 could be done with OSC.
   3. 2023-10-24
      1. updates from O-RAN f-2-f:
         1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
         2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
            1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
            2. more discussion coming at the joint OSC/OAI workshop in Boston
         3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
      2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
   4.  2023-11-07
      1. James is working with Taiwan lab on making sure we have good coverage
   5. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
   6. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: 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.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: demo of xApp project additions in I release → Next time
      
   5. 2024-01-16: re-evaluating RIC platform Jira items
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.
   4. 2023-11-07
      1. Naman presented his k8s operator work. Naman used Kubebuilder
      2. still working on operator to deploy RIC platform
   5. 2023-11-21:
      1. k8s operator commits - needs to be finalized.
   6. 2023-12-05: Naman gave an update on status of Samsung items
   7. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      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 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
   2. 2024-01-16 No news.
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-11-07: after discussions on the topic we would like to proceed with

      1. Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.

      2. Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.

      3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
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".
    2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
    3. 2023-11-21: as discussed in teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
    4. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    5. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
11. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be commited now obtained. IPv6-related commits expected over teh next weeks.
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. RIC-997 postponed to J
14. J release
    
    1. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J 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.
       1. Example Nokia J release: link

1. 1. input for release candidates: left ovleft oversers and generally open items, RSAC
   2. Sprint dates
      1. TODO - general timeframe: Jan-June 2024

1. RICAPP agenda: RICAPP Meetings.

2023-12-19 demo meeting instead of the normal project meeting, same time slot

2023-12-05

Recording: link to zoom recording

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.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11898 OK (simple alarms, but we created RIC-1028 for a more general test mock framework)
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 OK, since deployment acts as test
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12025 ok, lots of code, but very generic. Naman will try to add test case
      4. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12032 OK, only go.sum file
      5. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11895 OK (simple alarms, but we created RIC-1028 for a more general test mock framework)
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-1025 memory leak in routing manager
   2. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   3. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   4. RIC-1015 e2t too High default message size. → Nokia

   5. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   6. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   8. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look
   9. RIC-991 CVE-2023-40997 RMR related (not a duplicate) - Alexandre will take a look
   10. RIC-989 CVE-2023-40998 RMR (minor) security issue - Alexandre will take a look
   11. RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED
   12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   13. 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)
   14. RIC-915 dms_cli for installing xapp not working (raised by James)
   15. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   16. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   17. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   18. RIC-894 long idle period (days) causes RMR connection breaks
   19. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   20. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   21. 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.
   22. RIC-837 RMR is not forwarding messages from E2T to E2M
   23. RIC-835 → 2021-12-07 no news from Viktor
   24. fixed:
       
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 could be done with OSC.
   3. 2023-10-24
      1. updates from O-RAN f-2-f:
         1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
         2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
            1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
            2. more discussion coming at the joint OSC/OAI workshop in Boston
         3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
      2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
   4.  2023-11-07
      1. James is working with Taiwan lab on making sure we have good coverage
   5. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-01-16
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: no news. Wants to re-valuate tickets (earlier assigned to HCL).
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.
   4. 2023-11-07
      1. Naman presented his k8s operator work. Naman used Kubebuilder
      2. still working on operator to deploy RIC platform
   5. 2023-11-21:
      1. k8s operator commits - needs to be finalized.
   6. 2023-12-05: Naman gave an update on status of Samsung items
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      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 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia
         
      4. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      5. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-11-07: after discussions on the topic we would like to proceed with

      1. Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.

      2. Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.

      3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
      4. TODO-thoralf-to-ask-Gunja-to-present- Thoralf
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".
    2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
    3. 2023-11-21: as discussed in teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
    4. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
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

    3. 2023-11-07

       1. license topic still be discussed. Was working on an other project for last months

    4. 2023-12-05: moved the IPv6 item  to J release
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. RIC-997 postponed to J
14. Demo
    1. We will use the project meeting slot for the demos
    2. Naman to demo k8s operator deployment of platform (xapp part already done) and also A1 creating a policy.
    3. Adding support for DU in E2T/E2M/RNIB - >thoralf can do if not Gunja.
       
15. I release content
    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.

1. 1. input for release candidates: left overs and generally open items, RSAC
   2. 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)
   3. Plan (v03 as of 2023-08-18):
      1. I release plan moved to I release page.
      2. Thoralf will start generating images next week (Dec-11 - Dec-13)
2. RICAPP agenda: RICAPP Meetings.

2023-11-21

Recording: link to zoom recording

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.  TODO
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-1025 memory leak in routing manager
   2. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   3. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   4. RIC-1015 e2t too High default message size. → Nokia

   5. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   6. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   8. RIC-1001 RMR service should verify route tables - Alexandre will take a look
   9. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
   10. RIC-989 RMR (minor) security issue - Alexandre will take a look
   11. RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED
   12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   13. 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)
   14. RIC-915 dms_cli for installing xapp not working (raised by James)
   15. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   16. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   17. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   18. RIC-894 long idle period (days) causes RMR connection breaks
   19. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   20. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   21. 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.
   22. RIC-837 RMR is not forwarding messages from E2T to E2M
   23. RIC-835 → 2021-12-07 no news from Viktor
   24. fixed:
       
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 could be done with OSC.
   3. 2023-10-24
      1. updates from O-RAN f-2-f:
         1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
         2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
            1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
            2. more discussion coming at the joint OSC/OAI workshop in Boston
         3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
      2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
   4.  2023-11-07
      1. James is working with Taiwan lab on making sure we have good coverage
   5. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: 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.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
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.
   4. 2023-11-07
      1. Naman presented his k8s operator work. Naman used Kubebuilder
      2. still working on operator to deploy RIC platform
   5. 2023-11-21:
      1. k8s operator commits - needs to be finalized.
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      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 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia
         
      4. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      5. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-11-07: after discussions on the topic we would like to proceed with

      1. Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.

      2. Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.

      3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
      4. TODO-thoralf-to-ask-Gunja-to-present- Thoralf
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".
    2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
    3. 2023-11-21: as discussed in the beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
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

    3. 2023-11-07

       1. license topic still be discussed. Was working on an other project for last months

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. .RIC-997 likely being postponed.
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.

      1. 
         

2. RICAPP agenda: RICAPP Meetings.

2023-11-07

Recording: link to zoom recording

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.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11889 ok. included test cases
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/11999 actually small changes, but as this is generated code, no need for test cases. Actually hand-written code is coming in another review together with test code.
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-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

   2. RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia

   3. RIC-1015 e2t too High default message size. → Nokia

   4. RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia

   5. RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption 

   6. RIC-1009 E2Mgr API can be improperly invoked → TODO-thoralf-converted-this-to-Epic
   7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   8. RIC-1001 RMR service should verify route tables - Alexandre will take a look
   9. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
   10. RIC-989 RMR (minor) security issue - Alexandre will take a look
   11. RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED
   12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   13. 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)
   14. RIC-915 dms_cli for installing xapp not working (raised by James)
   15. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   16. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   17. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   18. RIC-894 long idle period (days) causes RMR connection breaks
   19. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   20. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   21. 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.
   22. RIC-837 RMR is not forwarding messages from E2T to E2M
   23. RIC-835 → 2021-12-07 no news from Viktor
   24. fixed: RIC-972
       
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 could be done with OSC.
   3. 2023-10-24
      1. updates from O-RAN f-2-f:
         1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
         2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
            1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
            2. more discussion coming at the joint OSC/OAI workshop in Boston
         3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
      2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
   4.  2023-11-07
      1. James is working with Taiwan lab on making sure we have good coverage
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: 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.
   2. 2023-11-07: Not in the call today
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.
   4. 2023-11-07
      1. Naman presented his k8s operator work. Naman used Kubebuilder
      2. still working on operator to deploy RIC platform
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      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 → still to be made 1.0.0
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 
      3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it.
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-11-07: after discussions on the topic we would like to proceed with

      1. Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.

      2. Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well. TODO-discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation

      3. TODO-thoralf-to-ask-Gunja-to-present
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".
    2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
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

    3. 2023-11-07

       1. license topic still be discussed. Was working on an other project for last months

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. ...
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
3. Every time: Check 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. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/5848 (ok, exceptional) "Add ability to save route table updates to disk". Actual code lines changed is "only" 96 in an area that supports debugging. Wrote a note to Scott, but no expectation to add test cases.
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/5856 (ok, includes unit test)
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/vespamgr/+/5864 (ok, actually only test cases for coverage improvements)
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/5865 (ok, adds HTTP port in subscription, test case was adapted)
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/5897 (ok, unit testing coverage improvements)
   6. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/5909 (ok,. test case was added)
   7. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/5925 (ok, new test cases)
   8. not yet merged: https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/5933
   9. not yet merged: https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/5826 (conclusion: no unit testing equivalent for YAML files in helm charts).
4. every second time: Review code coverage stats. (Sunil checks if this next step (overview page) is on HCL or on Thoralf's side as next action) - will discuss with Thoralf next time or by email.
   1. no news yet.
5. Thoralf still to update or CII evaluation
6. Heewon's xApp python framework issue related to RIC-773 - check agian two weeks from now.

7. RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - completed

   1. Subtask RIC-747( Study how nanobot tests can be extended to Xapp)  - Prepared  a study PPT and will discuss in next call with Matti and Thoralf. 

   2. Subtask RIC-748(Study OTF & Xtesting as a prospective test framework candidate to draw from for ORAN Near RT RIC) :  Prepared a PPT and will discuss in next call with Matti and Thoralf

8. RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress // Able to generate sampling data after getting some help from Thoralf. Continue to work with other scenarios to compare with previous results. Same status as in last meeting

9. RIC-731- [Static code and test coverage for E2] -  90% Completed. Blocked on RIC-760 for test coverage. Same status as in last meeting

10. RIC-671 [Achieve level "passing" in CII]  Requested Thoralf for submitting application for ORAN project onboarding on LFN security. Same status as in last meeting

11. RIC-150 - Perform e2e RIC benchmarking

    1. Subtask: RIC-740, RIC-741 & RIC-742 Addressed the review comments provided by Dave.  Jenkin job is also successful.  Waiting for Bharath to review the tickets. So that tickets can be closed.

    2. Subtask: RIC-754 KPIMON xapp validation using nanobot with SDL                                Committed the code in gerrit. Review and Job is successful.                                    Will merge the code.

12. .RIC-743 Create multiple e2sim for RIC benchmarking Same status as in last meeting

13. RIC-744 Verify the E2E communication for multiple e2sim  Same status as in last meeting

14. A1-EI Subhash is now working on this. E2 work. Subhash to send e-mail to Thoralf with details on change in committers, incl. LF ID of Naman.
15. demos again?
    1. Thoralf to discuss demos for Nokia features.
    2. Possible influxDB demo to show how to use from xApps
    3. Possible demos in devops areas (e.g. RIC-754)
    4. demo for RIC-747/RIC-748 slidesets
16. RICAPP agenda: RICAPP Meetings.

17. RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - completed

    Subtask RIC-747( Study how nanobot tests can be extended to Xapp) : Discussed with Thoralf and based on priority we listed out the scenarios for xapp testing using nanobot. 

    First Priority:

    • Xapp Testing Enhancement like Subscription deletion need to be addup.
    • The control interface nanobot could even steer different scenarios, e.g., related to timing. E.g., send a subscription delete for a originally-failed or non-existent subscription; or send duplicate subscriptions, … I.e., testing for correct behavior in failure/timeout scenarios.

     Second Priority:     

    • Xapp need to handle E2 Control which already has a scenario (see spec) in which the E2 node sends back a RIC CONTROL ACK. That could be tested as well.
    • Additionally we could have test cases for A1 policy handling (and possibly A1-EI handling if we get +https://jira.o-ran-sc.org/browse/RIC-129+ implemented within Dawn)

    Third Priority:

    • O1 proxying, i.e., the CM flow to xApps and FM/PM flow from xApps would be more test cases. 
    • Change in the xApp test implementation in which we do not rely on logs but nanobot communicates with the test xApp via some control interface to check Whether a test has been successful or not.

    Subtask RIC-748(Study OTF & Xtesting as a prospective test framework candidate to draw from for ORAN Near RT RIC) :  Given demo to Thoralf and Matti about this OTF and xtesting comparison.    

      As discussed with Thoralf  he asked which one we can go with either xtesting or OTF.

      I preferred OTF test framework need to explore more on hands-on experience with OTF and VTH integration.

      Working in progress on deploying OTF in to our environment and also looking for OSC lab access to understand.

Older meeting minutes

check from here: Project meetings (old)

...