Versions Compared

Old Version 685

changes.mady.by.user Thoralf Czichy

Saved on

compared with

New Version 686

changes.mady.by.user Abhijit Gadgil

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-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-1011 (Nokia fixes) E2 error with cause duplicate-error for all subscriptions requests after resource-limit failure - FIXED
    2. RIC-1009 E2Mgr API can be improperly invoked → convert to bigger Epic?
    3. RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
    4. RIC-1001 RMR service should verify route tables - Alexandre will take a look
    5. RIC-991 rmr related (not a duplicate) - Alexandre will take a look
    6. RIC-989 rmr (minor) security issue - Alexandre will take a look
    7. RIC-979 (Abhijit will close this one) 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 (Naman) 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-896 xapps sending same msg type and sub id fails - details to be clarified
    15. RIC-894 long idle period (days) causes RMR connection breaks
    16. RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
    17. RIC-857 sporadically RMR takes multiple minutes before being "ready"
    18. 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.
    19. RIC-837 RMR is not forwarding messages from E2T to E2M
    20. RIC-835 → 2021-12-07 no news from Viktor
    21. fixed: RIC-1011
  4. James: updates?
    1. 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.
    2. 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
    3. 2023-08-29: no news
    4. 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.
    5. 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)
  5. Prashant's work in near-RT RIC(subteam-p)
    1. 2023-08-22 : could not participate
  6. Sunil updates (subteam-h)?
    1. 2023-07-18, 2023-08-01, 2023-08-22, 2023-08-29: no news
    2. 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
  7. Subhash/Naman updates (subteam-s) ?
    1. 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
    2. 2023-08-22: we discussed Jira item priority.
    3. 2023-08-29: no news, other than Naman working on the operator implementation.
    4. 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
    5. 2023-09-26: What happened to kserve adapter?
  8. Abhijit updates (subteam-ag) ?
    1. 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)
    2. 2023-07-18: no news
    3. 2023-08-01: got logs from Subhash. Now ran into issues with Dockerfile in E2T (gcc related differences between ubuntu 20 and 22)
    4. 2023-08-22: next release item discussed and RIC-979
    5. 2023-08-29:
      1. created RIC-1004 for release I item.
      2. still working on RIC minimal implementation (demo coming once ready, might take still weeks)
        1. once it's somewhat usable, pls. place into subdirectory under ric-plt/ric-dep
    6. 2023-09-12:
      1. changes related to registration API needed in xapp-frame (problem still to be thought of)
      2. something not working in github: IT-25974 - again related to github replication.
    7. 2023-09-26
      1. Abhijit to present his work on a single near RT RIC helm chart and bringing up the platform on minikube on Ubuntu 22.04. 
  9. Cap Gemini updates (subteam-cg)? 
    1. 2023-08-01

      1. Gunja to present conflict management design

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

    2. 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. Conflict detection and management. Presentation by Gunja on Sep-12 link-to-slideset
        1. Ashish S. (CapGemini) presented this.
        2. Thoralf will initiate a new repo for this: ric-plt/conflictmgr
          1. this might become an optional or mandatory (but default-disabled) component of thr near-rt ric platform.
          2. todo-cap-gemini: align usage of UE ID with wg3 discussion on this.
          3. additional latency comes only from guidance request
          4. xapp-framework could be extended to automatically do E2 guidance requests
  10. 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.
    5. 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".
  11. Dhiraj (subteam-r)
    1. 2023-07-18: IPv6 changes to come as review
    2. 2023-08-01: working on it.
    3. 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).
    4. 2023-09-29:
      1. got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes
  12. Alexandre (subteam-utfpr)
    1. 2023-08-22: Alexandre couldn't participate, but informed after the meeting by e-mail: "My plan for the next two weeks is to fix both RIC-989 and RIC-991 issues."
    2. 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
  13. Nokia (subteam-n)
    1. 2023-08-22: want to work on RIC-997
    2. 2023-09-12: Thoralf did changes to readthedocs in all near-RT RIC repos. LF informed (link) these changes are needed because some configuration parameters are being removed. No further changes needed due to this. Example: https://gerrit.o-ran-sc.org/r/c/ric-plt/a1/+/11747. Note, though, that some repos don't currently generate read-the-docs documention. For the "A1" example, though you see a new documentation version in this URL: https://readthedocs.org/projects/o-ran-sc-ric-plt-a1/builds/
    3. Thoralf on holiday on Oct-10. Sunil?
  14. I release content

...