Meeting Info

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:

Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/9644759813
Meeting ID for dial-in: 9644759813

UTC-time	every 2nd Tuesday, check from calendar	https://zoom.us/j/9644759813
New York (EDT / UTC-4 during DST (-5 in the winter))	every 2nd Tuesday, check from calendar	+1 669 900 6833 // +1 646 558 8656 // 855 880 1246 (Toll Free) // 877 369 0926 (Toll Free)
Paris (CEST / UTC+1 in the winter (+2 during DST))	every 2nd Tuesday, check from calendar	+33 7 5678 4048 // +33 1 8288 0188 // 805 082 588 (Toll Free)
Beijing (CST / UTC+8)	every 2nd Tuesday, check from calendar	+86 10 87833177 // +86 10 53876330 // 400 616 8835 (Toll Free) // 400 669 9381 (Toll Free)
Tokyo (JST / UTC+9)	every 2nd Tuesday, check from calendar	+81 524 564 439 // +81 3 4578 1488 // 0 800 100 5040 (Toll Free)
Helsinki (EEST / UTC+2 in the winter (+3 during DST))	every 2nd Tuesday, check from calendar	+358 341092129
Delhi (IST // UTC +5:30	every 2nd Tuesday, check from calendar	TODO
Other international numbers	World Time Zone Map	International numbers available: https://zoom.us/u/acyy3hylQi

2024-04-09

Recording: near_rt_ric_09_04-2024.mp4

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
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
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:
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.
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
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
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
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.
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.
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.
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.
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.
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.
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)
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. 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)
RICAPP agenda: RICAPP Meetings.

2024-03-26

Recording: link to zoom recording

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
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
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:
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.
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
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.
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)
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
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.
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.
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.
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.
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.
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.
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. 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)
RICAPP agenda: RICAPP Meetings.

2024-03-12

Recording: link to zoom meeting

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
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
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:
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.
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
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.
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
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.
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
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.
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.
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
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.
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.
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. 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)
RICAPP agenda: RICAPP Meetings.

2024-02-13

Recording: link to zoom recording

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
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
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:
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)
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
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
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
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
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
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.
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.
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
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.
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. 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)
RICAPP agenda: RICAPP Meetings.

2024-01-30

Recording: link to zoom recording

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
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
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:
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.
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
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
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
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.
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
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.
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.
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
Nokia (subteam-n)
1. RIC-997 postponed to J
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. 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)
RICAPP agenda: RICAPP Meetings.

2024-01-16

Recording: link to zoom recording

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
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
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-1031 Data 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
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.
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
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
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.
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.
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
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.
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.
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
Nokia (subteam-n)
1. RIC-997 postponed to J
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. input for release candidates: left ov left overs ers and generally open items, RSAC
2. Sprint dates
  1. TODO - general timeframe: Jan-June 2024

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

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)
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
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:
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.
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
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).
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
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.
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
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.
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
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
Nokia (subteam-n)
1. RIC-997 postponed to J
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.
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. 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)
RICAPP agenda: RICAPP Meetings.

2023-11-21

Recording: link to zoom recording

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
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
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:
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.
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
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.
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.
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.
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
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.
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
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
Nokia (subteam-n)
1. .RIC-997 likely being postponed.
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.
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.
RICAPP agenda: RICAPP Meetings.

2023-11-07

Recording: link to zoom recording

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.
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
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~~
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
Prashant's work in near-RT RIC(subteam-p)
1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
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
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
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.
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
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.
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
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
Nokia (subteam-n)
1. ...
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.
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.
RICAPP agenda: RICAPP Meetings.

Older meeting minutes

check from here: Project meetings (old)

Show all results

Space shortcuts

Page tree

Meeting Info

2024-04-09

2024-03-26

2024-03-12

2024-02-13

2024-01-30

2024-01-16

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

2023-12-05

2023-11-21

2023-11-07

Older meeting minutes