...

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

Zoom 1 Info:

...

...

2024-

...

04-

...

23

Recording: TODO

1. note the presentations on RIC and xApps from ONeS (link) and in O-RAN.
2. How do we plan work for Dawn. Thoralf proposes 1h planning meeting where we collect input from all possible contributors.
   1. We also look at the current draft/wish list cherry_and_dawn_near_rt_ric.pptx
   2. Thoralf to ask for wishes from Martin S.

2020-09-29

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_09_29_part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2020_09_29_part2.mp4

1. reminder on next demo: 2020-10-15 Cherry R6.2 . Pls. add anything you want to demo there.
2. RIC-360 any progress. Discussion with Nune and Nithin kept?
   1. deployment script changes (Abdulwahid) related to helm3. Discussed with Felix (onboarder (felix)  changes still needed).
   2. appmgr changes no discussion → Nune
   3. Thoralf to invite meeting with Alok + Sri + ramesh (still this weeks)
   4. Status: working on go code changes in appmgr
3. RIC-509
   1. subitems being worked on by LF next.
   2. Status: Created Jira tickets for each component under the EPIC: (e.g. RIC-648, RIC-649, RIC-650) & submitted Gerrit change requests to these three tickets.
4. RIC-109: since Jussi on holiday pls. involve Timo T (another committer for dbaas). Status:Converted the k8 manifest files into helm chart. Creating documentation other artifacts as discussed on the call with ORAN SPOCs.
5. RIC-249 (of RIC-95) currently blocked by XML-to-PER conversion of RIC_SERVICE_UPDATE_ACK.
   1. Thoralf still to test the 1-week old code that Rahul wrote (RIC-248)
   2. This now hangs with Adi.
   3. Also another issue is how an empty RIC Service Query/update would look like. ASN.1 is also a bit unclear.
6. RIC-203 is still in team S1 or currently nobody planning to work on this?
   
   1. Rahul might be able to work on this, but earliest decision on this in next meeting.
7. RIC-150 (RIC benchmark) Status: Able to exchange RIC Subscription Request & Response between HW xAPP and E2 Simulator (Action type - Report). Now working on handling RIC Indication message exchnage between HW xAPP & E2 Simulator
8. RIC-149 (more tests) Status: 1) RIC deployment Testsuite: RIC deployment testing is done. Need to send the code for review. 2) Healthcheck Testsuite: O1mediator issue is fixed. Created interface.robot and verified the log for this component. dbaas - ping pong test is in progress. submgr - Unable to proceed due to ClusterIP issue. We sent query to Dave on this. 3) ETE Testsuite : robotxapp deployment is in progress.
9. some items postponed from Cherry to Dawn: RIC-585 (the alarm for E2 connection loss) , RIC-139 (O1 adapter to summarize platform health state) , RIC-421 (O1 mediator graceful restart)
10. Subhash xApp demo can be in platform code. Subhash would like to discuss this.
11. RICAPP agenda: RICAPP Meetings.

2020-09-15

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_09_15.mp4

1. Schedule for R6 (second half of Cherry: Jira usage conventions → §6).
2. demos for demo day (next week Thursday = Sep-24 in 2020-09-24 Cherry R6.1 - CANCELLED)
3. Subhash: move on with exact contribution.
   1. [1] Higher abstraction level in xAPP framework SDK (golang) [https://jira.o-ran-sc.org/browse/RIC-366]
      1. We discussed possible abstraction of this on API level. Matti said one person on AT&T side has been working on this before. We need to set up a separate meeting on this: Subhash, Nune, Matti, Neeraj Gupta (HCL), Vaishali (HCL), h_w.park@samsung.com, Akash (bouncer xapp) Identify new capabilities that we can implement on xapp framework side. Focus on things not yet implemented in any xapp frameworks. presentation by  h_w.park@samsung.com on what is planned. Aim for 10am EDT (NewYork) on Monday, Sep-21
      2. RIC-80 is already in progress by Antti teams.
      3. general goal xApps should only rely on E2SM, but do not need to touch E2AP messages (using ASN.1). So, a good abstraction would allow xApp implementation without ever touching an ASN.1 compiler if an E2SM would be defined in something else than ASN.1. We can discuss this further in the Monday meeting.
   2. [2] Support for E2AP RESET procedure  [https://jira.o-ran-sc.org/browse/RIC-383]
   3. [3] Developing version of xAPP [https://jira.o-ran-sc.org/browse/RIC-120]
      1. existing "hello world" is C++, but does more than just saying "Hello world", e.g. has own service model. Additional demo xapps in go/python are welcome. For go see in xapp-framework for Go for some skeleton code.
      2. for example, it would be good to have E2SM support for "hello world" E2SM in the simulator.
4. Alok RIC-509 works better with Ceph (instead of NFS). Meeting to discuss how to integrate this to be called by Alok.
5. Akash asked about the hello world xApp in terms of a new bouncer xApp (for benchmarking). Pls. contact Matti to get you in contact with hello world expert. Akash to attend also the Monday meeting.
6. (post-meeting addition): Ron now merged the patch into the E2 simulator: https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/4700 Work on the simulator can now continue.
7. (post-meeting addition): RIC-360: continued work on appmgr // RIC-509: testing JJB templates in sandbox (sandbox permissions obtained) // RIC-150 Able to send RIC Subsription Request message from Bouncer xAPP to E2 terminator. Working on handling of the RIC Subsription request message at E2 terminator to E2SIM. Debuging is in progress. Able to exchange E2 Setup request and response. RIC-149: Ricdeployment Testsuite - existing issue got fixed except statefulset, working on this. Sent code modification to Dave and Bharath for review. Healthcheck Testsuite - Interface.robot files missing for few components got fixed and added keyword healthcheck for missing components as well. Working on dbaas, submgr related inerface.robot parameters to add and test. E2E Testsuite: Working robotxapp deployment using http post request using both manual and robot automation.
8. RICAPP agenda: RICAPP Meetings.

2020-09-01

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_09_01.mp4

1. S1+S2 team any news?
   1. Rahul progressing on RIC-95. Thoralf will help with testing as E2 simulator is needed.
   2. Subhash interested in picking up items on near-RT RIC platform. Thoralf to send information package.
   3. Double-check progress on E2 simulator in simulator project. Action item-Matti: check with Ron. Make sure to to add copyright and license statement.
   4. RIC-372 (sdlpy now supports notifications) now done.
2. H1 team any news?
   1. RIC-109 (helm/k8s upgrade) Working on Non NFS based cluster storage on k8s
   2. RIC-509: HCL to present output/status of RIC-509.
      
      1. analysed com-pylog project on sonarcloud using our a/c
      2. Matti noted that xApp's MC xapp has done the same. Always needs to involve LF support case. HCL to include Matti in discussion.
   3. RIC-360: Go lang based code changes in progress
   4. RIC-150: (e2e benchmarking) Working on the Bouncer xAPP Implementation. "successfully built the e2apv1sim code manually in the LAB and run the e2sim binary. The e2sim sending the E2 setup request message to RIC terminator. The RIC terminator received the E2 setup message and it is not sending the response to e2sim. Because, in decode part of E2 setup request message in RIC, some parameters(RANfunction_Item) are not handled in RIC side and it's giving the decode error."
   5. RIC-149 (testing): Started fixing up the health check of ric component testsuites with few missing keywords and missing riccomponent_interface.robot files. As we confirmed with Bharath and Dave we are proceeding to fix the healthcheck and e2e testsuites related issues. Status: In progress Issue: Currently working on this while adding a1mediator interface.robot file " <tpl ($content).AsConfig $>: error calling tpl: Error during tpl function execution for "a1mediator.robot". Due to this some component related files are not mounted to nanobot pod. 
3. alarms implemented in Cherry → check status with owners of sub user stories in

   Jira
   server ORAN Jira serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key RIC-56

   (check with owners of 585 203 and 204). Contact Nune
4. to discuss this reply to Jinri's request: https://lists.o-ran-sc.org/g/main/message/812
   1. reply: " from near-RT RIC side we work with: (1) Akraino REC as the Akraino blueprint that we integrate RIC with (2) Nokia investigating if we can provide a wireshark dissector for E2AP (pending discussion with O-RAN alliance) (3) We're using the VESPA (Prometheus to VES adapter) project.
5. Anything to demo on Thursday? Matti (50/50)?
6. RICAPP agenda: RICAPP Meetings.

2020-08-18 special meeting on E2 simulator

Recording: 2018_08_18_special_meeting_on_e2_simulator.mp4 (no meeting notes created)

2020-08-18

Recording: 2 parts: near_rt_ricplatform_and_ricapp_meeting_2020_08_18_part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2020_08_18_part2.mp4

...

The below projects are onboarded to SonarCloud but not scanned. 

ric-plt-e2 ric-plt-sdlgo ric-plt-xapp-frame ric-plt-appmgr ric-plt-dbaas ric-plt-dbaas-hiredis-vip ric-plt- nodeb-rnib ric-plt-submgr ric-plt-utils ric-plt-jaegeradapter ric-plt-tracelibcpp ric-plt-tracelibgo ric-plt- vespamgr ric-plt-asn1-documents ric-plt-streaming-protobufs ric-plt-ric-test ric-plt-ric-dep ric-plt-demo1

not in sonar: com-golog com-pylog com-gs-lite

...

Project name in SonarCoud

...

Vulnerabilities

...

Coverage

...

Last scan

...

ric-plt-alarm-go

...

0

...

38.8

...

8/5/2020

...

ric-plt-lib-rmr

...

0

...

73.6

...

8/3/2020

...

ric-plt-lib-rmr-c (old code, old job not in use anymore)

...

10

...

42

...

3/29/2020

...

ric-plt-lib-rmr-py

...

0

...

0

...

4/5/2020

...

ric-plt-rtmgr

...

0

...

77.5

...

8/5/2020

...

ric-plt-sdl

...

1 - minor

...

66.6

...

7/30/2020

...

ric-plt-xapp-frame-cpp

...

0

...

94.3

...

3/25/2020

...

com-log

...

3

...

89.9

...

8/5/2020

Note that Matti and scot are trying to remove the old job info sonarcloud. ric-plt-lib-rmr-c

...

1. RIC-114 scope change

...

1. Routing Manager now supports route distribution to multiple RMR control ports.

...

1. E2M - Get node list API changed and now return also the node connection status - completed. Swagger : https://wiki.o-ran-sc.org/display/RICP/E2+Manager+REST+API+Swagger

2. Publish SDL event in case Connection Status is changed - Testing is completed - waiting for further testing with some sample xApp from Nokia

3. Publish SDL event in case gNB is added/updated/deleted - in progress

4. E2T Prometheus implementation - completed (including review and testing)

...

1. O1 APIs (O1-PM/FM/CM) in C++ framework completed - see demo from last week // python framework demo was done earlier in Cherry.
2. E2 Simulator work still ongoing (Ron doing cleanup work). Ron will give presentation about simulator code in meeting with Samsung/HCL/ATT/Nokia after this meeting.
3. RMR-to-VES event adapter for statistics implemented

...

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
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 - Done, still some issues are seen, to further check and report issue.
   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, duplicate of 1052(DONE)
      
   8. RIC-1047 crash in E2T metric increment code - WIP
   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  - WIP
   12. RIC-1042 Can't register xApp
   13. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation - Mostly fixed, To be confirmed by Abhijit.
   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.
   7. 2024-04-23:
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,2024-04-23: 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 - Done
      
   10. 2024-03-09: Absent
   11. 2024-04-23: Not much updates.
       
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,2024-04-23: 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.
      
   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.
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,2024-04-23: 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.
    6. 2024-04-23: Not present
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,2024-04-23: 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,2024-04-23: 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,  to include k8s version upgrade, clean up of pending issues.
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-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. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
   2. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04 - To be assigned to Sunil
   3. RIC-1047 crash in E2T metric increment code 
   4. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   5. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   6. RIC-1043 Crash in E2T buildPrometheusList Function 
   7. RIC-1042 Can't register xApp
   8. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   9. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   10. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   11. RIC-1025 memory leak in routing manager
   12. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

   17. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
   18. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
   19. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   20. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/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"
   28. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
   29. RIC-837 RMR is not forwarding messages from E2T to E2M
   30. RIC-835 → 2021-12-07 no news from Viktor
   31. 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: 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.
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)
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
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: 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.
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: 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: 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.
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-03-12

Recording:  link to zoom meeting

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on (end of I release)
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04
   2. RIC-1047 crash in E2T metric increment code 
   3. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   4. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   5. RIC-1043 Crash in E2T buildPrometheusList Function 
   6. RIC-1042 Can't register xApp
   7. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   8. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   9. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   10. RIC-1025 memory leak in routing manager
   11. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

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

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

2024-02-13

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on (end of I release)
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. new RIC-1047 crash in E2T metric increment code 
   2. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
   3. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
   4. RIC-1043 Crash in E2T buildPrometheusList Function 
   5. RIC-1042 Can't register xApp
   6. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   7. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   8. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   9. RIC-1025 memory leak in routing manager
   10. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

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

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

2024-01-30

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on 2023-09-26
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix 
   2. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr 
   3. RIC-1043 Crash in E2T buildPrometheusList Function 
   4. RIC-1042 Can't register xApp
   5. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   6. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   7. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
   8. RIC-1025 memory leak in routing manager
   9. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

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

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

2024-01-16

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on 2023-09-26
      1. TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
   2. RIC-1031Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
   3. RIC-1032 → RIC-1035 - we cpontinue with this under RIC-1035 (discussed with Abhijit in the project meeting)
   4. RIC-1025 memory leak in routing manager
   5. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

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

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

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

      3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
   2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
    2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
    3. 2023-11-21: as discussed in teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
    4. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    5. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
11. Dhiraj (subteam-r)
    
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be commited now obtained. IPv6-related commits expected over teh next weeks.
12. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
13. Nokia (subteam-n)
    1. RIC-997 postponed to J
14. J release
    
    1. We mark items that you are >90% sure (=”committed”) to work on during 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for J release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
       1. Example Nokia J release: link

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

1. RICAPP agenda: RICAPP Meetings.

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

2023-12-05

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on 2023-09-26
      1.  https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11898 OK (simple alarms, but we created RIC-1028 for a more general test mock framework)
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 OK, since deployment acts as test
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12025 ok, lots of code, but very generic. Naman will try to add test case
      4. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/12032 OK, only go.sum file
      5. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/11895 OK (simple alarms, but we created RIC-1028 for a more general test mock framework)
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-05-23:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1025 memory leak in routing manager
   2. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

   7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   8. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look
   9. RIC-991 CVE-2023-40997 RMR related (not a duplicate) - Alexandre will take a look
   10. RIC-989 CVE-2023-40998 RMR (minor) security issue - Alexandre will take a look
   11. RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED
   12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   13. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   14. RIC-915 dms_cli for installing xapp not working (raised by James)
   15. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   16. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   17. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   18. RIC-894 long idle period (days) causes RMR connection breaks
   19. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   20. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   21. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
       1. 2021-12-21: Trying to get bandwidth for this during F release.
   22. RIC-837 RMR is not forwarding messages from E2T to E2M
   23. RIC-835 → 2021-12-07 no news from Viktor
   24. fixed:
       
4. James: updates?
   1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
   2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
      1. ODU-high and near-RT RIC (currently using stub).
      2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
      3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
      4. James will check with Sunil on issues he has with the test cases
      5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar could be done with OSC.
   3. 2023-10-24
      1. updates from O-RAN f-2-f:
         1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
         2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
            1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
            2. more discussion coming at the joint OSC/OAI workshop in Boston
         3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
      2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
   4.  2023-11-07
      1. James is working with Taiwan lab on making sure we have good coverage
   5. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
   2. 2024-01-16
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
   4. 2024-01-16: no news. Wants to re-valuate tickets (earlier assigned to HCL).
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-08-29: no news, other than Naman working on the operator implementation.
   2. 2023-09-12:
      1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
      2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
         1. Thoralf sent instructions to John → DONE
      3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
      4. Naman also works on the operator implementation
   3. 2023-09-26:
      
      1. kubernetes operator new repo needed or not?
         1. xapp deployment → appmgr or ricdms
         2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
      2. What happened to kserve adapter? → Subhash can check.
   4. 2023-11-07
      1. Naman presented his k8s operator work. Naman used Kubebuilder
      2. still working on operator to deploy RIC platform
   5. 2023-11-21:
      1. k8s operator commits - needs to be finalized.
   6. 2023-12-05: Naman gave an update on status of Samsung items
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia
         
      4. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      5. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-11-07: after discussions on the topic we would like to proceed with

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

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

      3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
      4. TODO-thoralf-to-ask-Gunja-to-present- Thoralf
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
    2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
    3. 2023-11-21: as discussed in teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
    4. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
11. Dhiraj (subteam-r)
    
    1. 2023-08-22:
       1. checking compliance/license issues
       2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
    2. 2023-08-29:
       1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes

    3. 2023-11-07

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

    4. 2023-12-05: moved the IPv6 item  to J release
12. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
13. Nokia (subteam-n)
    1. RIC-997 postponed to J
14. Demo
    1. We will use the project meeting slot for the demos
    2. Naman to demo k8s operator deployment of platform (xapp part already done) and also A1 creating a policy.
    3. Adding support for DU in E2T/E2M/RNIB - >thoralf can do if not Gunja.
       
15. I release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.

1. 1. input for release candidates: left overs and generally open items, RSAC
   2. Sprint dates
      1. Sprint I release dev sprint 1: Aug-21 to Sep-10
      2. Sprint I release dev sprint 2: Sep-11 to Oct-1
      3. Sprint I release dev sprint 3: Oct-2 to Oct-22
      4. Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
      5. Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
   3. Plan (v03 as of 2023-08-18):
      1. I release plan moved to I release page.
      2. Thoralf will start generating images next week (Dec-11 - Dec-13)
2. RICAPP agenda: RICAPP Meetings.

2023-11-21

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on 2023-09-26
      1.  TODO
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-05-23:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1025 memory leak in routing manager
   2. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

   7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   8. RIC-1001 RMR service should verify route tables - Alexandre will take a look
   9. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
   10. RIC-989 RMR (minor) security issue - Alexandre will take a look
   11. RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED
   12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   13. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   14. RIC-915 dms_cli for installing xapp not working (raised by James)
   15. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   16. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   17. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   18. RIC-894 long idle period (days) causes RMR connection breaks
   19. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   20. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   21. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
       1. 2021-12-21: Trying to get bandwidth for this during F release.
   22. RIC-837 RMR is not forwarding messages from E2T to E2M
   23. RIC-835 → 2021-12-07 no news from Viktor
   24. fixed:
       
4. James: updates?
   1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
   2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
      1. ODU-high and near-RT RIC (currently using stub).
      2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
      3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
      4. James will check with Sunil on issues he has with the test cases
      5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar could be done with OSC.
   3. 2023-10-24
      1. updates from O-RAN f-2-f:
         1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
         2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
            1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
            2. more discussion coming at the joint OSC/OAI workshop in Boston
         3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
      2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
   4.  2023-11-07
      1. James is working with Taiwan lab on making sure we have good coverage
   5. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
   3. 2023-11-21: no updates. Difficult to find engineers working on this.
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-08-29: no news, other than Naman working on the operator implementation.
   2. 2023-09-12:
      1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
      2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
         1. Thoralf sent instructions to John → DONE
      3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
      4. Naman also works on the operator implementation
   3. 2023-09-26:
      
      1. kubernetes operator new repo needed or not?
         1. xapp deployment → appmgr or ricdms
         2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
      2. What happened to kserve adapter? → Subhash can check.
   4. 2023-11-07
      1. Naman presented his k8s operator work. Naman used Kubebuilder
      2. still working on operator to deploy RIC platform
   5. 2023-11-21:
      1. k8s operator commits - needs to be finalized.
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
         
      3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia
         
      4. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      5. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-11-07: after discussions on the topic we would like to proceed with

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

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

      3. discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
      4. TODO-thoralf-to-ask-Gunja-to-present- Thoralf
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
    2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
    3. 2023-11-21: as discussed in the beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
11. Dhiraj (subteam-r)
    
    1. 2023-08-22:
       1. checking compliance/license issues
       2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
    2. 2023-08-29:
       1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes

    3. 2023-11-07

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

12. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
13. Nokia (subteam-n)
    1. .RIC-997 likely being postponed.
14. I release content

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

      1. 
         

2. RICAPP agenda: RICAPP Meetings.

2023-11-07

Recording: link to zoom recording

1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
   1. Last checked on 2023-09-26
      
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 ok, (not yet merged)
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11889 ok. included test cases
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/ricdms/+/11999 actually small changes, but as this is generated code, no need for test cases. Actually hand-written code is coming in another review together with test code.
2. every second time: Review code coverage stats and blocker code smells
   1. We take a look at the two links in the beginning of this page: Code coverage reports..
   2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
   3. Thoralf did this last on 2023-05-23:  we did not do this this time
3. Every time: Check if there are new bug reports in JIRA: link
   1. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

   6. RIC-1009 E2Mgr API can be improperly invoked → TODO-thoralf-converted-this-to-Epic
   7. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
   8. RIC-1001 RMR service should verify route tables - Alexandre will take a look
   9. RIC-991 RMR related (not a duplicate) - Alexandre will take a look
   10. RIC-989 RMR (minor) security issue - Alexandre will take a look
   11. RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED
   12. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
   13. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
   14. RIC-915 dms_cli for installing xapp not working (raised by James)
   15. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
   16. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
   17. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
   18. RIC-894 long idle period (days) causes RMR connection breaks
   19. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
   20. RIC-857 sporadically RMR takes multiple minutes before being "ready"
   21. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
       1. 2021-12-21: Trying to get bandwidth for this during F release.
   22. RIC-837 RMR is not forwarding messages from E2T to E2M
   23. RIC-835 → 2021-12-07 no news from Viktor
   24. fixed: RIC-972
       
4. James: updates?
   1. 2023-09-12: requested from PTLs pair-wise testing. From Near-RT RIC point of view we hope for the non-RT RIC project to initiate testing with A1 mediator standalone version.
   2. 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
      1. ODU-high and near-RT RIC (currently using stub).
      2. near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
      3. near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
      4. James will check with Sunil on issues he has with the test cases
      5. ArgoCD used by Taiwan lab in some ONAP SMO  case and the engineers there where wondering if something similar could be done with OSC.
   3. 2023-10-24
      1. updates from O-RAN f-2-f:
         1. nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
         2. OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
            1. see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
            2. more discussion coming at the joint OSC/OAI workshop in Boston
         3. session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
      2. OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
   4.  2023-11-07
      1. James is working with Taiwan lab on making sure we have good coverage
5. Prashant's work in near-RT RIC(subteam-p)
   1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
6. Sunil updates (subteam-h)?
   1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
   2. 2023-11-07: Not in the call today
7. Subhash/Naman updates (subteam-s) ?
   1. 2023-08-29: no news, other than Naman working on the operator implementation.
   2. 2023-09-12:
      1. We had a meeting with John and Denis on non-rt RIC compatibility. Agreed in fixes for URL and policystatusobject type from integer→string (as per standard) → Naman.
      2. Thoralf to figure out a way to start A1 mediator standalone for CI testing
         1. Thoralf sent instructions to John → DONE
      3. current implementation of /data-delivery URL in A1 - need to check if >1 consumer of EI data (sent by non-RT RIC) works on our side.
      4. Naman also works on the operator implementation
   3. 2023-09-26:
      
      1. kubernetes operator new repo needed or not?
         1. xapp deployment → appmgr or ricdms
         2. ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
      2. What happened to kserve adapter? → Subhash can check.
   4. 2023-11-07
      1. Naman presented his k8s operator work. Naman used Kubebuilder
      2. still working on operator to deploy RIC platform
8. Abhijit updates (subteam-ag) ?
   1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0
         
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 
      3. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it.
9. Cap Gemini updates (subteam-cg)? 
   1. 2023-11-07: after discussions on the topic we would like to proceed with

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

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

      3. TODO-thoralf-to-ask-Gunja-to-present
10. Himanshu (subteam-gs) would like to work on RIC-963
    
    1. 2023-08-29: ready for merging once the CI problem (gofmt) is fixed. Can be merged together with a change in the helm chart (ric-dep). Default behavior is "strict order" (as currently). But config value can change to "any order".
    2. 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
11. Dhiraj (subteam-r)
    
    1. 2023-08-22:
       1. checking compliance/license issues
       2. How are policy types created? xApps register by policy type and understands the schema that is bound to it. Non-RT RIC should create policies using the same schema (there's a GUI for this on non-RT RIC side).
    2. 2023-08-29:
       1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes

    3. 2023-11-07

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

12. Alexandre (subteam-utfpr)
    
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
13. Nokia (subteam-n)
    1. ...
14. I release content

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

...

2020-08-04

Recording: video+audio from the first 44 min (near_rt_ricplatform_and_ricapp_meeting_2020_08_05.mp4) and the last 14 minutes only as audio (near_rt_ricplatform_and_ricapp_meeting_2020_08_05.m4a)

1. Note updates in E2APv01.01 compared to E2APv01.00, e.g., related to config transfer and TNL (failover, scalability).
2. progress by subteams
   1. RIC-95 - currently blocked by IPR checks on Samsung side.
   2. Rahul mentioned integration test setup issues. One option is to ask fro help from Tel Aviv. E2 Sim is the other option. Samsung exploring options to make testing easier.
   3. Arun (from Samsung) not working for RIC anymore. Subhash replacing him.
   4. Simulator key contacts: Bharath, Ron shacham, Thoralf . Thoralf send a e-mail to Subhash as he was interested in this.
   5. RIC-109 call with Jussi done. Problem understood and how to do it. Next step how to distribute in K8S for efficient failover.
   6. RIC-360 helm and K8S (1.16 → 1.18) upgrade. Issues with one of the docker images for app manager. Trying to update the code for helm3. Alok did install on K8S 1.18. Did not find any issues.
   7. Thoralf to schedule a meeting with Ron, Rahul (Samsung), Subhash (Samsung), Ramesh (HSL), Sangeetha  (HCL), Alex with Ron introducing his vision on how to implement additional messages in teh E2 simulator. Also Bharath.
3. Thoralf to think how to report Nokia and AT&T progress
4. RIC app meeting

2020-07-21

Recording: near_rt_ricplatform_and_ricapp_meeting_2020_07_21.mp4

1. Matti hosts this meeting as Thoralf is on holiday
2. Thoralf added subteams S1, S2, H1 to Jira usage conventions. Check also §1e from the same wiki page on how they are used in JIRA.
   1. Alok: Helm 2→3, identified key areas, helm commands not supported, validation errors, tiller not supported in Helm 3, Zhe Huang
   2. Matti will introduce Alok (alok_bh@hcl.com) to Felix
   3. Alok: RIC-360 - who can provide detailed user stories - Matti will check with Felix first, then Thoralf when he is back
3. Next demo will be on Thursday, 2020-07-23 Cherry R5.3. Anything to demo?
4. RIC app meeting

2020-07-07

Recording: near_rt_ric_platform_project_meeting_2020_07_07.mp4

1. Recording of Jul-2 demo: TODO (pending Matti)
2. Thoralf on holiday Jul-21. The Jul-7 meeting we still have normally. Matti (hiltunen@a...) to host the Jul-21 meeting.
3. After discussion with xApp PTL (Matti), we will use the old existing empty repo "utils" as a general repo for small utility-like code. The first usage will be for RMR-to-VES mediator (event converter) "platform xapp". This work is done under RIC-420.
4. discuss contributions by HCL .

   1. Assign to Alok Bhatt:

      1. ricp-integration RIC-360: plan and prototype helm upgrade with xApp manager, REC, RIC infrastructure

                      Which K8S version with Helm 3 support to move to? Is 1.18 confirmed? Yes

                      App owners with whom we need to work with for this co-existence of Helm 2 and 3 change and for doing post deployment check / sanity testing? xapp manager, it-dep, ric-dep, Schedule meeting with Lusheng and Felix, Abdulwahid.

      1. ricp-e2e RIC-509: Components supporting continuous integration infrastructure, e.g., static code analysis. Schedule meeting with Lusheng

      Pl share more info on LF CI/CD. Sonarcloud or SonarQube? Jenkins Job Builder / Chained CI?Schedule meeting with Lusheng

      1. DBaaS RIC-109: DB: study: SDL scaling with Redis cluster (instead of sentinel) Schedule meeting with Jussi.

      App owners with whom we need to work with for doing this before and after comparison for this move from Sentinel to Redis Cluster mode? Should be transparent to user

      Output format expected from this study, if any

      Assign to Sangeetha KR:

      1. ricp-e2e RIC-149: Define and implement automated test cases for flows to be defined early in Bronze-R4
      2. ricp-e2e RIC-150: Perform e2e RIC benchmarking

      Pl connect us with Bharath Balasubramanian on these items.

   2. Pl enable community lab access for us to work on these. → connect with Lusheng for how to use TLab.

   3. We manage this existing team mapping, but the items are assigned to Alok and Sangeetha.
5. discuss contributions by Samsung

   1. For now, we would like to get your opinion regarding adding pub-sub feature to sdlpy/xapp-frame-py. As far as I know, this feature is already exists in sdlgo, but there seems to be no ticket related to this feature.

   2. This would be item RIC-372. Note that this is not related to xapp-frame-py, but to sdlpy only. Thoralf to reply to Timothy John Ebido. 
   3. item in JIRA to be assigned to him. Note that right now we have notifications only in go, but not in python or C++.
6. ricapp meeting

2020-06-23

Recording: near_rt_ric_platform_project_meeting_2020_06_23.mp4

1. Demo day is Jul-2, 9am ET: 2020-07-02 Cherry R5.2
2. Thoralf on holiday Jul-21. The Jul-7 meeting we still have normally.
3. Bengi asked for RMR performance data comparing old NNG against SI95 implementation. Nothing on wiki page, but we have the PDF in

   Jira
   server ORAN Jira serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key RIC-48

   that might help. Matti to ask Scott to eventually post the results also in the wiki page. Also to double-check that SI95 results are not already in wiki page somewhere.
4. Chokha interested in contributing to near-RT RIC.
5. Rittwik asked about what we should push to the maintenance release. So far nothing. Matti asked about adding alarm routes to routing manager. We created

   Jira
   server ORAN Jira serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key RIC-525

   for this.

2020-06-09

Recording: near_rt_ric_platform_project_meeting_2020_06_09.mp4

1. new contributors (Rahul) planning to work on RIC-203 implementation with Abdulwahid and on RIC-133 xApp scalability with Matti.
2. presentation to O-RAN alliance: 2020-06-08: Report to O-RAN alliance on plans for release "Cherry" under Project reports
3. demo moved by one week. We now demo in the first week of a sprint. For Sprint 1 in near-RT RIC we don't have a demo. First one for sprint 2 will be Jul-2.
4. committer change: Tommy → Chris L. (in a1, rmr, xapp-frame-py). Remove rajesh from RMR. Katri and Roni to be removed from all repos. Need a replacement.
5. RICAPP agenda: RICAPP Meetings.

2020-05-26

This event is cancelled due to overlapping workshop. Next meeting will be in two weeks in regular time slot.

2020-05-12

Recording: near_rt_ric_platform_project_meeting_2020_05_12.mp4

1. Review and agree to minutes of previous meetings
2. check RIC-95 status. Quite a lot of work. Code review and unit test cases still to be done.We quickly discussed a possibility of doing healthcheck also via a healthcheck E2SM that woudl have to be defined by O-RAN WG3. We discussed this because in the RICAPPSs Hello World xApp an non-standard E2SM does something similar. Current expectation is that WG3 work will not be picking up this E2SM any time soon.
3. Check for Bronze what we achieved and Cherry-R5 plans: link (check under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12")
4. Rittwik wants to talk about Cherry release planning.
   1. TS use case will probably be expanded on // possibly some ML model management aspects for RIC platform
   2. Rittwik mentioned more work in O1/O2, but for Cherry-R5 we might have issues with standardization not ready yet. More likely Cherry-R6 content.
   3. For scalability on E2AP no plans in R5 because of standardization being blocked. We do have work for xapp scalabilty study in Cherry-R5 and benchmarking planned for Cherry-R5.
5. We might or might not have to cancel the next meeting due to overlapping workshop. I will update the groups.io calendar if it's cancelled.
6. postponed items (out of Bronze): RIC-76 (subscription manager) and many more - see Cherry-R5 plans (same link as in (3) above).

2020-04-28

Recording: near_rt_ric_platform_project_meeting_2020_04_28.mp4

1. Review and agree to minutes of previous meetings
2. FYI RICP (combined with RICAPP) demos are every third week: Sprint demos
3. Status of
   1. RIC-95 (design approved by tel aviv teams // implementation should be ready // problem with testing as no access to simulator) Tel Aviv cannot test with proprietary simulator as no time. This might delay RIC-95 further. Harry cannot help as on leave. Ron might get simulator ready within two weeks, but there is some risk that service query is not working yet in simulator. Arunkumar could take a look at the service query support in simulator during next week once RIC-95 is ready. If we make good progress, we could still push this into maintenance release (after TOC approval).
   2. RIC-203 no progress. design not clear yet. Drop this from Bronze (not try to push it into maintenance release)
4. postponed DB items EPICS: (not even started):  RIC-123, RIC-107, RIC-118 and RIC-119 as well as user story: RIC-104 to post-Bronze-R4
5. 2020-04-28: epics still open team 1: 17, team 2: 5, team 3: 3, team 4: 8 : team 5: 10, team 6: 2, team 7: 2. sum = 47 still open
6. FYI: Tommy Carpenter has left the project. Committer upgrade needed. A1, xapp-frame-py → Chris Lott. RMR python version is in xapp-frame-py. RMR also replace tommy with Chris (even if no RMR python work a<nymore), Rpanta also remove from RMR repo. The repo "utils" we should remove. Add Chris now. Remove Tommy after Bronze. Thoralf to initiate this change.

2020-04-14

Recording: near_rt_ric_platform_project_meeting_2020_04_14.mp4

1. Review and agree to minutes of previous meetings
Between "DBAAS" single-instance and "HA" we switch by using same configmap with different content as in this review: https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/3105 For platform components this is a good solution. The idea is that xApps (if they use SDL) have something similar. We might have to expand how this works for xApps later on, e.g., so that xApps have a way to declare what they need in terms of data storage
2. 1. 1. .
3. RICAPP agenda: RICAPP Meetings.

Older meeting minutes

check from here: Project meetings (old)

...