Versions Compared

Old Version 737

changes.mady.by.user Thoralf Czichy

Saved on

compared with

New Version 738

changes.mady.by.user Thoralf Czichy

Saved on

Key

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

...

  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. 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: 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

...