Versions Compared

Old Version 614

changes.mady.by.user Thoralf Czichy

Saved on

compared with

New Version 745

changes.mady.by.user Abdul Wahid W

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

UTC-timeevery 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:30every 2nd Tuesday, check from calendarTODO


Other international numbers

World Time Zone Map

International numbers available: https://zoom.us/u/acyy3hylQi

...

2024-

...

04-23

Recording: zoom 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-02-28
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/10666 OK
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/10287 OK
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10405 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
        1. 2023-02-28: Abhijit worked with Matt and Sridhar from LF on this. Jobs are now running, but they fail. There's a credential issue. Abhijit to remind Sridhar. Once this is fixed, we can change Dockerfile to install prerequisites.
        2. 2023-03-28: This is OK and is now closed.
    every second time: Review code coverage stats and blocker code smells
  2. We take a look at the two links in the beginning of this page: Code coverage reports..
  3. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    1. (end of I release)
      1. TODO
  4. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
  5. Every time: Check if there are new Thoralf did this last on 2022-05-27, 2022-11-22, 2023-03-28:  we did not do this this timeEvery time: Check if there are new bug reports in JIRA: link
    1. new bug report RIC-9621057gNB unable to connect during high amount of Subscription Requests
    2. RIC-961 (fixed already)

    3. RIC-964 (fixed already)

    4. RIC_966 (fixed already)

    5. RIC-968 (fixed already)

    6. RIC-940 sdlpy missing whitespace → Timo
    7. RIC-939 race conditions in RMR → Abdulwahid
    8. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
    9. RIC-915 dms_cli for installing xapp not working (raised by James)
    10. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    11. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    12. RIC-897 SCTP connection fails with Viavi // update with workaround
    13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    14. RIC-894 long idle period (days) causes RMR connection breaks
    15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    17. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
      1. 2021-12-21: Trying to get bandwidth for this during F release.
    18. RIC-837 RMR is not forwarding messages from E2T to E2M
    19. RIC-835 → 2021-12-07 news from Viktor
    20. fixed: no new fixes
    21. anybody would like to get more familiar with RMR?

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

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

2023-03-14 (Tuesday)

Recording: link to zoom recording

We stick to the 4pm Helsinki time slot for this meeting. Note that Europe will switch to summer time on March-26. So, for people not doing the switch at the same time, the meetings after March-26 start one hour earlier. Reminder for participants from the US: The US already switched to summer time on Mar-12.

...

  1. Last checked on 2023-02-28
    1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10405 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
      1. 2023-02-28: Abhijit worked with Matt and Sridhar from LF on this. Jobs are now running, but they fail. There's a credential issue. Abhijit to remind Sridhar. Once this is fixed, we can change Dockerfile to install prerequisites.
    2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/10287 → waiting for test cases, Gunja know and will update test case.

...

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

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

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

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

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

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

2024-04-09

Recording: near_rt_ric_09_04-2024.mp4

  1. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
    1. Last checked on (end of I release)
      1. TODO
  2. every second time: Review code coverage stats and blocker code smells
    1. We take a look at the two links in the beginning of this page: Code coverage reports..
    2. The list below is only working reports // Anybody volunteering to work with LF on making the code coverage CI to work again (there's still the old JVM version)
    3. Thoralf did this last on 2023-12-14 as part of release notes:  we did not do this this time
  3. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-1057 gNB unable to connect during high amount of Subscription Requests
    2. RIC-1056 Crashing e2mgr after sending high amount of Subscription Requests
    3. RIC-1055 Unrestricted Registration of RMR Routing Information by xApp
    4. RIC-1054 Kong pod is in crash loopback due to Ingress controller container is not coming up in 1.28 k8s installation
    5. RIC-1052 Not able to install k8s and helm with Existing Ric installation shell script in document
    6. RIC-1051 Problems with deploying xAPPs for the Near-RT RIC - RELEASE H&I - To be checked by Himanshu
    7. RIC-1049 apt repository no longer supports Kubernetes version 1.16.0 in ubuntu 20.04 - To be assigned to Sunil
    8. RIC-1047 crash in E2T metric increment code 
    9. RIC-1045 A1 mediator is in crash loopback state for H-Release And I-Release (HCL team can fix) → DONE (was a mismatch between ric-dep and image versions)
    10. RIC-1044 Potential Missing Array Size Checks Leading to Crashes in e2mgr  
    11. RIC-1043 Crash in E2T buildPrometheusList Function 
    12. RIC-1042 Can't register xApp
    13. RIC-1041 Frequent Pod Eviction in Near-RT RIC Due to Ephemeral-Storage Resource Limitation
    14. RIC-1031 Data model is not compliant with latest A1 spec → Naman (planned to start work in next week)
    15. RIC-1032 → RIC-1035 - we continue with this under RIC-1035 (discussed with Abhijit in the project meeting) → Thoralf needs to take next step here (see also Abhijit's comment in RIC-1035 and in review)
    16. RIC-1025 memory leak in routing manager
    17. RIC-1017 xapp-frame -  xapp-frame may not be able to successfully subscribe to messages

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

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

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

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

    22. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue) → DONE
    23. RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look (note that this related to unimplemented feature RIC-1007)
    24. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    25. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org

...

  1. new bug report RIC-962

  2. RIC-961 (fixed already)

  3. RIC-964 (fixed already)

  4. RIC_966 (fixed already)

  5. RIC-968 (fixed already)

  6. RIC-940 sdlpy missing whitespace → Timo
  7. RIC-939 race conditions in RMR → Abdulwahid
  8. RIC-921 fix UT test case in e2mgr to stub time (leftover from review https://gerrit.o-ran-sc.org/r/c/ric-plt/e2mgr/+/8493)
  9. RIC-915 dms_cli for installing xapp not working (raised by James)
  10. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
  11. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
  12. RIC-897 SCTP connection fails with Viavi // update with workaround
  13. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
  14. RIC-894 long idle period (days) causes RMR connection breaks
  15. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
  16. RIC-857 sporadically RMR takes multiple minutes before being "ready"
  17. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    1. 2021-12-21: Trying to get bandwidth for this during F release.
  18. RIC-837 RMR is not forwarding messages from E2T to E2M
  19. RIC-835 → 2021-12-07 news from Viktor
  20. fixed: no new fixes
  21. anybody would like to get more familiar with RMR?

...

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

  1. The current platform deployment scripts might not be in line with O2 envisions
  2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
  3. O2-D(MS) is relevant to RIC platform.
  4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
  5. 2023-01-31: No news yet
  6. 2023-02-14 No news yet, Thoralf received e-mail on this from James. Still to check.
  7. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
  8. 2023-03-14: AP-James Meeting was held. We see use cases around deploying RIC platform using helm charts over O2; and deploying xApps over O2. For xApps the role of descriptor->helmcharts→k8s manifests in SMO is still missing. AP for James to check with SMO project on ASD (porting or making available "ricdms/dmscli" to SMO; kserve adapter also affected as it uses ricdms) and support for deploying using helm charts and James to discuss with RSAC. Bin-Yang wants to check how RIC can be deployed using helm charts only.

...

  1. 2023-01-31:
    1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
    2. Subhash asked for a wiki page documenting this work.
    3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
      1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
      2. Tacker-based deployment needs to be checked.
  2. 2023-03-14: no news

...

  1. 2023-03-14: no news

...

  1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
    1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
      1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
        1. Thoralf to create JIRA item for this
        2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
        3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
        4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
  2. 2023-03-14:
    1. E2 Reset E2mgr changes done. submgr change and notification to xapp still open.
    2. A1 mediator nanobot integration still under work.

...

  1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
    1. Thoralf raised support request to LF. Reminders sent. Still no solution.
  2. 2023-03-14: now has access to hw-rust, but not yet xapp-frame-rust (no need to escalate yet). CI for xapp-frame-rust works now.

...

  1. 2023-03-14
    1. RIC-851 done
    2. RIC-967 (RIC subscription delete required related changes in xApp communication) added to H release. We discussed this in a meeting and decided to implement pre and post notifications aligned with RICARCH.

...

  1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
  2. Sprint dates
    1. Sprint H release dev sprint 1: Feb-20´to Mar-12
    2. Sprint H release dev sprint 2: Mar-13 to Apr-2
    3. Sprint H release dev sprint 3: Apr-3 to Apr-23
    4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
    5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
  3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link

...

  1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
  2. 2023-01-31, 2023-02-14, 2023-02-28, 2023-03-14: no update

...

  1. data pipeline (Hoejoo's e-mail)
    1. 2023-01-31 not discussed in today's meeting

...

2023-02-28 (Tuesday)

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-02-28
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10405 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
        1. 2023-02-28: Abhijit worked with Matt and Sridhar from LF on this. Jobs are now running, but they fail. There's a credential issue. Abhijit to remind Sridhar. Once this is fixed, we can change Dockerfile to install prerequisites.
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/10287 → waiting for test cases, Gunja know and will update test case.
  2. every second time: Review code coverage stats and blocker code smells
  3. We take a look at the two links in the beginning of this page: Code coverage reports..
  4. 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)
    5. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this timeEvery time: Check if there are new bug reports in JIRA: link
    1. RIC-940 sdlpy missing whitespace → Timo
    2. RIC-939 race conditions in RMR → Abdulwahid
    3. 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)
    4. RIC-915 dms_cli for installing xapp not working (raised by James)
    5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMANDRIC-897 SCTP connection fails with Viavi // update with workaround
    7. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    8. RIC-894 long idle period (days) causes RMR connection breaks
    9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
    12. 2021-12-21: Trying to get bandwidth for this during F release.
    13. RIC-837 RMR is not forwarding messages from E2T to E2M
    14. RIC-835 → 2021-12-07 no news from Viktor
    15. fixed: no new fixes
    16. anybody would like to get more familiar with RMR?

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

    1. The current platform deployment scripts might not be in line with O2 envisions
    2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    3. O2-D(MS) is relevant to RIC platform.
    4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    5. 2023-01-31: No news yet
    6. 2023-02-14 No news yet, Thoralf received e-mail on this from James. Still to check.
    7. 2023-02-28: some e-mail discussion. Ball's on Bin Yang & James side. Subhash and Thoralf discussed this and Thoralf to call a meeting with Bin Yang, subhash, James, Thoralf.
  6. James:updates?
    1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
        1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
        2. Tacker-based deployment needs to be checked.
    2. 2023-02-14: no updates
    3. 2023-02-28: no updates (James did not participate).
  7. Sunil updates?
    1. 2023-02-28: no updates
  8. Subhash/Naman updates?
    1. 2023-02-28: working on RNIB models for E2 reset. Nanobot integration with A1 mediator. kServe adapter work ongoing (RICDMS extension planned).
      1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
        1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
          1. Thoralf to create JIRA item for this
          2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
          3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
          4. https://wiki.o-ran-sc.org/plugins/servlet/mobile?contentId=67535114#content/view/67535114 
  9. Abhijit updates?
    1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
      1. Thoralf raised support request to LF. Reminders sent. Still no solution.
  10. H release content
    1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
    2. Sprint dates
      1. Sprint H release dev sprint 1: Feb-20´to Mar-12
      2. Sprint H release dev sprint 2: Mar-13 to Apr-2
      3. Sprint H release dev sprint 3: Apr-3 to Apr-23
      4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
      5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
    3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
  11. GRPC vs RMR
    1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
    2. 2023-01-31, 2023-02-14, 2023-02-28: no update
  12. Integration with AI/ML project: kserve_adapter
    1. data pipeline (Hoejoo's e-mail)
      1. 2023-01-31 not discussed in today's meeting
  13. Gunja and Sachin CapGemini) presented changes that were done for RIC subscription delete required as per RIC-851. Thoralf to start a mail thread with Nitin, Subhash, Gunja, Sachin on how xapps can be notified of subscription changes. link to the presentation
  14. RICAPP agenda: RICAPP Meetings.

2023-02-14 (Tuesday)

Recording: link to zoom recording

    1.  
  2. James: updates?
    1. 2023-11-21
      1. was at OSC-OAI conference
      2. could start using team accounts to test beds from Colosseum (NU) and ARA
      3. discussed with Bimo (Taiwan lab) on pair-wise testing
      4. discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR  route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
    2. 2024-01-16: TM-500 in Taiwan lab is again available (discussions with Intel on bringing up L1 and L2). RIC probably not one of the very next steps.
    3. 2023-01-30: O-RAN f-2-f: James asked if any demo planned. → not planned.
    4. 2024-02-13: thinking about demos for f-2-f (in discussion with Bimu)
    5. 2024-03-12: No updates. Willing to give demo on ORAN-SC Near RT RIC Demo. Details to be worked on the technical and demo content.
    6. 2024-03-26: Unavailable today.
  3. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
    2. 2024-02-13,2024-03-12,2024-03-26,2024-04-09: no news
  4. Sunil updates (subteam-h)?
    1. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
    2. 2023-11-07: Not in the call today
    3. 2023-11-21: no updates. Difficult to find engineers working on this.
    4. 2024-01-16: demo of xApp project additions in I release → Next time
    5. 2024-01-16: re-evaluating RIC platform Jira items
    6. 2024-01-30: went through old Jira ticket, initial plan for release J: RIC-950, RIC-926, RIC-878 and RIC-860
    7. 2024-02-13: working on RIC subscription delete testing 
    8. 2024-03-12: Implementation completed, facing issues in code submission.
    9. 2024-03-26: Working on RIC-1049, documentation will also be made.
    10. 2024-03-09: Absent
  5. Subhash/Naman updates (subteam-s) ?
    1. 2023-12-05: Naman gave an update on status of Samsung items
    2. 2024-01-16: Naman updated readme (still to merged) on how to deploy RIC using operators.
    3. 2024-01-30, 2024-02-13: no news, but still needs to work on RIC-1031
    4. 2024-03-12: RIC-1031 - Needs more time to complete, To start working on  A1 mediator integration with Non RealTime RIC
    5. 2024-03-26:  Continuing on RIC-1031, Working on RIC-1048 (analysis on RMR scaling, design to be worked upon)
    6. 2024-03-09: Not available
  6. Abhijit updates (subteam-ag) ?
    1. 2023-10-24:
      1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
      2. no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy 
      3. 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
      4. Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and  confluence.
    2. 2024-01-16, 2024-01-30: No news.
    3. 2024-02-13: continues work on xapp framework rust, incl. metric support
    4. 2024-03-12: No news.
    5. 2024-03-26: Implementation done , testing pending for xapp framework rust, incl. metric support
    6. 2024-03-09: Not available.
  7. Cap Gemini updates (subteam-cg)? 
    1. We agreed to come back to repo creation for phase 2 (ricapp part) of conflict manager in 1H2024
    2. 2024-01-16: Ashish presented the  design of conflict manager, first phase: link to slideset
    3. 2024-03-26,2024-03-09: unavailable.
  8. Himanshu (subteam-gs) would like to work on RIC-963
    1. 2023-12-05: RIC-963 seems to be ready. Himanshu still wants to test this with unordered IEs. Requires a minor addition in ric-dep repo for new config parameter.
    2. 2024-01-16: RIC-963 ready and merged. New review for RIC-1030 for final changes on checking (or not checking) IE order in additional messages.
    3. 2024-03-12:  Interested work in open issues that are already assigned. To check RIC-1047, if Dhiraj is not working,   length of IE > 1024 in RIC_ACTION_DEFINITION causing some issue. Sandeep is working in it. Issue in submgr. Good to raise JIRA.
    4. 2024-03-26: Assigned RIC-1043,1044,1047. Will provide updates next week.  length of IE > 1024 in RIC_ACTION_DEFINITION causing issue in submgr - Sandeep to check if Jira needs to be raised. RIC-1051- Himanshu looking into it.
    5. 2024-03-09:  No updates on RIC-1043,1044,1047. Amit will contribute to this project.
  9. Dhiraj (subteam-r)
    1. 2023-12-05: moved the IPv6 item  to J release
    2. 2024-01-16: approval for changes to be committed now obtained. IPv6-related commits expected over the next weeks.
    3. 2024-01-26,2024-04-09: no news.
  10. Alexandre (subteam-utfpr)
    1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
    2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
    3. 2024-03-12: RIC-989 and RIC-991 closed. RIC-1001 would need support from ric-plt/rtmgr, will send email to Abdulwahid. xapp-frame(C++) changes for xapp registration locally completed. Jira will be raised
    4. 2024-03-26,2024-04-09: No news.
  11. Nokia (subteam-n)
    1. RIC-997 postponed to J
    2. 2024-02-13: Thoralf leaving Nokia/PTL role. Role is open for applications. Nokia nominated Abdulwahid.
  12. ORAN-SC half day workshop, San Jose, CA on April 29th - Any volunteers to make on-site demo of NEAR RT RIC - James will take it up.
    1. 2024-03-26: New nomination awaited from TOC.
    2. 2024-04-09: The presentation of NEAR RT RIC would be handled by someone else(not James)
  13. J release
    1. 2024-02-13: Naman's input
      1. no Jira tickets yet, but woudl like to focus on 
        1. K8S operator for day 2 operations, like scale-in and scale-out (but requires some thoughts on messaging) : RIC-1048
    2. I release theme for near-rt RIC was "RIC Platform Enhancements". What's it going to be for J?
      1. Thoralf's proposal based on current Jira list: "Make the platform more robust in handling E2AP, conflicts and A1"
    3. We
  14. 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  Dec-15
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
    15. every second time: Review code coverage stats and blocker code smells
  15. We take a look at the two links in the beginning of this page: Code coverage reports..
  16. 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)
    17. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this time
  17. Every time: Check if there are new bug reports in JIRA: link
    1. RIC-940 sdlpy missing whitespace → Timo
    2. RIC-939 race conditions in RMR → Abdulwahid
    3. 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)
    4. RIC-915 dms_cli for installing xapp not working (raised by James)
    5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    7. RIC-897 SCTP connection fails with Viavi // update with workaround
    8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    9. RIC-894 long idle period (days) causes RMR connection breaks
    10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    12. 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.
    13. RIC-837 RMR is not forwarding messages from E2T to E2M
    14. RIC-835 → 2021-12-07 news from Viktor
    15. fixed: no new fixes
    16. anybody would like to get more familiar with RMR?

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

    1. The current platform deployment scripts might not be in line with O2 envisions
    2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
    3. O2-D(MS) is relevant to RIC platform.
    4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
    5. 2023-01-31: No news yet
    6. 2023-02-14 No news yet, Thoralf received e-mail on this from James. Still to check.
  19. Sunil still to discuss with other team members for other items from subteam-h
    1. 2023-02-14: Sunil provided list with four items.
  20. James:updates?
    1. 2023-01-31:
      1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
      2. Subhash asked for a wiki page documenting this work.
      3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
        1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
        2. Tacker-based deployment needs to be checked.
    2. 2023-02-14: not updates
    21. H release content
    we
    1. mark items that you are >90% sure (=”committed”) to work on during
    22. 1H2023
    1. 1H2024 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for
    23. H
    1. 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. Sprint datesSprint H
          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-
        3. 20´to
          1. 19 to Mar-
        4. 12
          1. 10
          2. Sprint
        5. H
          1. J release dev sprint 2: Mar-
        6. 13
          1. 11 to
        7. Apr
          1. Mar-
        8. 2
          1. 31
          2. Sprint
        9. H
          1. J release dev sprint 3: Apr-
        10. 3
          1. 1 to Apr-
        11. 23
          1. 21
          2. Sprint
        12. H
          1. J release dev sprint 4: Apr-
        13. 24
          1. 22 to May-
        14. 14
          1. 12 (last planned development sprint)
          2. Sprint
        15. H
          1. J release dev sprint 5: May-
        16. 15
          1. 13 to Jun-
        17. 4
          1. 2 (only for unplanned last-minute development items)
      18. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
      19. GRPC vs RMR
        1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
        2. 2023-01-31: no update
        3. 2023-02-14: no update
      20. Johannes/Bryan: RUST as a language for xApps and framework. Will take this in the details in next meeting.
        1. 2023-01-31: Abhijit wanted to merge something. pls. contact Thoralf.
          1. no news from Johannes/Bryan
        2. 2023-02-14:
          1. Abhijit is now committer for the rust subsystems (platform and xapp) - but there seem to be issues on LF side that didn't actually made this happen.
          2. Thoralf to raise support request to LF
      21. Integration with AI/ML project: kserve_adapter
        1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
          1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
            1. Thoralf to create JIRA item for this
            2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. But also ok if only in one.
            3. 2023-02-14: Subhash discussed with Hoejoo on this (internally) - maybe a presentation coming later
        2. data pipeline (Hoejoo's e-mail)
          1. 2023-01-31 not discussed in today's meeting
      22. CapGemini to present to project meeting changes that were done for RIC subscription delete required
      23. RICAPP agenda: RICAPP Meetings.

      2023-01-31 (Tuesday)

      Recording: link to zoom recording

      1. 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/
      4. Every time: Check rule RC-4 (link) that all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing).
        1. Last checked on  Dec-15
          1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
      5. every second time: Review code coverage stats and blocker code smells
      6. We take a look at the two links in the beginning of this page: Code coverage reports..
      7. 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)
        8. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this timeEvery time: Check if there are new bug reports in JIRA: link
        1. RIC-940 sdlpy missing whitespace → Timo
        2. RIC-939 race conditions in RMR → Abdulwahid
        3. 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)
        4. RIC-915 dms_cli for installing xapp not working (raised by James)
        5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
        6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
        7. RIC-897 SCTP connection fails with Viavi // update with workaroundRIC-896 xapps sending same msg type and sub id fails - details to be clarified
        8. RIC-894 long idle period (days) causes RMR connection breaks
        9. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
        10. RIC-857 sporadically RMR takes multiple minutes before being "ready"
        11. RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.2021-12-21: Trying to get bandwidth for this during F release.
        12. RIC-837 RMR is not forwarding messages from E2T to E2M
        13. RIC-835 → 2021-12-07 no news from Viktor
        14. fixed: no new fixes
        15. anybody would like to get more familiar with RMR?
      8. Mark your affiliation in https://openprofile.dev  so that statistics are correctly generated.

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

        1. The current platform deployment scripts might not be in line with O2 envisions
        2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
        3. O2-D(MS) is relevant to RIC platform.
        4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Could be implemented as second option for deploying xApps.
        5. 2023-01-31: No news yet
      10. Sunil still to discuss with other team members for other items from subteam-h
        1. 2023-01-31: no news yet. HCL still in internal discussion on what open-src items to work on in 1H2023
      11. James:updates?
        1. 2023-01-31:
          1. working on existing robot test cases (that integrate xapps and platform) to be part of xtesting tests.
          2. Subhash asked for a wiki page documenting this work.
          3. WR also want to contribute to xtesting for O2. CNF package definition still open and concept of DMS.
            1. discussion with Bin Yang in this meeting is possible. Maybe some proposal would be good.
            2. Tacker-based deployment needs to be checked.
      12. H release content
        1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
        2. Sprint dates
          1. Sprint H release dev sprint 1: Feb-20´to Mar-12
          2. Sprint H release dev sprint 2: Mar-13 to Apr-2
          3. Sprint H release dev sprint 3: Apr-3 to Apr-23
          4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
          5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
        3. We go through the rough views on what you might want to work on. Also as input use delayed items from previous release link
      13. GRPC vs RMR
        1. 2023-01-17: Still working this within Nokia. WG3 also discusses this.
        2. 2023-01-31: no update
      14. Johannes/Bryan: RUST as a language for xApps and framework. Will take this in the details in next meeting.
        1. 2023-01-31: Abhijit wanted to merge something. pls. contact Thoralf.
          1. no news from Johannes/Bryan
      15. Integration with AI/ML project: kserve_adapter
        1. Kserve adapter (mentioned in RSAC and e-mail from Hoejoo),
          1. 2023-01-31 Joseph presented the kserve part. We agreed as working assumption to go for solution #1 (slide 2) with model-based inference. Comments by e-mail to Joseph. Slideset: link
            1. Thoralf to create JIRA item for this
            2. Subhash/Thoralf commented that ricdms cli and REST should be implemented at same time. BUt also ok if only in one.
        2. data pipeline (Hoejoo's e-mail)
          1. 2023-01-31 not discussed in today's meeting
      16. RICAPP agenda: RICAPP Meetings.

      2023-01-17 (Tuesday)

      Recording: link to zoom recording

      ...

      1. Last checked on  Dec-15
        1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF

      ...

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

      ...

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

      1. The current platform deployment scripts might not be in line with O2 envisions
      2. David Liu (WR) asked from James on O2 as well. James to check if a proposal on using X testing framework could also be used for integration. There's is also a link to robot test cases.
      3. O2-D(MS) is relevant to RIC platform.
      4. deploying xApps (LCM) is also an O2 issue - the alternative of using CRDs is not implemented in OSC RIC. Coudl be implemented as second option for deploying xApps.

      ...

      1. Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.
        1. RIC-860 + RIC-878
          1. Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in, but it seems https://gerrit.o-ran-sc.org/r/c/it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
          2. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in
          3. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
          4. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
          5. 2022-04-26: still open
          6. 2022-05-11: expecting to finalize by May-27
          7. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
          8. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
          9. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
          10. 2022-08-02: SUNIL SINGH to check any news on RIC-860 or RIC-878?
          11. 2022-08-16→2022-08-30->2022-09-13→2022-09-27: no update
          12. : some cleanup is needed first.
            1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
            2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
            3. test both if they are actually working
            4. 2022-08-30: team currently busy, but will pick up on this again soon
          13. 2023-01-17: for now remove form agenda and take back if we find someone to work on it.
        2. RIC-641 + RIC-705
          1. RIC-641: done in G
          2. RIC-705: xapp registration still open (for H?) → manage this via H content and don't keep it in the agenda.

      ...

      1. created on 2022-08-30: Update 2022-09-13 → 2022-09-27: Now hanging with Augu. - waiting for reply
      2. 2023-01-17: no news → we drop this item from the agenda

      ...

      1. 2022-11-08: continues work with keysight (using KPI-mon-go xApp (E2APv1, and older E2SM). hw-go could be used if E2AP2.0 is needed. hw-go does not parse E2SM-parts.
        1. HCL also working on E2APv2.0 xApps.
      2. 2023-01-17: work with keysight completed before thanksgiving weekend (excl. xapp; focus on base E2AP cases). No need to keep this in the agenda.

      ...

      1. we mark items that you are >90% sure (=”committed”) to work on during 1H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for H release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
      2. Sprint dates
        1. Sprint H release dev sprint 1: Feb-20´to Mar-12
        2. Sprint H release dev sprint 2: Mar-13 to Apr-2
        3. Sprint H release dev sprint 3: Apr-3 to Apr-23
        4. Sprint H release dev sprint 4: Apr-24 to May-14 (last planned development sprint)
        5. Sprint H release dev sprint 5: May-15 to Jun-4 (only for unplanned last-minute development items)
      3. Please prepare for next meeting a rough view on what you might want to work on. Also as input use delayed items from previous release link

      ...

      1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
      2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
      3. need to look at Mavenir E2SM-RC proposal.
      4. impact on xapp frameworks will happen as well.
      5. Alexandre mentioned option of using QUIC (grpc over QUIC).
      6. Thoralf to schedule a meeting once a proposal is ready.
      7. 2022-08-16 →2022-08-30 → 2022-09-27 → 2022-10-11: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
      8. 2022-11-08: focus of Nokia proposal will be on scalability (xApps, #E2 connections)
      9. 2022-11-22: WG3 spec for RICAPI available in current train. Worth reading. Defines GRPC, but also SCTP+Protobuf interfaces.
      10. 2023-01-17: Still working this within Nokia. WG3 also discusses this.

      ...

      1. 2023-01-17: not discussed today.

      ...

      2023-01-03 (Tuesday)

      Recording: Link to zoom recording

      Sunil kindly agreed to host also the RIC platform part of this week's project meeting.

      We will discuss the plans for the H release in the next meeting. As before, items that were delayed from the previous release and leftover items are prime candidates to work on. Left overs: link

      2022-12-06 (Tuesday)

      Recording:  Link to zoom recording

      The meeting was hosted by Sunil.

      Updates on RICP.

      1. Updates (from Subhash)
        1. RIC-385: first part done defining the E2 messages in golang, but actual Reset implementation still needed.  Rest goes to release H
        2. RIC-714: dms Rest interface. Instructions still missing
        3. RIC-914+RIC-849: done (helm charts and jenkins job still coming)
        4. RIC-911: done
      2. Updates (from Sunil)
        1. RIC-860 and RIC-878 code for REST subscriptiopn API is now actively being worked on.
      3. Updates (from Johannes)
        1. still struggling with CI, but likely to "formally" release RMR part of RUST framework.
      4. RICAPP agenda: RICAPP Meetings.

      2022-11-22 (Tuesday)

      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. 2022-10-11+2022-11-08+2022-11-22
          1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/9117 how automated CI module testing can be done is to be discussed // also need to discuss CI // already known that this requires discussion with LF
      2. every second time: Review code coverage stats and blocker code smells
      3. We take a look at the two links in the beginning of this page: Code coverage reports..
      4. 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)
        5. Thoralf did this last on 2022-05-27. 2022-11-22: we did not do this this timeEvery time: Check if there are new bug reports in JIRA: link
        1. RIC-940 sdlpy missing whitespace → Timo
        2. RIC-939 race conditions in RMR → Abdulwahid
        3. RIC-921 fix UT test case in e2mgr to stub time (leftover from review
          1. Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil 
          2. no progress in review on the plain helm chart based deployment in
          1. https://gerrit.o-ran-sc.org/r/c/ric-plt/
          e2mgr
          1. ric-dep/+/
          8493)
        4. RIC-915 dms_cli for installing xapp not working (raised by James)
        5. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
        6. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
        7. RIC-897 SCTP connection fails with Viavi // update with workaround
        8. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
        9. RIC-894 long idle period (days) causes RMR connection breaks
        10. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
        11. RIC-857 sporadically RMR takes multiple minutes before being "ready"
        12. 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.
        13. RIC-837 RMR is not forwarding messages from E2T to E2M
        14. RIC-835 → 2021-12-07 news from Viktor
        15. fixed: no new fixes
        16. anybody would like to get more familiar with RMR?

      5. demo day? Suggestion: Dec-20. Add demo topic here: 2022-12-20 Release G

          1. 11743 → to be merged by Thoralf Czichy 
          2. Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia
          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.
      7. 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
      8. 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".
        Sunil still to discuss with other team members for other items from subteam-h
          Other tickets CI/CD and Code coverage tickets? Sunil: I am still looking for the resources to work on that.RIC-860 + RIC-878
          Sangeetha working on RIC-860, done, but code still to be checked in. 2022-07-05& 2022-07-19 update:  - Code checked-in, but it seems
        1. 2023-11-07: addressing review comments of
        2. 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.
      9. 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

      10. Alexandre (subteam-utfpr)
        1. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
        2. 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
      11. Nokia (subteam-n)
        1. .RIC-997 likely being postponed.
      12. 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.


      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. /it/test/+/8530 that is part of GIT relation chain was abandoned (it contained the bulk of the changes for subscription deletion test)
          3. Sangeetha working on RIC-878, status see Jira item, code still to be checked in. 2022-07-05 & 2022-07-19 update:  - Code checked-in
          4. O1 testing is also being worked on. 2022-03-29 Sangeetha to raise Jira ticket
          5. Subhash asked for documentation of nanobot from Sunil. Almost done. 2022-05-11: Still open
          6. 2022-04-26: still open
          7. 2022-05-11: expecting to finalize by May-27
          8. 2022-06-07: news on RIC-860 and RIC-878 or O1 testing?
          9. 2022-07-05: Thoralf marked RIC-860 and RIC-878 as moved out of F release
          10. 2022-07-19: This is pending on LF to get permissions resolved and could then merge these.
          11. 2022-08-02: SUNIL SINGH to check any news on RIC-860 or RIC-878?
          12. 2022-08-16→2022-08-30->2022-09-13→2022-09-27: no update
          13. : some cleanup is needed first.
            1. RIC-860 - suggestion is to merge the one abandoned RIC-860 review and the one that is still open into one review and keep that as new review.
            2. RIC-878 - suggest to re-start review 8500 and merge it with the current open one for RIC-878 and start this as new review.
            3. test both if they are actually working
            4. 2022-08-30: team currently busy, but will pick up on this again soon
          14. contributions by new contributor on asn.1 encoders/decoders and APER ASN.1↔XML tool - waiting for repo proposal
            1. created on 2022-08-30: Update 2022-09-13 → 2022-09-27: Now hanging with Augu. - waiting for reply
          15. RIC-641 Progress on xapp side adaptation to REST interface? RIC-641 Sandeep→ Anh Nguyen (HCL) is working on this. Work is progressing.
          16. 2022-04-12: framework changes done. Now integrating with Bouncer xApp. The reviews are coming.
            17. 2022-06-21
          17. RIC-642 (python) done
            18. RIC-705 and RIC-641 being worked on by Anh Nguyen: https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-cppricdms/+/8561
          18. 2022-07-05: Thoralf moved RIC-705 and RIC-641 (xapp-frame-cpp) out of the F release. Which means they are likely early G release features.
          19. 2022-07-19: RIC-912 for clean up of the build process (should use dockerfile). But we first try to get current review through
          20. 2022-08-02: SUNIL SINGH check status with Anh Nguyen
          21. 2022-08-16: any news?
            1. one optinion is to cleanup CI first with the approach in RIC-912
            2. there are also instructions for testing CI given by LF infra. Thoralf-to dig out the instructions
          22. 2022-08-30  Waiting for Anh Nguyen to come fully back to work.
          23. 2022-09-13→ 2022-09-27: no update, but Anh Nguyen is now back and in discussion with Anssi
          24. 2022-10-11: Anh Nguyen to pick up again. Thoralf fixed CI issues via sandbox, minor change in CI job definition and it commit.
      2. James: RSAC recommended incorporating OTF in testing (David Kinsey can help)- Thoralf to start mail thread with HCL (sunil, Sangeetha) and David on this plus James.
        1. 2022-04-12
          1. last Thursday RSAC call was used for preparing OTF installation of the three microservices into O-Cloud (WR k8s with O2 IMS/DMS) to avoid firewall issues
          2. actual workshop planned for RSAC on Apr-21 9am EDT.
          3. Taking OTF into use in E release might be only partially done in E release (also discussed in last week's TOC)
        2. 2022-04-26
          1. OTF installed and configured in Bedminster lab. Still access issues, though. Workshop planned for next Wed morning, 8am ET.
          2. David K. shared a lab network picture with the RIC on a separate network. Thoralf not sure why. Subhash and Thoralf interested in the document shared in last RSAC meeting.
        3. 2022-05-11:
          1. Currently in the hands of OTF team (Alex)
          2. dms_cli seems to have issues (James has used this in E release), dms_cli does not have CI/CD case. For now, let's agree if a good problem report is sent, Nune or Thoralf can look at it.
            1. 2022-05-30: Thoralf comment in RIC-915
        4. 2022-06-21: XTesting (used by Anuket) proposed as alternative to OTF (lack of support from OTF developers)
        5. 2022-07-19: James is working on it with LF
        6. 2022-08-02: any updates?
          1. caur.us (johannes@ c...) working on docker compose deployment (no K8S). usable in CI?
          2. James working Sridhar on xTesting.
        7. 2022-08-16 no news. Friday James will have further discussion with xTesting "evangelist" from Anuket
        8. 2022-08-30 progress on xTesting - first results to be presented in RSAC on Sep-21.
        9. 2022-09-13: kubectl version used in testing doesn't match expectations. Work in progress
        10. 2022-09-27: Demo is in the RSAC meeting from last week. Instructions are here: Automated Testing via XTesting And also watch the RSAC video recording from last week: link (fast forward to minute 9:00).
          1. next step: promote this to all OSC subprojects via TOC.
          2. James trying to run robot test cases in it/test.
        11. 2022-10-11: still work in progress. Second demonstration with updated scripts: https://wiki.o-ran-sc.org/download/attachments/3604609/XTesting-demo.mp4?api=v2
        12. 2022-11-08: continues work with keysight (using KPI-mon-go xApp (E2APv1, and older E2SM). hw-go could be used if E2AP2.0 is needed. hw-go does not parse E2SM-parts.
          1. HCL also working on E2APv2.0 xApps.
      3. G release content wrap up
        1. we mark items that you are >90% sure (=”committed”) to work on during 2H2022 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for G release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
        2. Sprint dates
          1. Sprint G release dev sprint 1: Aug-22 to Sep-11
          2. Sprint G release dev sprint 2: Sep-12 to Oct-2
          3. Sprint G release dev sprint 3: Oct-3 to Oct-23
          4. Sprint G release dev sprint 4: Oct-24 to Nov-13 (last planned development sprint)
          5. Sprint G release dev sprint 5: Nov-14 to Dec-4 (only for unplanned last-minute development items)

        3. link to G Release summary. Try to finalize all work by Dec-6 so we can generate the release images in the week of Dec-6

      4. GRPC vs RMR
        1. Nokia is plannig RMR with GRPC (E2AP-equivalent xApp interfaces)
        2. to include Alexandre in discussion as well. Subhash also interested in what's coming. Nitin (mavenir) and Sunil (HCL) also interested.
        3. need to look at Mavenir E2SM-RC proposal.
        4. impact on xapp frameworks will happen as well.
        5. Alexandre mentioned option of using QUIC (grpc over QUIC).
        6. Thoralf to schedule a meeting once a proposal is ready.
        7. 2022-08-16 →2022-08-30 → 2022-09-27 → 2022-10-11: no news yet, current approach we assume E2M manages E2 node to gNB list mapping and submgr (together with E2T) manage subscriptions. xApps to be aware of many E2T instances and many xApp instances.
        8. 2022-11-08: focus of Nokia proposal will be on scalability (xApps, #E2 connections)
        9. 2022-11-22: WG3 spec for RICAPI available in current train. Worth reading. Defines GRPC, but also SCTP+Protobuf interfaces.
      5. In O-RAN f-2-f in October, OSC has a three hour slot for presentations about what OSC did. RSAC coordinates this. Slideset on content of E and F release, show existing demo on RIC deploy, xapp deploy and connect simulator, show demo on E2AP2.0 incl. E2 config update (all together 30 min).
        1. 2022-09-13: likely the way we go forward - Subhash and Thoralf will handle
          1. 2022-09-27: Thoralf to create presentation material and send to subhash
          2. 2022-10-11: Material shared and sent to RSAC
          3. 2022-11-08: DONE
        2. FYI: FYUZ (O-RAN, TIP, Metaverse summit) happens the week after the O-RAN F-2-F (same place) - Thoralf will present on the O-RAN day
          1. 2022-11-08: DONE
          2. Thoralf talked about the RIC in the presentation "Panel 3 - The RIC: How to over-deliver on the promise". The panel 3 recording starts at 1:46:00 into the youtube video: https://youtu.be/W1i6EPQ1wzo?t=6370 Thoralf also talked in the breakout panel discussion "Unpacking the intelligence of RIC: optimization and automation of complexity" (no video)
          3. James organized a video loop for the OSC video recordings and James (CMCC) and and Ramesh (HCL) talked in the breakout panel discussion "Accelerating O-RAN adoption through open source"
          4. OAI planning to support E2SM-KPM/E2SM-RC in CU/DU/gNB
          5. ns-3 E2 adapter (GPL) is now published in OSC.
      6. Update from Samsung side
        1. news discussed in G release content section
          1. 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.
      8. 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
      9. 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
      10. 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
      11. Prashant's work in near-RT RIC(subteam-p)
        1. 2023-08-22, 2023-09-26. 2023-11-07: could not participate
      12. 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
      13. 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
      14. 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.
      15. 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
      16. 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.
      17. 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

      18. 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
      19. Nokia (subteam-n)
        1. ...
      20. 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.
        2. RUST as a language for xApps and framework. Will take this in the details in next meeting.
      2. 2022-08-02
        1. hw-rust creation review by Johannes = https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70416 ?
        2. Sunil to contact Johannes that he abandons his change and we continue with Sunil's: https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/70429
      3. 2022-09-13: working is progressing. end of September first commits should come.
      4. 2022-09-27: first commit likely coming this week. Johannes could demo in two weeks from now.
      5. 2022-10-11: first commit under review.
        1. 2022-10-11 Johannes to look into CI (and module tests) for Rust
          1. status: basic framework ready (ping-pong dmeo works between two xapps). next step SDL.
        2. 2022-11-08 demo (5-10min)
        6. 2022-11-22. Thoralf to ask for status
      7. RICAPP agenda: RICAPP Meetings.

      Older meeting minutes

      check from here: Project meetings (old)

      ...