...
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 in the winter (+2 during DST)) | 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 |
Delhi (IST // UTC +5:30 | every 2nd Tuesday, check from calendar | TODO |
Other international numbers | World Time Zone Map | International numbers available: https://zoom.us/u/acyy3hylQi |
2023-12-05
Recording:
- 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).
- Last checked on 2023-09-26
- TODO
- Last checked on 2023-09-26
- every second time: Review code coverage stats and blocker code smells
- We take a look at the two links in the beginning of this page: Code coverage reports..
- 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)
- Thoralf did this last on 2023-05-23: we did not do this this time
- Every time: Check if there are new bug reports in JIRA: link
- RIC-1025 memory leak in routing manager
- RIC-1017 xapp-frame - xapp-frame may not be able to successfully subscribe to messages
RIC-1016 e2t sctp_params structure may not be initialized properly → Nokia
RIC-1015 e2t too High default message size. → Nokia
RIC-1014 e2t potential race condition in the `listener` function due to multiple `listener` threads. → Nokia
RIC-1013 e2t e2term pod does not become ready. Possible stack/heap corruption
- RIC-1002 (Nokia fixes) Abnormal signaling process cause E2Term crash (this could be a security issue)
- RIC-1001 CVE-2023-41627 RMR service should verify route tables - Alexandre will take a look
- RIC-991 CVE-2023-40997 RMR related (not a duplicate) - Alexandre will take a look
- RIC-989 CVE-2023-40998 RMR (minor) security issue - Alexandre will take a look
RIC-972 (Naman) URL for A1 mediator to align with spec. → CLOSED- RIC-965 RMR wormhole connections uses stale endpoints to make connections
- 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)
- RIC-915 dms_cli for installing xapp not working (raised by James)
- RIC-905 new (from PW) Issue in reporting the CLEAR ALARM as VES EVENT
- RIC-901 new (from PW) BUG FIX IN 'Get ALARM INFO’ NETCONF COMMAND
- RIC-896 xapps sending same msg type and sub id fails - details to be clarified
- RIC-894 long idle period (days) causes RMR connection breaks
- RIC-864 xapp-frame-cpp CI does not use Dockerfile and therefore uses Ubuntu18.04 (not 20.04) in build
- RIC-857 sporadically RMR takes multiple minutes before being "ready"
- RIC-852 Intermittent Issue with E2T: While setting up E2 setup request and response.
- 2021-12-21: Trying to get bandwidth for this during F release.
- RIC-837 RMR is not forwarding messages from E2T to E2M
- RIC-835 → 2021-12-07 no news from Viktor
- fixed:
- James: updates?
- 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.
- 2023-09-26: This was presented in TOC (See link). Cases relevant for near-RT RIC:
- ODU-high and near-RT RIC (currently using stub).
- near-RT RIC and xApp (KPIMON/bouncer or maybe adding CCC xApp)
- near-RT RIC and non-RT RIC (A1) - next step on non-RT RIC side (A1 standalone mediator provided)
- James will check with Sunil on issues he has with the test cases
- ArgoCD used by Taiwan lab in some ONAP SMO case and the engineers there where wondering if something similar could be done with OSC.
- 2023-10-24
- updates from O-RAN f-2-f:
- nephio and OAI discussion: Nephio team would like to add RAN components (OAI, OSC, and parts of the OSC SMO (via Seshu) into R2 (~Feb2024)
- OAI had three demos. One of them is about improving QoE with H release of near-RT RIC using some code copied from KPM and hello world xApps.
- see demo "oai-osc-ric-demo.mp4" in link and the demo session recording on the O-RAN web site (thoralf-todo)
- more discussion coming at the joint OSC/OAI workshop in Boston
- session on SCCL did make some progress in that WG10/WG6 understanding improved. Additional discussion scheduled under O-RAN umbrella for Oct-31.
- OSFG discussed on the super wireless footprint (matrial available at O-RAN OSFG)
- updates from O-RAN f-2-f:
- 2023-11-07
- James is working with Taiwan lab on making sure we have good coverage
- 2023-11-21
- was at OSC-OAI conference
- could start using team accounts to test beds from Colosseum (NU) and ARA
- discussed with Bimo (Taiwan lab) on pair-wise testing
- discussed with John Keeney (non-rt ric ptl) and discussed A1 pairwise testing. Asked from Sunil what's best A1-policy using xApp. None exists on open-src side. Naman commented that for Policy the hello-world xApp (C++ likely) could be used (just requires RMR route for policy type (must match the policy type that is created via curl)). James to contact Naman if help needed.
- Prashant's work in near-RT RIC(subteam-p)
- 2023-08-22, 2023-09-26. 2023-11-07: could not participate
- Sunil updates (subteam-h)?
- 2023-09-12: can give update next time. Maybe 2 or 3 items to work on.
- 2023-11-07: Not in the call today
- 2023-11-21: no updates. Difficult to find engineers working on this.
- Subhash/Naman updates (subteam-s) ?
- 2023-08-29: no news, other than Naman working on the operator implementation.
- 2023-09-12:
- 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.
- Thoralf to figure out a way to start A1 mediator standalone for CI testing
- Thoralf sent instructions to John → DONE
- 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.
- Naman also works on the operator implementation
- 2023-09-26:
- kubernetes operator new repo needed or not?
- xapp deployment → appmgr or ricdms
- ric platform → ric-dep (still work in progress) - check if operator can use helm chart defined by Abhijit.
- What happened to kserve adapter? → Subhash can check.
- kubernetes operator new repo needed or not?
- 2023-11-07
- Naman presented his k8s operator work. Naman used Kubebuilder
- still working on operator to deploy RIC platform
- 2023-11-21:
- k8s operator commits - needs to be finalized.
- Abhijit updates (subteam-ag) ?
- 2023-10-24:
- Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil
- no progress in review on the plain helm chart based deployment in https://gerrit.o-ran-sc.org/r/c/ric-plt/ric-dep/+/11743 → to be merged by Thoralf Czichy
Abhjit raise RIC-1013 ... RIC-1017 for issues he has discovered. Thoralf to find someone to work on it → most assigned to Nokia- 1 and 2 of RIC-1004 still be finailized this week. Rest to be moved to a new item.
- Sunil asked about the Rust xApp → ready with basic hello world scenario. Documentation is best placed into readme and confluence.
- Abhijit and James release new base image: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/bldr-ubuntu22-c-go:0.1.0 → still to be made 1.0.0 → Reminder Abhijit Gadgil
- 2023-10-24:
- Cap Gemini updates (subteam-cg)?
- 2023-11-07: after discussions on the topic we would like to proceed with
Phase1: Conflict Manager (running as a platform component) without E2SM parsing which means that Conflict Manager feature will work only for Conflict Aware xApps. Interface between Conflict Aware xApp and Conflict Manager will be gRPC.
Phase2: E2SM xApp support so that the Conflict Manager feature works for Conflict Unaware xApps as well.
- discuss-with-Sunil-on-when-and-how-in-terms-of-repo-creation → we agreed to come back to this in 1H2024
- TODO-thoralf-to-ask-Gunja-to-present- Thoralf
- 2023-11-07: after discussions on the topic we would like to proceed with
- Himanshu (subteam-gs) would like to work on RIC-963
- 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".
- 2023-11-07: addressing review comments of https://gerrit.o-ran-sc.org/r/c/ric-plt/submgr/+/11681 tomorrow. Then we should be able to merge this.
- 2023-11-21: as discussed in teh beginning of the meeting. Review comment still being worked on. Once handled, pls. merge. And wer handle commits as piecemeal small items.
- Dhiraj (subteam-r)
- 2023-08-22:
- checking compliance/license issues
- 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).
- 2023-08-29:
- got clarity on license issues and now waiting for internal approval before publishing ipv6 releated changes
2023-11-07
license topic still be discussed. Was working on an other project for last months
- 2023-08-22:
- Alexandre (subteam-utfpr)
- 2023-08-29: Alexandre working on RIC-989 and RIC-991. Will also take a look at RIC-1001
- 2023-09-26: subscription message issue with encoding E2SM parts. A. will send e-mail to Thoralf
- Nokia (subteam-n)
- .RIC-997 likley being postponed.
- I release content
- we mark items that you are >90% sure (=”committed”) to work on during 2H2023 with your label, like subteam-n (Nokia), subteam-s (Samsung) and so on. Items that are proposed for I release but not “committed” we mark with subteam-n-proposal, subteam-s-proposal and so on. To ease usage I created a couple of filters for follow up. See §7.3 from Jira usage conventions.
- input for release candidates: left overs and generally open items, RSAC
- Sprint dates
- Sprint I release dev sprint 1: Aug-21 to Sep-10
- Sprint I release dev sprint 2: Sep-11 to Oct-1
- Sprint I release dev sprint 3: Oct-2 to Oct-22
- Sprint I release dev sprint 4: Oct-23 to Nov-12 (last planned development sprint)
- Sprint I release dev sprint 5: Nov-13 to Dec-3 (only for unplanned last-minute development items)
- Plan (v03 as of 2023-08-18):
- I release plan moved to I release page.
- RICAPP agenda: RICAPP Meetings.
2023-11-21
Recording: link to zoom recording
...