Meeting Info
RIC project meetings are open to the public and held on Tuesdays at 2pm UTC. World Time Zone Map
Zoom 1 Info:
- Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/9644759813
- Meeting ID for dial-in: 9644759813
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-02
Recording: TODO
- We would like to introduce a minor branch from Cherry in which we combine Cherry with the xApp onboarding feature. This way we have a stable branch (as compared to master) against which xApps can be developed that require this change.
- fixes done to cherry we will also do to "cherry-plus-onboarding" (exact branch date to be checked with Felix, but it should be soon (this or next week)).
- only branch is in components that actually have a change.
- all Dawn features continue on master (no similar approach for such features)
- Moved the following items from subteam-n back to subteam-n-proposal
RIC-71 Subscription manager: Better debugging capabilities
RIC-226 fix for SDL (C++) silent hang
RIC-330 Merge individual library repos (lib) python into framework repo. Also for C++ and for Golang
RIC-366 A1 API as higher abstraction level in xapp framework SDK (golang)higher abstraction level in xapp framework SDK (golang)
RIC-373 O1 mediator to check health of all platform components and expose this via O1
RIC-421 O1 mediator to handle restart gracefully
- please check your contribution plan and mark things as "soft commitment" like subteam-X. and things that you don't commit to as "subteam-X-proposal". Once done, send me a e-mail with that fact. Deadline: Feb-9-2021
- links under §7.5 in Jira usage conventions
- A1-EI
- only minor update to slideset and that serves as design proposal according to which implementation is done.
- configuration update concept.
- further discussion by mail.
- RICAPP agenda: RICAPP Meetings.
2021-01-21 4th meeting on Dawn planning
Recording: RIC_and_RICAPP_dawn_planning_2021_01_21.part1.mp4 and RIC_and_RICAPP_dawn_planning_2021_01_21.part2.mp4
- discuss CII badging page: CII status: near-RT RIC
- HCL wanted to some work related to CII: (1) code scanning for vulnerabilities (owasp tool and more tools) (2) continuation of static code analysis (E2T)
- contact on LF side is: trishan de lanerolle (tdelanerolle@linuxfou....org)
- HCL Sangeetha take a look if we can do dsomething for CII "The project MUST have evidence that the test_policy for adding tests has been adhered to in the most recent major changes to the software produced by the project."
- HCL wanted to some work related to CII: (1) code scanning for vulnerabilities (owasp tool and more tools) (2) continuation of static code analysis (E2T)
- RIC-671 mark to E and Dawn
- RIC-636 and RIC-635 Ramesh is checking
- RIC–114: Thoralf to remove from HCL and create new item for INflux-based time series support. Thoralf created RIC-734 after the mneeting and removed RIC.-114 from HCL and dawn
- RIC-682 (Samsung) - look if the only remaining item in it (RIC-382) make sense and if you want to work on this.
2021-01-19
Recording: near_rt_ricplatform_and_ricapp_meeting_2021_01_19.mp4
- Implementation of RIC-114 (redis time series plugin) - Ramesh
- move out from Dawn: RIC-114
- create new item for InfluxDB Relay integration and unless we see issues we include it always into Near-RT platform, but only for xApp usage. No need to have an abstract SDL interface that hides the actual underlying Time-series DB. Still to be discussed: Only put this in xApp framework if we can fully hide the fact that it is InfluxDB or put dependency on InfluxDB into xapp framework. Pending Also WG3 work.
- E2APv1.1 vs E2APv2.0 and do we upgrade to E2APv1.1. Do we define configuration transfer and OID in E2 Setup as mandatory (as in E2APv2.0) even if in E2APv1.1 they are optional?
- E2SIM work also needed. Need to bring this up in TOC as it might affect other E2 nodes implementations on DU/CU.
- thoralf to schedule a meeting on this with Rahul/Subhash/Rittwik for next week Wednesday/Thursday
- FYI: Dhiraj (committer in E2T) would like to have discussion with Alok on RIC-731. He (Dhiraj) will call a meeting, To get some understanding of how this was done for other repos and what Alok is planing.
- Subhash wants to discuss A1-EI. We agreed to
A1 mediator should provide the mechanism to receive EIJobResult and further send it to xApp over RMR.
- xApp should use preconfigured EITypeID to create EIJob.
- going through current list of Dawn items and checking commitments - meeting on Thursday, 8am, ET.
- RICAPP agenda: RICAPP Meetings.
2021-01-05
Recording: near_rt_ricplatform_and_ricapp_meeting_2021_01_05.mp4
- discuss RIC-708 on whether AT&T or Samsung can work on the python and c++ subitem for the xapp framework (mentioned in description of RIC-708). Matti said the python part AT&T could work on. To be checked by Matti.
- E2AP 1.1 spec high level discussion (raised by Rahul) - slideset presented, next step is to continue by e-mail disucssion (Matti, Thoralf, E2M/E2T committers, )
- A1-EI discussion. Subhash waiting for comments from Matti. Also there was some discussion on the "EI result object" (received by xApp/near-RT RIC). EI result object expected top be provided by EI data producer, while job is managed by non-rt RIC. I.e., there's an interface between non-RT RIC and EI data producer on informing about jobs (and URL targets for the EI result objects).
- HCL (Alok) to report on quick analysis on "more advanced" LF CI/CD pipeline that we might want to use in context of OTF (integration track).
- uses gitlab-based CI. for continuing testing LF uses XTESTING
- Alok shared the link from opnfv: http://testresults.opnfv.org/functest/xtesting/
- Alok still discuss with nanobot folks and Felix how current verification is done. (infrastructure testing?)
- Subhash asked about existing robot test cases and how they would be integrated.
- Ramesh commented that ONAP is more aligned with LFN and that's one of the reasons we are looking into this.
- RICAPP agenda: RICAPP Meetings.
2020-12-22
Recording: near_rt_ricplatform_and_ricapp_meeting_2020_12_22.mp4
- we started 15 minutes late
- next meeting Jan-5-2021
- For 2021: HCL (Alok) to report on quick analysis on "more advanced" LF CI/CD pipeline that we might want to use in context of OTF (integration track).
- A1/EI implementation plan A1-EI-HLD.pptx
- RICAPP agenda: RICAPP Meetings.
2020-12-08 dawn planning
Recording: RIC_and_RICAPP_dawn_planning_2020_12_08_part1.mp4 , RIC_and_RICAPP_dawn_planning_2020_12_08_part2.mp4 and RIC_and_RICAPP_dawn_planning_2020_12_08_part3.mp4
2020-12-08 main project meeting
Recording: near_rt_ricplatform_and_ricapp_meeting_2020_12_08_part1.mp4 and near_rt_ricplatform_and_ricapp_meeting_2020_12_08_part2.mp4
- CII badging status (end of Cherry) needs to be filled in: CII status: near-RT RIC
- nobody volunteered. Thoralf to do this.
- committers changed for E2T and E2Mgr. For A1, for ric-dep
- Dawn planning: See §7.5 for filters for Dawn planning. We use labels:
- preliminarily committed: subteam-n, subteam-h / h1, subteam-s / s1 / s2, subteam-a
- proposal to other team: subteam-n-proposal, subteam-s-proposal, subteam-h-proposal, subteam-a-proposal
- demos in December for Dec-17? let me know if there's something to demo.
- HCL proposed demo of benchmarking
- meeting on Dec-22? We will keep the meeting. What about Jan-5? Also ok.
- HCL status
- HCL: RIC-149: Review comments completed. Merged. DONE
- HCL: RIC-150: Code committed and Merged. completed part in Cherry (log-base checking), but more work in Dawn (API based checking)
- HCL: RIC-109: Merged. marked as DONE
- HCL: RIC-360: Code submitted & Merged CLOSE once gerrit review in RIUC-678 is done (see open review https://gerrit.o-ran-sc.org/r/c/it/dep/+/5237)
- HCL: RIC-509: Merged. CLOSE in JIRA DONE
In Progress:
- Enhancing E2E packet flow between xapp and e2sim by adding APIs to capture and parse the packets
- RIC indication message decoded in bouncer xapp. Multi E2 connection setup in progress.
- Samsung: no updates related to Cherry.
- RICAPP agenda: RICAPP Meetings.
For Dawn planning meeting:
- Dawn-R7 starts this week and is up to about Mar-5, Dawn-R8 starts Mar-6 and ends ~Apr-26
- RIC-705/RIC-706 subteam-s or subteam-a?
Older meeting minutes
check from here: Project meetings (old)