Page History

...

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. https://gerrit.o-ran-sc.org/r/c/ric-plt/sdl/+/6584  OK
   2. https://gerrit.o-ran-sc.org/r/c/ric-plt/xapp-frame-py/+/6551 OK (move of implementation from one repo to another)
2. Skipped today: 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. 1. ric-plt/a1 85,3 // no bugs (2021-01-26)

   3. 1. ric-plt/alarm-go 0,0 // no bugs (2021-01-31)

      2. ric-plt/appmgr 0,0 // 1 major bug (2021-01-31)

      3. ric-plt/asn1-documents not applicable

      4. ric-plt/dbaas 0,0 // 2 blocker bugs in UT code (2021-01-27) - seems not to be anymore in latest version of source code.

      5. ric-plt/e2 0,0 // 2 blocker bugs (2021-06-18) - Thoralf raised RIC-802 and send e-mail to Dhiraj, Subhash and Naman. 2021-08-17: RIC-802 is for subteam-n in E. No other news

      6. ric-plt/e2mgr 88,4 // no bugs (2021-01-30)

      7. ric-plt/lib/rmr 86,1 // no bugs (2021-08-17)

      8. ric-plt/rtmgr 77,8 // no bugs (2021-01-31)

      9. ric-plt/sdl  66,6 // 1 minor vulnerability bug (2021-01-29)

      10. ric-plt/sdlgo 45,5 // no bugs (2021-02-01)

      11. ric-plt/streaming-protobufs 0,0 // no bugs (2021-01-31)

      12. ric-plt/submgr 33,4 // no bugs (2021-01-31)

      13. ric-plt/tracelibcpp 0,0 // 1 major bug (2021-08-10)

      14. ric-plt/tracelibgo 94,7 // no bugs (2021-01-31)

      15. ric-plt/vespamgr 79,0 // no bugs (2020-12-07)

      16. ric-plt/xapp-frame 0,0 // no bugs (2021-01-31)

      17. ric-plt/xapp-frame-cpp 95,6 // still 2 blocker bugs (2021-08-04) - same as before. Anybody willing to work on them?

      18. ric-plt/xapp-frame-py 96,3 // 0 blocker bugs (2021-01-26)

      19. com/golog 80,7 // no bugs (2021-01-31)
      20. com/log 73,5 // 1 blocker bug and 8 minor ones (2021-01-27) - same as before. Need to fix sonarcube Sonarcube issues (with Java version) first.
      21. com/pylog 33,7 // 11 major and minor bugs (2021-01-26)
3. Every time: Check if there are new bug reports in JIRA: link
   1. new: RIC-826 (discussion ongoing)
4. Note the presentation slides and video from "Open Source Conference 2021 (5G, IoT and Edge Computing) (organized by the IEEE ComSoc Bangalore chapter and Samsung SOSCON" is now available here: Overall architecture (not component-specific)
5. E2-related specs are now in IPR approval phase on O-RAN alliance side (O-RAN alliance member only access):

   1. O-RAN.WG3.UCR-v01.00: https://oranalliance.atlassian.net/wiki/download/attachments/2068513840/O-RAN.WG3.UCR-v01.00.docx?api=v2

   2. O-RAN.WG3.E2GAP-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/213254315/O-RAN.WG3.E2GAP-v02.00.docx?api=v2

   3. O-RAN.WG3.E2AP-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/226295809/O-RAN.WG3.E2AP-v02.00.docx?api=v2

   4. O-RAN.WG3.E2SM-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/244318246/O-RAN.WG3.E2SM-v02.00.docx?api=v2

   5. O-RAN.WG3.E2SM-KPM-v02.00 https://oranalliance.atlassian.net/wiki/download/attachments/244318246/O-RAN.WG3.E2SM-KPM-v02.00.docx?api=v2

   6. O-RAN.WG3.E2SM-RC-v01.00 https://oranalliance.atlassian.net/wiki/download/attachments/244318246/O-RAN.WG3.E2SM-RC-v01.00.docx?api=v2

6. E release "committed" content: link
7. Design or coordination aspects of some items of the E release
   1. RIC-638 config transfer E2APv1.1 (Subhash)
   2. RIC-445 CLI (demo from subhash as well)
   3. NOT today: RIC-80 and RIC-796 (REST interface for subscriptions only) (Possibly Anssi)
   4. RIC-809 subscription interface (Supreeth)
   5. RIC-805 We are likely moving the "remove old API part" only in the next release, i.e., maintain old and new in parallel for one release. Team needs some more discussion before something can be presented. Namespace in new implementation is given as part of each get/set method. Previously the namespace was given during SDK initialization. During E release we will only deprecate the old interface, but keep it. Only in F release we will remove.
   6. Mavenir thinking about gRPC as communication mechanism (Matti to send e-mail address to Thoralf).
   7. Discuss disaggregated VES agent use case and impact on RIC. Thoralf
      1. This is O-RAN O1 release 6 work (July-Dec 2021). Thoralf understands it introduces a "VES proxy agent" into the Edge CloudInfra that on the left gets VES events from CNFs (e.g., via REST events, or (the new thing) a CloudInfra Kafka instance) and on the right side forwards these to the SMO (e.g., directly into Kafka). Not sure if left-side injection can also be done via O1 websocket performance data streaming.
      2. There might be some issues around data schema alignment that need to be addressed
      3. Anyway, from CNF point of view seems to be one more way of sending statistics/metrics out towards the SMO. For now let's focus on existing O1 (files or websocket streaming) means. Also note that statistics are currently collected via Prometheus. I.e., if, we'd be talking about a new or update mediator component that takes the data from Prometheus and sends it to that new "VES proxy agent".
      4. Note that performance related there are also activities under the Prometheus umbrella that might be relevant, e.g., https://openmetrics.io/
      5. So this seems not to be relevant for the E release of near-RT RIC.
8. ...
9. RICAPP agenda: RICAPP Meetings.

...