...

...

2024-

...

04-

...

23

Recording: zoom link

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
      https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/7955 ok, removal of deprecated 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. We Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this today.this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1057 gNB unable to connect during high amount of Subscription Requests
   2. RIC-897 SCTP connection fails with Viavi
   3. RIC-894 long idle period (days) causes RMR connection breaks
   4. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   5. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail.
      1. could be staging repo related (10004) vs release repo (10002) for the base image
   6. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   7. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   8. RIC-835 → 2021-12-07 news from Viktor
   9. RIC-837 RMR is not forwarding messages from E2T to E2M
   10. 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.
   11. fixed: RIC-895 (routes in routing mgr for service update messages)
   12. anybody would like to get more familiar with RMR?
4. Sunil still to discuss with other team members for other items from subteam-h
   1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
   2. 2022-03-01_
      1. Sangeetha working on RIC-860, done, but code still to be checked in.
      2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
      3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
      4. Subhash asked for documentation of nanobot from Sunil. almost done.
   3. 2022-03-15: status Sangeetha?
5. 1. 1056Crashing e2mgr after sending high amount of Subscription Requests
   2. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
   3. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation
   4. 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.
   5. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
   6. 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)
      
   7. RIC-1047 crash in E2T metric increment code - WIP
   8. 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)
   9. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   10. RIC-1043 Crash in E2T buildPrometheusList Function  - WIP
   11. RIC-1042 Can't register xApp
   12. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation - Mostly fixed, To be confirmed by Abhijit.
   13. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   14. 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)
   15. RIC-1025 memory leak in routing manager
   16. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

   21. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   22. 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)
   23. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   24. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit
   James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
   1. 2022-01-27 (Mail sent)
      
   2. 2022-02-15: resending with the right David
      
   3. 2022-03-01:
      1. workshop to be planned (James in discussion with David)
      2. in last weeks SMO+RSAC meeting this was discussed as well. It would be good to have a test case that just verifies successful deployment of the RIC platform, workshop still to be scheduled.
      3. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
      4. 2022-03-15: James creating a E release profile for powder
   4. 2022-03-15: workshop still to be held (was moved by two weeks (Mar-24))
      
   5. 2022-03-29: workshop planned for April-7 9am EDT https://lists.o-ran-sc.org/g/discuss/message/487
6. Progress on E2APv2.0?
   1. in ric platform and simulators?
      1. Any first code/design review request that Arun and Dhiraj should review?
      2. progress, subhash: simulator adapted. E2T changes internally ready.
      3. Subhash&co did not plan to do any testing on xApp side.
      4. thoralf to sent invitation to Subhash &co for Friday → DONE
         
         1. agreed on configuration transfer to be handled similar to function definitions as E2APv2.0 now defines configuration updates as replacing instead of updating existing component configuration entries.
         2. E2 reset to be handled as new state that xApps see: "connected---transition1-->connected-but-under-reset---transition2-->connected". We use a timer, instead of strict xapp and submgr confirmation that all has been cleaned up. xApps shall resubscribe only after transition2. xapps can assume that submgr has removed all subscriptions (in its view of the world) and that the E2 node has removed them (in its view of the world)
         3. Subhash will send slideset for this during this week
         4. E2 implementation status and reviews coming?
      5. 2022-03-15 any news?
         1. do we need an E2APv2.0 branch (submgr used/uses e2ap-v02.00)
            1. if we create a E2 branch now we can do the review in that branch. E2T, E2M, and RNIB. submgr already has branch.
            2. Subhash to ask from Alex Stancu for branch in E2 sim
         2. Already initial versions of the work? Dhiraj and Arun are available for reviewing.
         3. updated design: E2AP 2.0 Design
         4. Could provide initial version in which config handling (IE in E2 Setup) is just ignored.
         5. AP: Subhash to present he E2AP2.0 slides (15min)
         6. A1 mediator work proceeding (two more APIs)
      6. 2022-03-29
         1. AP: Subhash to present he E2AP2.0 slides (15min) from here: E2AP 2.0 Design
            
         2. Simulator code updated to E2APv2.0: https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/7971 (incl. asn1c generated files) config transfer message coming soon
         3. protobuf definitions for configuration components under re-work
         4. E2APv2-0 branches? nodeb-rnib already branched.
   2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
      1. kpimon
      2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
         1. hw-go issue with old xapp frame lib used. - needs to be updated.
         2. in same mail thread there's another issue - to be discussed over mail.
         3. 2022-03-15: Still open corner case where registration is not done yet, but sub requests are already sent. Thoralf to ask from Nune.
            
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
         1. done, but not yet open for review.
   3. in DU
      1. 2022-02-23 user-30c9d reported in TOC that this work is done.
7. RIC-641 Sandeep (HCL) is working on this. Work is progressing
8. New contribution proposals
   1. E2 RESET handling
      1. when meeting?
      2. Thoralf to send meeting invitation for this or next week (timezone india+europe)
   2. Influx-DB Wrapper
      1. new repo=stslgo (shared time series layer)
      2. involve Sunil (HCL) and Dhiraj and Subhash & co for proposal
   3. O1-NetConf Enhancements
      
      1. Nune said "ok"
   4. Stability Issues
      1. Nune said "ok"
   5. Thoralf created JIRA items for the items in c and d and b: Link =https://jira.o-ran-sc.org/issues/?jql=labels%20%3D%20subteam-p
9. RICAPP agenda: RICAPP Meetings.

2022-03-15

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/sdlgo/+/7944 OK
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlpy/+/7945 OK
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/7946 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..
   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. 2022-03-15: Thoralf went through the list → no updates.
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-890, RIC-891, RIC-892: build of xapp-ccp framework seems to fail.
   2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   3. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   4. RIC-835 → 2021-12-07 news from Viktor
   5. RIC-837 RMR is not forwarding messages from E2T to E2M
   6. RIC-840 Unable to deploy E2Term on Dawn release
   7. 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.
   8. fixed: no new fixes since last meeting. We marked RIC-840 as done because in E it seems to work.
   9. anybody would like to get more familiar with RMR?
4. Sunil still to discuss with other team members for other items from subteam-h
   1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
   2. 2022-03-01_
      1. Sangeetha working on RIC-860, done, but code still to be checked in.
      2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in.
      3. O1 testing is also being worked on.
      4. Subhash asked for documentation of nanobot from Sunil. almost done.
   3. 2022-03-15: status Sangeetha?
5. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
   1. 2022-01-27 (Mail sent)
      
   2. 2022-02-15: resending with the right David
      
   3. 2022-03-01:
      1. workshop to be planned (James in discussion with David)
      2. in last weeks SMO+RSAC meeting this was discussed as well. It would be good to have a test case that just verifies successful deployment of the RIC platform, workshop still to be scheduled.
      3. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
      4. 2022-03-15: James creating a E release profile for powder
   4. 2022-03-15: workshop still to be held (was moved by two weeks (Mar-24))
6. Progress on E2APv2.0?
   1. in ric platform and simulators?
      1. Any first code/design review request that Arun and Dhiraj should review?
      2. progress, subhash: simulator adapted. E2T changes internally ready.
      3. Subhash&co did not plan to do any testing on xApp side.
      4. thoralf to sent invitation to Subhash &co for Friday → DONE
         
         1. agreed on configuration transfer to be handled similar to function definitions as E2APv2.0 now defines configuration updates as replacing instead of updating existing component configuration entries.
         2. E2 reset to be handled as new state that xApps see: "connected---transition1-->connected-but-under-reset---transition2-->connected". We use a timer, instead of strict xapp and submgr confirmation that all has been cleaned up. xApps shall resubscribe only after transition2. xapps can assume that submgr has removed all subscriptions (in its view of the world) and that the E2 node has removed them (in its view of the world)
         3. Subhash will send slideset for this during this week
         4. E2 implementation status and reviews coming?
      5. 2022-03-15 any news?
         1. do we need an E2APv2.0 branch (submgr used/uses e2ap-v02.00)
            1. if we create a E2 branch now we can do the review in that branch. E2T, E2M, and RNIB. submgr already has branch.
            2. Subhash to ask from Alex Stancu for branch in E2 sim
         2. Already initial versions of the work? Dhiraj and Arun are available for reviewing.
         3. updated design: E2AP 2.0 Design
         4. Could provide initial version in which config handling (IE in E2 Setup) is just ignored.
         5. AP: Subhash to present he E2AP2.0 slides (15min)
         6. A1 mediator work proceeding (two more APIs)
   2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
      1. kpimon
      2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
         1. hw-go issue with old xapp frame lib used. - needs to be updated.
         2. in same mail thread there's another issue - to be discussed over mail.
         3. 2022-03-15: Still open corner case where registration is not done yet, but sub requests are already sent. Thoralf to ask from Nune.
         4. 2022-03-29: xapp wasn't registered (as visible in output of curl commane below. instructions how to register are in user_guide_v2

            1. $ curl -i -X GET http://10.244.0.138:8080/ric/v1/xapps    //IP = appmgr IP

            2. []

      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
         1. done, but not yet open for review.
   3. in DU
      1. 2022-02-23 user-30c9d reported in TOC that this work is done.
7. Alexandre started work on RIC-705
8. RIC-641 Sandeep (HCL) is working on this.
9. RICAPP agenda: RICAPP Meetings.

2022-03-01

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/submgr/+/7610 OK
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7587 OK redis client from v7 to v8 and adapting to changes in interface.
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. not done this time.
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   2. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   3. RIC-835 → 2021-12-07 news from Viktor
   4. RIC-837 RMR is not forwarding messages from E2T to E2M
   5. RIC-840 Unable to deploy E2Term on Dawn release
   6. 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.
   7. fixed: no new fixes since last meeting.
   8. anybody would like to get more familiar with RMR?
4. Cross-check with A. if he has updated the instructions to point to helm3.
   1. A. can look on this on Jan-31 and update here: new section here - https://docs.o-ran-sc.org/projects/o-ran-sc-it-dep/en/latest/installation-guides.html
   2. 2022-02-14: there's a review for this documentation change (change 7638). The review fails in LF CI/Jenkins in SMO/non-rt RIC related parts. Asked help from James by e-mail. James raised a request to LF: IT-23628
   3. 2022-02-16: merged and DONE.
5. Sunil still to discuss with other team members for other items from subteam-h
   1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
   2. Sangeetha working on RIC-860, done, but code still to be checked in.
      
   3. Sangeetha working on RIC-878, status see Jira item
      
   4. Subhash asked for documentation of nanobot from Sunil.
6. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
   1. 2022-01-27 (Mail sent)
      
   2. 2022-02-15: resending with the right David
      
   3. 2022-03-01: workshop to be planned (James in discussion with David)
   4. in last weeks SMO+RSAC meeting this was discussed as well. It would be good to have a test case that just verifies successful deployment of teh RIC platform, workshop still to be scheduled.
   5. James ran O-ran profile in powder lab. Seemed to work and deploy Dawn. Working with David Jo. (UoU) to update to E release.
7. Progress on E2APv2.0?
   1. in ric platform and simulators?
      1. Any first code/design review request that Arun and Dhiraj should review?
      2. progress, subhash: simulator adapted. E2T changes internally ready.
      3. Subhash&co did not plan to do any testing on xApp side.
      4. thoralf to sent invitation to Subhash &co for Friday → DONE
         
         1. agreed on configuration transfer to be handled similar to function definitions as E2APv2.0 now defines configuration updates as replacing instead of updating existing component configuration entries.
         2. E2 reset to be handled as new state that xApps see: "connected---transition1-->connected-but-under-reset---transition2-->connected". We use a timer, instead of strict xapp and submgr confirmation that all has been cleaned up. xApps shall resubscribe only after transition2. xapps can assume that submgr has removed all subscriptions (in its view of the world) and that the E2 node has removed them (in its view of the world)
         3. Subhash will send slideset for this during this week
   2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
      1. kpimon
      2. bouncer (working on rest based submgr API if that means HCL is working RIC-641, please inform Alexandre about this.
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
         1. hw-go issue with old xapp frame lib used. - needs to be updated.
            
         2. in same mail thread there's another issue - to be discussed over mail.
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
   3. in DU
      1. 2022-02-23 user-30c9d reported in TOC that this work is done.
8. anybody working on this RIC-705 Alexandre wants to know.
   1. 2022-02-15: Thoralf sent mail to E & A.
   2. 2022-02-21: Alexandre agree to work on RIC-705. Might also later work on RIC-641. To keep track of things, I (Thoralf) took the liberty to give Alexandre a separate subteam tag in Jira: “subteam-utfpr” and marked RIC-705 as per the convention. I updated the links in §7.2 accordingly in Jira usage conventions.
9. RICAPP agenda: RICAPP Meetings.

2022-02-15

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. not done this time.
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. ric-plt/alarm-go 0,0 // no bugs (2021-11-22 → 2022-02-13 )
   4. ric-plt/appmgr 19,3 // 1 major bug (2022-01-30 → 2022-02-13)
   5. ric-plt/e2mgr 88,6 // no bugs (2021-11-18 → 2022-02-14)
   6. ric-plt/lib/rmr 86,2 // no bugs (2021-11-23 → 2022-02-08)
   7. ric-plt/sdlgo 25,2 → 90,2// no bugs (2022-01-31 → 2022-02-14) → RIC-887 fixed reporting job issue
   8. ric-plt/submgr 51,2 // no bugs (2022-01-30 → 2022-02-13)
   9. ric-plt/tracelibcpp 0,0 // 1 major bug (2022-01-25 → 2022-02-08)
   10. ric-plt/tracelibgo 96,2 //0 bugs (2022-01-30 → 2022-02-13)
   11. ric-plt/xapp-frame 0,0 // no bugs (2021-11-22 → 2022-02-13)
   12. ric-plt/xapp-frame-cpp 95,6 // no blocker bugs (2022-01-26 → 2022-02-09)
3. Every time: Check if there are new bug reports in JIRA: link
   1. new RIC-885, RIC-887 (sdlgo) → fixed
   2. new RIC-883 xappframe-cpp → Alexandre fixed this
   3. RIC-872 → Alexandre fixed this
   4. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   5. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   6. RIC-835 → 2021-12-07 news from Viktor
   7. RIC-837 RMR is not forwarding messages from E2T to E2M
   8. RIC-840 Unable to deploy E2Term on Dawn release
   9. 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.
   10. fixed: RIC-872, RIC-883, RIC-885, RIC-887
   11. anybody would like to get more familiar with RMR?
4. Cross-check with A. if he has updated the instructions to point to helm3.
   1. A. can look on this on Jan-31 and update here: new section here - https://docs.o-ran-sc.org/projects/o-ran-sc-it-dep/en/latest/installation-guides.html
   2. 2022-02-14: there's a review for this documentation change (change 7638). The review fails in LF CI/Jenkins in SMO/non-rt RIC related parts. Asked help from James by e-mail. James raised a request to LF: IT-23628
5. Sunil still to discuss with other team members for other items from subteam-h
   1. 2022-02-15 done and clarified
      
      1. RIC-878 - A1 mediator testing in nanobot
      2. RIC-860 xapp testing nanobot enhancements: wider coverage of functionality, e.g., Subscription deletion
      3. RICAPP-176 adapting bouncer xapp to REST subscription interface.
      4. Other tickets CI/CD and Code coverage tickets, I am still looking for the resources to work on that.
6. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
   1. 2022-01-27 (Mail sent)
      
   2. 2022-02-15: resending with the right David
      
7. Progress on E2APv2.0?
   1. in ric platform and simulators?
      1. any questions/comments on Arun's slideset in RIC-722 ?
      2. Any first code/design review request that Arun and Dhiraj should review?
      3. progress, subhash: simulator adapted. E2T changes internally ready.
      4. config xapp and E2 manager interface.
      5. discuss E2 reset
      6. thoralf to sent invitation to Subhash &co for Friday
      7. Subhash&co did not plan to do any testing on xApp side.
   2. in xapps? E2APv2.0 update in xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
      1. kpimon
      2. bouncer
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
   3. in DU?
8. anybody working on this RIC-705 Alexandre wants to know.
   1. 2022-02-15: Thoralf sent mail to E & A.
9. RICAPP agenda: RICAPP Meetings.

2022-02-01

Recording: link to zoom recording

1. 1. r/c/ric-plt/e2mgr/+/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: 
       
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.mp4

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-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: 
       
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.
   6. 2024-03-26: Unavailable today.
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,2024-03-26,2024-04-09: 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.
   9. 2024-03-26: Working on RIC-1049, documentation will also be made.
   10. 2024-03-09: Absent
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
   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
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.
   5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
   6. 2024-03-09: Not available.
      
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
   3. 2024-03-26,2024-03-09: unavailable.
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.
    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.
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.
    3. 2024-01-26,2024-04-09: no news.
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
    4. 2024-03-26,2024-04-09: No news.
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.
    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)
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
16. 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)
17. RICAPP agenda: RICAPP Meetings.

2024-03-26

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. Thoralf-TODO-cross-check with A. if he has updated the instructions to point to helm3.
   1. A. can look on this on Jan-31 and update here: new section here - https://docs.o-ran-sc.org/projects/o-ran-sc-it-dep/en/latest/installation-guides.html
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. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7450 ok
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/alarm-go/+/7465 ok
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7481 ok
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/7515 ok
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7592 ok (note this is the E2APv2.0 support in submgr in subbranch "e2ap-02.00" - only to be merged with other E2APv2.0 changes)
   6. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7587 ok
   7. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7610 ok
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. 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. ric-plt/alarm-go 0,0 // no bugs (2021-11-22 → 2022-01-30 )
   4. ric-plt/appmgr 17,5 → 19,3 // 1 major bug (2021-11-22 → 2022-01-30)
   5. ric-plt/e2mgr 88,6 // no bugs (2021-11-18 → 2022-01-30)
   6. ric-plt/lib/rmr 70,4 → 86,2 // no bugs (2021-11-23 → 2022-01-25)
   7. ric-plt/sdlgo 47,4 → 32.4 → 25,2 // no bugs (2021-11-23 → 2022-01-31) → raise bug
   8. ric-plt/submgr 44,8  → 47,4 → 51,2 // no bugs (2021-11-22 → 2022-01-30)
   9. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-11-16 → 2022-01-25)
   10. ric-plt/tracelibgo 94,7 → 96,2 //0 bugs (2021-11-22 → 2022-01-30)
   11. ric-plt/xapp-frame 0,0 // no bugs (2021-09-30 → 2021-11-22) - same as before.
   12. ric-plt/xapp-frame-cpp 96,3 → 95,6 // still 2 blocker bugs → 0 blocker bugs (fix) (2021-11-17 → 2022-01-26)
   13. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
5. 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/e2mgr/+/8493)
   21. RIC-915 dms_cli for installing xapp not working (raised by James)
   22. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   23. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   24. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   25. RIC-894 long idle period (days) causes RMR connection breaks
   26. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   27. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   Every time: Check if there are new bug reports in JIRA: link
   1. new: RIC-872 needs someone to fix. → Alexandre working it. Discussion in revies
   2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   3. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   4. RIC-835 → 2021-12-07 news from Viktor
   5. RIC-837 RMR is not forwarding messages from E2T to E2M
   6. RIC-840 Unable to deploy E2Term on Dawn release
   7. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   8. 2021-12-21: Trying to get bandwidth for this during F release.
   9. fixed: RIC-880, RIC-875, RIC-873, RIC-869, RIC-862
   10. anybody would like to get more familiar with RMR?
6. F release
   
   1. schedule
      1. Sprint F release dev sprint 1: Feb-21 to Mar-13 (as per Releases)
      2. Sprint F release dev sprint 2: Mar-14 to Apr-3
      3. Sprint F release dev sprint 3: Apr-4 to Apr-24
      4. Sprint F release dev sprint 4: Apr-25 to May-15 (last planned development sprint)
      5. Sprint F release dev sprint5: May-16 to Jun-5 (only for unplanned last-minute development items)
   2. Filter All RICP items: F release only (links copied from Jira usage conventions)
      
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-s and all teams.
         
      2. committed items only: all teams (committed)
      3. items that are known to require work, but are currently not in F release: link
   3. update xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
      1. kpimon
      2. bouncer
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
   4. Sunil still to discuss with other team members for other items from subteam-h
   5. James: RSAC recommended incorporating OTF in testing (David K. can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James. 2022-01-27 (Mail sent)
      
7. James had a meeting with Powderlab in UofU on using their lab setup for testing. They have earlier tested OSC D release (and others). James is thinking about using this. Low hanging fruit would be to see if we can run our end-2-end robot test cases in this lab.
   1. POWDER testbed ORAN demo submission at MWC 2022: https://oranalliance.atlassian.net/wiki/spaces/OAH/pages/2330100360/PROCESSING+MWC-B-22-14+University+of+Utah
      
8. Needed: overview of what is in golang and what in python and what in c++ and what is missing →
   
   1. Added this as RIC-882 (F release)
9. RICAPP agenda: RICAPP Meetings.

2022-01-18

Recording: RIC platform meeting, demo on OID support in RIC, RIC xApp meeting, demo on hello-world python xapp

1. Thoralf-TODO-cross-check with Abdulwahid if he has updated the instructions to point to helm3.
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. we did not do this this time.
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. We did not do this this time
   Anybody willing to work on them?
4. Every time: Check if there are new bug reports in JIRA: link
   1. new: RIC-872 needs someone to fix. → Alexandre fixed this.
   2. RIC-875 thoralf to gheck with timo if fixed already.
   3. All others thoralf still to gpo thporugh if any news on them.
   4. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build

   5. RIC-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak) → Alexandre → DONE

   6. RIC-861 re-enable RMR libary's module tests

   7. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   8. RIC-835 → 2021-12-07 news from Viktor
   9. RIC-837 RMR is not forwarding messages from E2T to E2M
   10. RIC-840 Unable to deploy E2Term on Dawn release
   11. 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.
   12. fixed: RIC-862, RIC-828, RIC-836, RIC-858, RIC-859, RIC-863, RIC-865
   13. anybody would like to get more familiar with RMR?
5. F release
   
   1. schedule
      1. Sprint F release dev sprint 1: Feb-21 to Mar-13 (as per Releases)
      2. Sprint F release dev sprint 2: Mar-14 to Apr-3
      3. Sprint F release dev sprint 3: Apr-4 to Apr-24
      4. Sprint F release dev sprint 4: Apr-25 to May-15 (last planned development sprint)
      5. Sprint F release dev sprint5: May-16 to Jun-5 (only for unplanned last-minute development items)
   2. Filter All RICP items: F release only (links copied from Jira usage conventions)
      
      1. committed (90% sure) and tentative (90...30% sure) items: subteam-n, subteam-h, subteam-s and all teams.
         
      2. committed items only: all teams (committed)
      3. items that are known to require work, but are currently not in F release: link
   3. update xApps that use the old RMR to-be-removed xapp subscription interface - Thoralf asking Sunil to coordinate xapp-side adaptation to REST interface - see RIC-375
      1. kpimon
      2. bouncer
      3. all hello-world xapps (hw-go already uses submgr REST ifc)
      4. update simulators (discuss with Subhash if needed) do we have two simulators we have to update?
   4. Sunil still to discuss with other team members for other items from subteam-h
   5. James: RSAC recommended incorporating OTF in testing (David K. can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
6. Needed: overview of what is in golang and what in python and what in c++ and what is missing
7. E-release Demo for E2APv1.1 and support for OID in function definitions (Naman)
8. RICAPP agenda: RICAPP Meetings.

2022-01-04

Recording: link to zoom recording

1. no near-rt RIC platform issues on the agenda. If anything to discuss, pls. discuss. If not, move on to point 2.
2. RMR related bug raised by Erkki RIC-872, Matti assigned it to Alexander, who will work on it.
3. RICAPP agenda: RICAPP Meetings.

2021-12-21

Recording: link to zoom recording

1. We will have the E-release demo in one hour from now: 2021-12-21 Release E
2. next meeting: Jan-4-2022 focus will be the ric xapp project. After this the next one is on Jan-18 which will again handle xapp and ric platform combined.
   
   1. Any input for F release, pls. send to Thoralf (back in office on Jan-10)
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. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/6964 ok, not relevant as only API definition
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7151 ok
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7152 ok
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6712 ok, as a test tool.
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7398 ok
   6. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7428 ok
   7. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7290 ok
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)
   3. We did not do this this time
   Anybody willing to work on them?
5. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build

   2. RIC-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak) → Alexandre

   3. RIC-861 re-enable RMR libary's module tests

   4. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   5. RIC-835 → 2021-12-07 news from Viktor
   6. RIC-837 RMR is not forwarding messages from E2T to E2M
   7. RIC-840 Unable to deploy E2Term on Dawn release
   8. 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.
   9. fixed: RIC-828, RIC-836, RIC-858, RIC-859, RIC-863, RIC-865
   10. anybody would like to get more familiar with RMR?
6. Action items
   1. SCCL update - Matti will check with Tracy
      
      1. still discussion within O-RAN-SC still ongoing
      2. publication of O-RAN specs of July train should happen any time now.
      3. O-RAN specs of July train have been released. Need to check if any parts have been put under SCCL
   2. E2 simulator seeing E2 setups not passing through: 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). Amit raised RIC-852 for this.
      1. 2021-12-21 no news from Nokia side. → see RIC-852 above
7. E release
   
   1. E release images test-deployed. E2 Setup works, xApp deployment. All manual checks.
   2. TOC approved E release on Dec-15. Release images are here: Near-RT RIC (E release)
   3. 2021-12-21 Thoralf double-checked that branch "e-release" has been created in all components and also updated release checklist (all OK now): Release criteria checklist - Release E. All criteria "ok"
8. Preliminary planning for the F release
   1. Not completed in E release (spill over into F): RIC-849, and all from this list.
   2. Candidate list for F release (priority column as per Thoralf's best understanding) https://jira.o-ran-sc.org/issues/?jql=(fixVersion%20in%20(ZZZ_future)%20or%20fixVersion%20in%20(F)%20)AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20%20ORDER%20BY%20component%20ASC
   3. we will discuss this again in the next meeting.
   4. Thoralf to send a reminder.
9. Nitin: submgr subscription REST interface: https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/xapp-frame.git;a=tree;f=api
10. RICAPP agenda: RICAPP Meetings.

2021-12-07

Recording: link to zoom recording

1. Anybody new who wants to introduce him/herself?
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. we did not do this this time.
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. We did not do this this time
   Anybody willing to work on them?
4. Every time: Check if there are new bug reports in JIRA: link

   1. RIC-865 → Done fix unit tests in xapp-frame-py

   2. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build

   3. RIC-862 xapp-frame-py caching of error code data not happening (was: Python RMR Memory Leak)

   4. RIC-861 re-enable RMR libary's module tests

   5. RIC-858 → Done
   6. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   7. RIC-835 → 2021-12-07 news from Viktor
   8. RIC-836 → Done
   9. RIC-837
   10. RIC-840
   11. RIC-852
   12. anybody would like to get more familiar with RMR?
   13. Can Alexandre help with the RMR bug RIC-858?
5. Action items
   1. SCCL update - Matti will check with Tracy
      
      1. still discussion within O-RAN-SC still ongoing
      2. publication of O-RAN specs of July train should happen any time now.
      3. O-RAN specs of July train have been released. Need to check if any parts have been put under SCCL
   2. E2 simulator seeing E2 setups not passing through: 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). Amit raised RIC-852 for this.
      1. 2021-12-07 no news from Nokia side.
6. Expected that we stop development end of November. In Dec-7 meeting we will do status check and after this only exceptional (specially managed) commits to near-RT RIC for the rest of December.
   1. reverting a commit related to simulator in https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/7253
   2. E release images test-deployed. E2 Setup works, xApp deployment. All manual checks.
7. Preliminary planning for the F release
   1. likely not completed in E release (spill over into F): RIC-647, and all from this list.
   2. Candidate list for F release (priority column as per Thoralf's best understanding) https://jira.o-ran-sc.org/issues/?jql=(fixVersion%20in%20(ZZZ_future)%20or%20fixVersion%20in%20(F)%20)AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20%20ORDER%20BY%20component%20ASC
   3. we will discuss this again in two weeks from now.
   4. Thoralf to send a reminder.
8. Thoralf to arrange release demo for Dec-21: Release Demo with e.g. OID, submgr changes and E release example deployment
9. RICAPP agenda: RICAPP Meetings.

2021-11-23

Recording: link to zoom recording

1. 1. RIC-837 RMR is not forwarding messages from E2T to E2M
   2. RIC-835 → 2021-12-07 no news from Viktor
   3. 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: 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.
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. 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
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: 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.
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: 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: 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.
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

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. Anybody new who wants to introduce him/herself?
4. 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/sdlgo/+/7017 ok
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7074 ok
   3. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/7088 ok
   4. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/7087 ok
   5. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/7103 ok
5. 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-09-30 → 2021-11-22)
   4. ric-plt/appmgr 0,0 → 17,5 // 1 major bug ( 2021-09-30 → 2021-11-22)
   5. ric-plt/e2mgr 88,0 // no bugs (2021-09-28 → 2021-11-18)
   6. ric-plt/lib/rmr 86,1->70,4 // no bugs (2021-09-07 → 2021-11-23) → raise bug
   7. ric-plt/sdlgo 47,4 → 32.4// no bugs (2021-09-28 → 2021-11-23) → raise bug
   8. ric-plt/submgr 44,8  → 47,4// no bugs (2021-09-30 → 2021-11-22)
   9. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-08-10 → 2021-11-16)
   10. ric-plt/tracelibgo 94,7//0 bugs (2021-09-30 → 2021-11-22)
   11. ric-plt/xapp-frame 0,0 // no bugs (2021-09-30 → 2021-11-22) - same as before.
   12. ric-plt/xapp-frame-cpp 96,3 // still 2 blocker bugs (2021-09-22->2021-11-17)
   Anybody willing to work on them?
6. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-858 → new
   2. RIC-835
   3. RIC-836 → Done
   4. RIC-837
   5. RIC-840
   6. RIC-852
   7. RIC-857
   8. anybody would like to get more familiar with RMR?
   9. Can Alexandre help with the RMR bug RIC-858?
7. Action items
   1. SCCL update - Matti will check with Tracy
      
      1. still discussion within O-RAN-SC still ongoing
      2. publication of O-RAN specs of July train should happen any time now.
   2. E2 simulator seeing E2 setups not passing through: 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). Amit raised RIC-852 for this.
   3. DONE-2021-11-23 James (INT PTL): Sent email to PTLs on what is needed. Need automation of testing for all projects.
      1. Any comments?
      2. VES alarm events, for example (James)
      3. James: non-rt RIC - near-RT RIC integration A1. Discuss With Sunil/Matti/James, e.g. TS xApps has disabled code for this.
      4. A1-EI could also be integrated (Subhash raised this)
      5. Ramesh - resue E2 simulator
      6. DONE-2021-11-23: thoralf to start mail thread on this.
8. Expected that we stop development end of November. In Dec-7 meeting we will do status check and after this only exceptional (specially managed) commits to near-RT RIC for the rest of December.
9. Subhash (sent this before the meeting)

   1. E2AP v1.1 support [RIC-640 and RIC-638] : We are working on implementation of RIC-640 and RIC-638. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/6931 https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/7041 https://gerrit.o-ran-sc.org/r/c/ric-plt/nodeb-rnib/+/7050

   2. A1 mediator (Could be moved to F release) (RIC-647): partial implementation is done to support A1-P API which is not enabled yet.

   3. RICDMS (Could be moved to F release) [RIC-714] : Implementation is not yet started only we have finalized the API.

   4. RICCTL (Could be moved to F release) [RIC-445] : Pushed some sample commands for A1-P related operations. We are discussing with our internal team to use code from ONAP community which is taking little time.

10. Preliminary planning for the F release
    1. likely not completed in E release (spill over into F): RIC-647, and all from this list.
    2. Candidate list for F release (priority column as per Thoralf's best understanding) https://jira.o-ran-sc.org/issues/?jql=(fixVersion%20in%20(ZZZ_future)%20or%20fixVersion%20in%20(F)%20)AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20%20ORDER%20BY%20component%20ASC
    3. we will discuss this again in two weeks from now.
11. 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
    2. I understand that we updated this together with the Ubuntu 20.04 update during the last two weeks.
12. Nitin: installation using helm3.
    1. Sangeetha: this should be possible since Cherry. Helm charts are the same.
13. Calico should also work.
14. Sangeetha asked for bug reports if any help is needed. Thoralf commented that before starting to work check with Thoralf if already someone working on the item.
15. RICAPP agenda: RICAPP Meetings.

2021-11-09

Recording: link to zoom recording

1.  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
       
2. 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
3. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
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
5. 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
6. Abhijit updates (subteam-ag) ?
   1. Anybody new who wants to introduce him/herself?
      1. GG (Parallel Wireless): wants to participate and possible contribute
      2. Viktor (contractor for globallogic/ARM) working on the ARM64 port
   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/sdlgo/+/6887 ok
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/6832 ok
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/6939 ok
      4. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/6966 ok
      5. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricctl/+/6963 ok, yaml only
      6. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/6915 ok
      7. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2/+/6931 ok, asn1c output only
      8. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/6964 ok, yaml only
      9. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdlgo/+/6958 ok
      10. 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
      11. 1. https://gerrit.o-ran-sc.org/r/c/ric-plt/
          sdlgo
          1. ric-dep/+/
          7006 ok
          1. 11743 
          2. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it.
   3. 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
   4. 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.
   5. 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

   6. 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
   7. Nokia (subteam-n)
      1. ...
   8. 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. 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?
   3. Every time: Check if there are new bug reports in JIRA: link
      1. RIC-835
      2. RIC-836 → Done
      3. RIC-837
      4. RIC-840
      5. RIC-852
      6. RIC-857
      7. anybody would like to get more familiar with RMR?
         1. Alexandre offered to help a bit and would like to get familiar with RMR.
   4. Action items
      1. SCCL update - Matti will check with Tracy
         
         1. still discussion within O-RAN-SC still ongoing
         2. publication of O-RAN specs of July train should happen any time now.
         3. no news (2021-11-23)
      2. E2 simulator seeing E2 setups not passing through: 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). Amit raised RIC-852 for this.
         1. 2021-11-23: still open as we focus on RMR - E2T case
      3. James (INT PTL): Sent email to PTLs on what is needed. Need automation of testing for all projects.
         1. Any comments?
         2. VES alarm events, for example (James)
         3. James: non-rt RIC - near-RT RIC integration A1. Discuss With Sunil/Matti/James, e.g. TS xApps has disabled code for this.
         4. A1-EI could also be integrated (Subhash raised this)
         5. Ramesh - resue E2 simulator
         6. TODO thoralf to start mail thread on this.
         7. 2021-11-23: Thoralf to send
   5. Thoralf recorded a 24min step-by-step video on how to deploy the Dawn release: 2021-11-05 Demo video release Dawn
      1. anybody has time to do part of the demo with public E2 simulator?
   6. Expected that we stop development end of November. In Dec-7 meeting we will do status check and after this only exceptional (specially managed) commits to near-RT RIC for the rest of December.
   7. Arm port (do we need Jenkins CI jobs?)
      1. new merge requests
      2. RIC-835 - Viktor offered possibility of access to ARM hardware if needed (Subhash said restarting the componet helps)
   8. Preliminary planning for the F release
      1. likely not completed in E release (spill over into F): RIC-647, and all from this list.
      2. Candidate list for F release (priority column as per Thoralf's best understanding) https://jira.o-ran-sc.org/issues/?jql=(fixVersion%20in%20(ZZZ_future)%20or%20fixVersion%20in%20(F)%20)AND%20project%20%3D%20%22Near%20Realtime%20RAN%20Intelligent%20Controller%22%20%20ORDER%20BY%20component%20ASC
   We did not discuss this today: 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.A1-Med is using 1.16; others need to be checked
   10. RICAPP agenda: RICAPP Meetings.

   Older meeting minutes

   check from here: Project meetings (old)

   ...