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

2020-01-21

Recording:

1. Review and agree to minutes of previous meetings
2. We have this meeting intentionally one week after the previous one. To align on even weeks.
3. RSAC health case use discussion
4. RICAPP agenda: RICAPP Meetings.

2020-01-14

Recording: near_rt_ric_platform_project_meeting_2020_01_14.mp4

1. Review and agree to minutes of previous meetings
2. Propose to have every even week and next meeting would be on 2020-01-21. This is to align with O-RAN alliance meetings. This was ok-ed.
3. JIRA conventions for release B planning: Jira usage conventions . We take a quick look at the current Epics in JIRA.
4. RSAC use case on health check seems difficult to digest. Further discussion needed. Direction is to use alarm management, and statistics for alarm monitoring. Actual health checks based test messages also needed, but details still open.
   1. John to move the updated health check document into a RSAC wiki page by Thursday. Further updates can be done there.
5. RICAPP agenda: RICAPP Meetings.

2019-12-17

Recording: near_rt_ric_platform_project_meeting_2019_12_17.mp4

1. Review and agree to minutes of previous meetings → OK
2. Next meeting will be in 2020 on January, 14.
3. tentative: JIRA conventions for release B planning: Jira usage conventions
4. RSAC use case on health check seems difficult to digest. Further discussion needed.
5. RICAPP agenda: RICAPP Meetings.

2019-12-03

Recording: near_rt_ric_platform_project_meeting_2019_12_03.mp4 (last 25 minutes lost due to Zoom software not working correctly)

1. Review and agree to minutes of previous meetings → OK
2. Amber press release should be out today.
3. ASN.1 compiler asn1c is now maintained outside of O-RAN SC in https://github.com/nokia/asn1c Related e-mail: link
4. December, 17 is the last meeting in 2019. Dec-31 we skip due to holiday season. First meeting in 2020 is on January, 14.
5. Status on this? No progress yet. We're working on good instructions. For now the best is to start reading README.md in the repo "it/dep" (https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree). This is maintained outside of the RIC platform project, though. Eventually, we will have the RIC platform deployment in ric-plt/ric-dep. We are also working on an xApp developer guide for how to develop an xApp in golang. Thoralf to check how we could do this for C++. There is value in the guideline describing a "base". It does not have to describe each and every option. Instructions should work on REC Akraino blueprint and on plain K8S. LE-status-20191204: Waiting for Felix' cleanup work (currently in review). After this 5 working days.
6. Related to the developer guide: current idea is to talk about (1) Helm Charts, xApp descriptor and schema files, (2) HTTP interface for K8s health probes (aliveness, readiness), (3) RMR interface for communication with other RIC components, (4) Logging, (5) SDL, (6) Config managements (Configmap), (7) metrics creation. If we do not have a E2SM coming soon into WG3, then some simple hello-world E2SM would be good as a base for a demo/sample xApp. We need to consider if we can use the demo1 xApp for the documentation. For C++ let's use a simple E2SM (which has nothing to do with X2). Aim for combined document go and C++. LE-20191204: Thoralf asked from Antti. No reply yet.
7. SDL Dev guide = 20191213 (LE given on 20191204)
8. Status of RMR library which will include new MEID handling and update of the documentation related to this.
   1. RMR-routing manager and E2T-to-routing-manager interface is now designed. Scott is optimistic that RMR part is ready by end of this week.
   2. Matti to at design of MEID routing in RMR under RMR wiki pages as "RMR MEID routing - draft design"
9. Some question related to SDL library from Bengi (primarily developing C++; possibly python).
   1. Q: SDL user guide is needed. Should include some design principles and the big picture. E.g. why there are some constraints on the data types that can be used (e.g. using ordered sets). What is the role of event API and timer API, and when to use own namespace, role of access libraries for read and write APIs (e.g. R-NIB API of E2 manager (go)). Best practices around that also needed. TODO-Thoralf-ask-SDL documentation to go into open-src wiki.
10. Input from the TS use case for Bronze: "how do we update ML models" is one question we need to address in RICP
11. Need to plan how we use JIRA in RIC
12. RICAPP agenda: RICAPP Meetings.

2019-11-19

Recording: near_rt_ric_platform_project_meeting_2019_11_19.mp4

1. Review and agree to minutes of previous meetings
2. Release names: Amber, Bronze, Cherry are now decided.
3. INFO.yaml files should now be ready (exceptions: RSM and rtmgr). Committer management still requires approval by ToC. Plan is to change this approval practices for release Bronze. Once approved, PTL or delegate must update INFO.yaml with new/changed names and reference to approval. We might go for a solution where existing committers must approve and ToC only is notified, but this is not changed yet.
4. Amber release status by repo: Project Readiness for Amber Release#(NearRealtime)RICPlatform
5. All license exceptions (code re-used form other sources) are now listed here: https://wiki.o-ran-sc.org/display/ORAN/License+Attribution+Records To be approved by TOC on Wednesday, Nov-19.
6. We're working on good instructions. For now the best is to start reading README.md in the repo "it/dep" (https://gerrit.o-ran-sc.org/r/gitweb?p=it/dep.git;a=tree). This is maintained outside of the RIC platform project, though. Eventually, we will have the RIC platform deployment in ric-plt/ric-dep. We are also working on an xApp developer guide for how to develop an xApp in golang. Thoralf to check how we could do this for C++.
7. RICAPP agenda: RICAPP Meetings.

2019-11-05

Recording: near_rt_ric_platform_project_meeting_2019_11_05.mp4

1. Review and agree to minutes of previous meetings
2. Amber release status by repo: Project Readiness for Amber Release#(NearRealtime)RICPlatform
   1. as part of this Paul asked, can someone actually deploy the RIC platform? Bengi clearly said that getting other RIC platform components up is difficult.  Documentation needed.
3. Documentation guidelines: https://wiki.o-ran-sc.org/display/DOC#DocumentationHome-RequiredFiles and Configure Repo for Documentation
4. New component request to be made for Resource Status Processor. Compare to Resource Status Manager (defined here).
5. Proposal: new component: resource-status-processor

   The resource status processor handles incoming E2 resource status report messages and saves the data from these messages into the RNIB. Note that control or management of resource status reporting is not done by this processor, but by the Resource Status Manager. Committers: Shuky Har-Noy, Hila Anina, Yaki Ratz

6. I will also propose change of committers to TOC:
   1. ric-plt/rtmgr: existing committers work on other project. New ones (all Nokia): Nithinsen K and Abdulwahid W
   2. ric-plt/submgr: existing committers work on other project. New ones (all Nokia): Anssi Mannila, Juha Hyttinen
7. We plan to work on O1 implementation using "sysrepo data store plus netopeer 2" over the next few months. We also plan to work on A1 implementation and scalability if E2 termination component. Eventually this work is likely to become b-release content.
8. There will soon be coming changes in E2 definitions that we are currently using in near-RT RIC.  Once WG3 settles on a stable draft specification we can start adapting.
9. RICAPP agenda: RICAPP Meetings.

2019-10-22

Recording: near_rt_ric_platform_project_meeting_2019_10_22_part1.mp4 and near_rt_ric_platform_project_meeting_2019_10_22_part2.mp4

1. Review and agree to minutes of previous meetings
2. Discuss repo changes before sending them as one batch to TOC for approval.
3. Release B planning: Contributions
4. O1 in Release B?
5. RICAPP agenda: RICAPP Meetings

2019-10-08

Recording: near_rt_ric_platform_project_meeting_2019_10_08_part1.mp4 and near_rt_ric_platform_project_meeting_2019_10_08_part2.mp4

1. Review and agree to minutes of previous meetings
2. Review and approve Scope of the RIC platform and its components (summary). After approval next step is to inform this to TOC. This was discussed. No further comments. Thoralf to bring this to TOC and to discuss the sentence "This source code is part of the near-RT RIC (Radio Intelligent Controller) platform project (RICP)" in TOC, esp. with Jack
3. B-release content. O1 southbound - if netconf based - as per Matti mainly related to xApp manager. O1 simulator RU and DU (requires yang as input). Provide yang models for RIC (with managed objects). Ritwick to post b-releas analysis in RSAC wiki page.
4. FYI. RICP presentation at ONS, Antwerpen, 2019: Overall architecture (not component-specific)
5. E2AP documentation in gerrit: https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/asn1-documents.git;a=tree
6. RICAPP agenda: RICAPP Meetings

2019-09-24

Recording:RICmeeting9-24.mp4

1. Review and agree to minutes of previous meetings
2. Open action item from last meeting: Thoralf Czichy : status check for each item with owners of JIRA item. 2019-09-24: Still open.
3. There are no particular issues being discussed in RICP in this session. So this will focus on RICAPP.
4. RICAPP agenda: RICAPP Meetings

2019-09-10

Recording: near_rt_ric_platform_project_meeting_2019_09_10.mp4

1. Review and agree to minutes of previous meetings
2. Discuss draft status report for RICP: Project reports
3. Who hosts next meeting on 2019-09-24 (Thoralf at ONS (Open Networking Summit) Europe, e.g., presenting RIC link )? → Matti
4. Open action item Thoralf Czichy : status check for each item with owners of JIRA item.
5. RICAPP agenda: RICAPP Meetings

2019-08-27

Recording: near_rt_ric_platform_project_meeting_2019_08_27.mp4

1. Review and agree to minutes of previous meetings
2.  T1 = Antti, T2= Juha, T3 = Abdulwahid (was Viktor), T4 = Itamar, T5 = Rajesh, T6=Lusheng, T7=Bharath. All RIC items marked with suggested primary owner of the item. Thoralf to write e-mail to each suggested owner on status for each item. Initial JIRA filter: link. 
   1. need feedback by each PO by end of September - to facilitate release B planning.
3. RICAPP agenda: RICAPP Meetings

2019-08-13

Recording: near_rt_ric_platform_project_meeting_2019_08_13.mp4

1. Review and agree to minutes of previous meetings
2. Any objections to this proposal from RICP and RICA PTL: Meeting moved one hour later to 13:00 UTC. We will handle the meeting for the RICP (near-RT RIC platform) and RICA (RIC xApps) projects together. The respective PTL will handle their part. First 30 minutes with focus on RICP and the last 30 minutes focus on RICA. Note that if RICP takes less than 30 minutes, RICA issues might already be handled before 13:30 UTC. The meeting will be held every uneven week.
3. Release name finalized: "Amber" (former "A" release)
4. New repos (from the last 2 weeks) - see under "completed" Outstanding Resource Requests for Linux Foundation
5. NOT: If Thoralf found time to go through them before the meeting: "A" release Epics (focus on Epics that are under development) - assignment via JIRA is still missing.
6. RICAPP agenda: RICAPP Meetings
7. Rittwik mentioned an xApp proposed by Samsung which will be discussed in more detail in another O-RAN meeting later today (Rittwik to send details). Rittwik sent the details: RSAC meetings = https://wiki.o-ran-sc.org/display/RSAC/calendars In any, case the RSAC meetings discuss release A and B planning items Zoom 1 bridge: https://zoom.us/j/9644759813   (Tue 9-10pm Eastern New York time every other week) and (Thu 9-10am Eastern New York time every other week)

2019-07-30

Recording: near_rt_ric_platform_project_meeting_2019_07_30.mp4

1. Review and agree to minutes of previous meetings
2. Notice: non-RT RIC project proposal: https://wiki.o-ran-sc.org/download/attachments/3604819/RICnon-RT_OSC_project_proposal.pdf
3. Notice the links/instructions for o-ran-sc's JIRA, e-mail, Gerrit: Tools (mailing list, JIRA, Gerrit)
   1. user-59b16 mentioned that the Thoralf Czichy need to re-check the user stories/Epics in Jira. We need to assign each item to persons (e.g. subproject leads)
4. Any ideas on Election process for new committers for RIC repos .
   
   1. Thoralf Czichy to make proposal with user-d3360
   2. (Update-Jul-31-2019: Jack Murray needs to write down a manual for this (including some ideas how to make it more efficient), ideally by  Aug-7. If not, maybe Lusheng can at least write down how it is currently handled)
5. Any ideas on Process for new repos (RIC PTL (or person nominated by PTL) suggests to TOC. TOC confirms. Repo can be created)
   1. Thoralf Czichy to make proposal with user-d3360
   2. (Update-Jul-31-2019: Jack Murray needs to write down a manual for this (including some ideas how to make it more efficient), ideally by  Aug-7. If not, maybe Lusheng can at least write down how it is currently handled)

2019-07-23 (no meeting due to holiday period)

2019-07-09 (no meeting due to holiday period)

2019-06-25

Agenda/Notes

1. Review and agree to minutes of previous meetings

2. Code review practice and bootstrapping of committers. https://wiki.o-ran-sc.org/display/TOC/Tutorials and https://wiki.o-ran-sc.org/display/TOC/Seed+Code+Contribution Contact Lusheng Ji if things are not clear (https://lists.o-ran-sc.org/g/main/message/57).

3. General available information: The release calendar: https://wiki.o-ran-sc.org/display/REL/Releases

   1. Q (Pierre-Henri): are all projects following the calendar. Ritwick: Yes, but only pairwise testing between the project components as per testing strategy and acceptance criteria in EPICs.

4. Release A requirements for RIC, but also incl. eNB and O-DU/OFH: https://wiki.o-ran-sc.org/pages/viewpage.action?spaceKey=RSAC&title=Contributions

   1. comments expected by end of US business day Wednesday, 26.Jun Comment directly to wiki page.
   2. Note that the document suggest the usage of ONAP's https://wiki.onap.org/display/DW/OTF+-+Open+Test+Framework

5. (Any preferences on rocketchat vs IRC?)