Page History

...

1. record-to-cloud. Note we change the recording format and I will post after the meeting in the meeting minutes a publicly available link like this one: link. This allows reading the audio transcript and fast-forward to places in the video that are highly-relevant. The transcript usually take a few hours before available. The video is available immediately.
2. Regular items:
   
   1. Every time: Check that all large 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/lib/rmr/+/5748 OK
      2. https://gerrit.o-ran-sc.org/r/c/ric-plt/rtmgr/+/5743 NOK - Thoralf contacts committers. Bug report RIC-764.
      3. https://gerrit.o-ran-sc.org/r/c/ric-plt/lib/rmr/+/5681 OK
      4. https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/5640 OK
      5. https://gerrit.o-ran-sc.org/r/c/ric-plt/libe2ap/+/5617 OK as documentation commit
   2. every second time: Review code coverage stats.
3. Snapshot (2021-03-16) jira_dawn_near_rt_ric.xlsx  // Always latest view from JIRA: Content of Dawn: 31 items planned: link and 15 "stretch goals": link

4. RIC-671 (Alok) Who did originally pointed us to the “LF security” service? Which security issues it actually discovers that we do not already cover with Sonarcube? Does it actually address “container scans” for vulnerabilities? Does it cover scanning for including of vulnerable libraries or modules, like go modules? If we decide to go forward, we need to … (1) decide if we create a “meta project” entry similar to, e.g., CNCF? Like “O-RAN software community (O-RAN SC)” under which we then have separate projects, like, Near-RT RIC, which in turn will include a certain number of repositories?

   1. RIC-671 [Achieve level "passing" in CII]   Requested Thoralf for submitting application for ORAN project onboarding on LFN security. // Also explored LFN inputs using nexus IQ. The example jobs failed into sandbox. Will continue to work on it.
   2. Alok to schedule a meeting on this
5. Initial discussion on alpine base images. We handle by e-mail. At least QP xApp uses alpine (the same was as A1)
6. HCL Items:
   1. RIC-184 - [Adapt to latest K8S and helm (testing in OSC labs)] - InProgress VPN access enabled waiting for Felix to create VM in T-lab & share details.  – Pending In the absence of VM provisioned in Tlab, VM was created in HCL Lab & tested with k1.18 with helm3. The logs were shared with Thoralf & two minor bugs reported ( RIC-761 for dbaas & RIC-762 for helm3). The fix for both bugs have been submitted into Gerrit review by respective owners.
      1. Subtask: RIC-746 Run nanobot based test automation from - it/test repository on RIC with k8 1.18/helm3 in OSC Lab  // Nanobot Testing in progress on latest helm version and k8s.
   2. RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress // Able to generate sampling data after getting some help from thoralf. Continue to work with other scenarios to compare with previous results.
   3. RIC-731- [Static code and test coverage for E2] -  90% Completed. Blocked on RIC-760 for test coverage.
   4. RIC-150 - Perform e2e RIC benchmarking
      1. Subtask: RIC-741   Verify Subscription flow using RMR API // Code committed and sent for review
      2. Subtask: RIC-742 Verify Indication flow using RMR API // Code committed and sent for review
      3. Subtask: RIC-754 KPIMON xapp validation using nanobot with SDL // KPIMON deployed and it is running. Validating the packet flow between KPIMON & E2SIM. – InProgress
   5. RIC-743 Create multiple e2sim for RIC benchmarking // Able to connect 800 e2sim nodes to the ric platform. Number of connected nodes drops after scaling. Tested with  with 1500 E2 node iterations.  // Collecting the logs and document the observation in a Jira Ticket (still pending)
   6. RIC-744 Verify the E2E communication for multiple e2sim // Debugging the issue on subscription response messages with multiple e2simulator – For 10 E2 SIM, RIC subscription Request and response is working fine. // Now scaling it for 800+ RIC Subscription request/response.
      1. Thoralf asked Himesh: Could you provide a description of what you did and what happened in the failure case and where we currently are.
7. InfluxDB issue (simple single-instance should be enough).
8. configuration handling in E2AP seems to settle down. Rahul (not in meeting today) will finalize via e-mail.
9. Subhash (Samsung) asked about t-lab access. About VMs OSC Community Lab Note that HCL is also working on this. Matti looking for someone from ATT to help (Felix busy).
10. RICAPP agenda: RICAPP Meetings.

...