...
| UTC-time | every 2nd Tuesday, check from calendar | |
| New York (EDT / UTC-5) | 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) | every 2nd Tuesday, check from calendar | +358 341092129 |
| Other international numbers | World Time Zone Map | International numbers available: https://zoom.us/u/acyy3hylQi |
2021-02-16
...
- discuss how to proceed with RIC-184. OTF,. robot. Maybe schedule another meeting during this week,
- update from HCL: User stories created under RIC-184 (InProgress)
- Got credentials for OSC lab created for Alok facilitated by Felix.
- Requested Felix, for rest of the credentials for HCL team members
- Working with HCL local IT team for VPN client whitelisting
RIC-723 - [Study performance overhead of latest opentracing solutions] – InProgress
- We be going through the content shared by Thoralf from previous effort of opentracing based work
RIC-731- [Static code and test coverage for E2] - 90% Completed.
- Blocked for Developer’s response.
RIC-671 [Achieve level "passing" in CII]
- Internally discussed the requirements for Epic.
- Need a setup call with Thoralf this week for clarifying & grooming the stories. Alok created a gap analysis. Alok to call for a meeting.
RIC-150 - Perform e2e RIC benchmarking
Subtask: RIC-741 Verify Subscription flow using RMR API Subscription Request and response verification done using kubectl api and calculated latency on RoundTripTime of subscription flow in nanobot automation
Subtask: RIC-742 Verify Indication flow using RMR API Currently working on latest code of bouncer xapp and e2sim to validate the indication message flow locally using nanobot. Working on CDF (distribution function) plotting to represent latency vs throughput on the message flow.
RIC-743 Create multiple e2sim for RIC benchmarking
Benchmarking the code with 1500+ E2SIM, But the result is not stable (only 50 or 700 E2 nodes are connected). "moving up from 50 is not yet stable". Currently checking on this.
- Try to make this reproducible. Maybe someone from E2T/E2M can take a look at it,
RIC-744 Verify the E2E communication for multiple e2sim // adding the sleep timer after every GNB sub request that has reduced the number of message rejection on subMgr side. It like the 1 is rejected out of 5 messages. // Debugging the issue // continue by e-mail with committers.
- Dhjiraj to talk to Sangeetha on the automation side.
- E2AP config transfer (Rahul)
- Rahul to send a mail on the type of octet strings we might have.
- A1-EI design updated: A1-EI_v2.pptx
RICAPP agenda: RICAPP Meetings.
2021-02-02
Recording: near_rt_ricplatform_and_ricapp_meeting_2021_02_02.part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2021_02_02.part2.mp4
...