RIC project meetings are open to the public and held on Tuesdays at 2pm UTC. World Time Zone Map
Zoom 1 Info:
UTC-time | every 2nd Tuesday, check from calendar | |
New York (EDT / UTC-4 during DST (-5 in the winter)) | every 2nd Tuesday, check from calendar | +1 669 900 6833 // +1 646 558 8656 // 855 880 1246 (Toll Free) // 877 369 0926 (Toll Free) |
Paris (CEST / UTC+1) | every 2nd Tuesday, check from calendar | +33 7 5678 4048 // +33 1 8288 0188 // 805 082 588 (Toll Free) |
Beijing (CST / UTC+8) | every 2nd Tuesday, check from calendar | +86 10 87833177 // +86 10 53876330 // 400 616 8835 (Toll Free) // 400 669 9381 (Toll Free) |
Tokyo (JST / UTC+9) | every 2nd Tuesday, check from calendar | +81 524 564 439 // +81 3 4578 1488 // 0 800 100 5040 (Toll Free) |
Helsinki (EEST / UTC+2 in the winter (+3 during DST)) | every 2nd Tuesday, check from calendar | +358 341092129 |
Other international numbers | World Time Zone Map | International numbers available: https://zoom.us/u/acyy3hylQi |
Recording: todo-record-to-cloud
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?
RICAPP agenda: RICAPP Meetings.
Recording:near_rt_ricplatform_and_ricapp_meeting_2021_03_02.mp4
HCL items:
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. Sent the reminder on Thu (25th Feb). VM in T-lab still needed from Felix.
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. sampling data now available. Numbers seem to be different than from previous PDF. Alok to schedule meeting with Thoralf once enough new information is available.
RIC-731- [Static code and test coverage for E2] - 90% Completed. Had a debug session with E2 dev team today (2nd March) & we were able to get the blocker issue resolved. Looking forward to close the issue by this week & ready for submitting Gerrit changes to ci-management repo.
RIC-671 [Achieve level "passing" in CII] Received information from LFN on queries on dynamic code analysis & CLM. Going through it.
RIC-150 - Perform e2e RIC benchmarking
Subtask: RIC-741 Verify Subscription flow using RMR API Done – Still need to commit the code
Subtask: RIC-742 Verify Indication flow using RMR API Done – Still need to commit the code
Subtask: RIC-754 KPIMON xapp validation using nanobot with SDL : KPIMON Xapp deployment got crashloopbackoff state. Sent mail to the committer (Jinwei.fan@samsung.com) to confirm on this.
RIC-743 Create multiple e2sim for RIC benchmarking Able to connect 800 e2sim nodes to the ric platform. Number of connected nodes drops after trying to scale >800 (Tests fail with 1500 E2 node iterations).
RIC-744 Verify the E2E communication for multiple e2sim Transaction ID issue has been resolved. Now debugging the issue on subscription response messages with multiple e2simulator.
RICAPP agenda: RICAPP Meetings.
check from here: Project meetings (old)