Versions Compared

Old Version 667

changes.mady.by.user Naman Gupta

Saved on

compared with

New Version 668

changes.mady.by.user Thoralf Czichy

Saved on

Key

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

...

2023-08-22 (exceptionally one week later than normal)

Recording: TODO 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-04-11
      1. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame/+/10923 OK, module version updates only
  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-1002 Abnormal signaling process cause E2Term crash (this could be a security issue)
    2. RIC-1001 RMR service should verify route tables.
    3. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
    4. RIC-989 rmr (minor) security issue - Alexandre will take a look
    5. new: RIC-988 CLOSED e2 component configuration → Duplicate of fix https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/e2mgr.git;a=commit;h=d2f1a29d3f1cc779045148a82729f644e6110776 
    6. RIC-986 ping-pong example xapp-frame-py needs fixes in the dockerfile DONE
    7. RIC-979 Decode Error with e2sim on e2term Pod - 2023-08-22: Abhijit still looking into this, but with latest Ubuntu packages this seems not to cause the problem anymore.
    8. RIC-972 URL for A1 mediator to align with spec.
    9. RIC-965 RMR wormhole connections uses stale endpoints to make connections 
    10. 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)
    11. RIC-915 dms_cli for installing xapp not working (raised by James)
    12. RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
    13. RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
    14. RIC-897 SCTP connection fails with Viavi // update with workaround → Thoralf changed this into an Epic (problem was on simulator side. But some useful extension on E2T comes from this as well)
    15. RIC-896 xapps sending same msg type and sub id fails - details to be clarified
    16. RIC-894 long idle period (days) causes RMR connection breaks
    17. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    18. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    19. 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.
    20. RIC-837 RMR is not forwarding messages from E2T to E2M
    21. RIC-835 → 2021-12-07 no news from Viktor
    22. fixed: RIC-986
  4. Himanshu: demo on the OAI CU <--> OSC RIC integration
    1. Himanshu presented the integration of SDRAN-fork of OAI (with SDRAN E2 support added) and how the CU connects to OSC RIC
  5. 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
    3. 2023-04-11: H release test cases related O2 IMS committed into it/test. Some of these related to existing robot test cases.
    4. 2023-04-25: no updates
    5. 2023-05-09:
      1. Q-to-James: summary of what you presented in TOC (1 min) and let's raise question to all for input to integration project.
        1. Xtesting is used in integration project now (already for 6 months or so). Xtesting works also with robot test cases.
        2. James working in this integration for the test cases that are already in it/test. Infrastructure team also contributed O2 releated robot test cases (requires o-loud).
        3. Input from other subprojects, incl. our near-RT RIC project?
      2. James needs some hints on how to run the existing robot test cases in it/test related to missing env variables: GLOBAL_INJECTED_E2MGR_USER and APPMGR_ENDPOINT.
    6. 2023-05-23 → no news
    7. 2023-07-18: James' focus is currently on OSC & OAI cooperation. Current thinking is to use Taiwan lab to host OAI -based installation over E2AP (2.0). See also https://openairinterface.org/mosaic5g/
      1. usage of robot test cases (from it/test) is still something that James is thinking about.
      2. Himanshu commented that he tried OAI CU/DU with OSC RIC and KPM xApp.
    8. 2023-08-01:
      1. O2 integration with OSC RIC is still pending with WR.
      2. OAI was discussed in last week's TOC, and it seems OAI license is not blocker for using OAI in OSC-labs.
    9. 2023-08-22:
      1. Can we do pair-wise testing, e.g., between (1) xapp and RIC, (2) non-RT RIC ↔ near-RT RIC testing (only A1) ?
        1. E.g., KPIMON or bouncer xApp could be used. Sunil might be able to help.
        2. e.g., existing discussion with John
  6. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22 : could not participate
  7. Sunil updates (subteam-h)?
    1. 2023-07-18, 2023-08-01, 2023-08-22: no news
  8. Subhash/Naman updates (subteam-s) ?
    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
    4. 2023-04-11: E2 reset work in submgr is now under work.
    5. 2023-04-25: Naman working on E2 reset (submgr part), ricdms not too much progress. no update on kserve
    6. 2023-05-09:
      1. E2 reset done, but still one more review coming on submgr to block subscriptions fo0r E2 nodes under reset.
      2. A1 bug fixes being almost ready.
      3. A1 mediator nanobot might be delayed.
      4. AI/ML adapter work is still ongoing - ricdms changes still coming during next 1-2 weeks.
    7. 2023-05-23
      1. E2 reset (from E2 node): done
      2. KServe adapter still being worked on.
      3. nanobot integration still being worked on.
    8. 2023-07-18: no news, planning for I release
    9. 2023-08-01:
      1. E2AP v3.0 → we took a look at what changes are coming 
      2. A1 enhancements
      3. considering upgrade of ubuntu and k8s
      4. deploying RIC and xapps using k8S operator I_Release_Proposal_Samsung_Naman.pptx
      5. DMS delete PI
      6. E2 reset from ric to e2 node
    10. 2023-08-22: we discussed Jira item priority.
  9. Abhijit updates (subteam-ag) ?
    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.
    3. 2023-03-28: working on RIC-969 and part of RIC-957
    4. 2023-04-11:
      1. RIC-969 first set of APIs (SDL) implemented. RNIB not yet (also under RIC-969).
      2. hw world xApp should grow with the implementation of xapp-frame-rust. Initial hw-rust xapp will show use of SDL/RNIB.
    5. 2023-04-25
      1. working on RNIB support in rust (https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-rust/+/10906) and next step hw-rust.
    6. 2023-05-09
      1. RIC-977 (subscription API) - pls. merge.
      2. RIC-978 pls. try to complete during this week.
      3. issues with E2 simulator → to get in contact with Naman and Subhash
    7. 2023-05-23
      1. hw-rust xapp using xapp descriptor (config.json) works, but still fixing lifeness and readiness probe
      2. testing of subscriptions using hw-rust (facing the E2T problem)
    8. 2023-07-18: no news
    9. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
    10. 2023-08-22: next release item discussed and RIC-979
  10. Cap Gemini updates (subteam-cg)? 
    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, 2023-04-11, 2023-04-25, 2023-05-23: no news.
    3. 2023-05-23: presentation on RIC SUBSCRIPTION DELETE REQUIRED and communication between xApps and submgr. → DONE
    4. 2023-07-18: Cap Gemini (Gunja) conflict management presentation planned for end of July
    5. 2023-08-01

      1. Gunja to present conflict management design

      2. thinking about adding support for DU in E2T/E2M/RNIB in I release

    6. 2023-08-22:
      1. Gunja provided reviews for DU support. Nokia to reviewed and merged

        1.  https://gerrit.o-ran-sc.org/r/q/topic:%22Multiple+E2+Node+support%22 and  https://gerrit.o-ran-sc.org/r/q/topic:Multi_E2_Node

      2. conflit management status?
  11. Himanshu (subteam-gs) would like to work on RIC-963
    1. code changes, but difficult to test as difficult to change order of IEs in message.
    2. 2023-06-06: Added unit tests (integrated in image building) - did some changes in the stubs (based on environment variables). Next step looking into this.
    3. 2023-07-18: Code changes almost ready for RIC subscription response - gerrit review coming.
    4. 2023-08-22: feedback from Anssi on submgr received and incorporating these changes, but not yet in review.
  12. Dhiraj (subteam-r)
    1. 2023-05-23: ipv6 - Alexandre working on this: RIC-985. Note that this requires re-creation of most container images.
    2. 2023-06-06: ipv6 fix is merged. Dhiraj tried with this new version. Containers start. Good. Investigation continues - most likely fix needed in routing manager ([ brackets cause issues)and E2T (crashes to be fixed).
    3. 2023-07-18: IPv6 changes to come as review
    4. 2023-08-01: working on it.
    5. 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).
  13. Alexandre (subteam-utfpr)
    1. 2023-05-23: no news
    2. 2023-06-06:
      1. fixed IPv6 support in RMR - works in IPv6 only case and in case of providing specific IPv6 address. Routing mgr might require additional work.
      2. seems also to be a bug in interface name solution in RMR. Remember to create a JIRA item (RIC-987)
    3. 2023-08-22: news?
  14. Nokia (subteam-n)
    1. 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, 2023-04-11, 2023-04-25, 2023-05-09, 2023-05-23, 2023-07-18: no update
    2. 2023-08-22: want to work on RIC-997
  15. I release content

...