2021 Q2 (Apr, May, Jun)
2021 06 30
Recording: link to zoom recording
Agenda
Call for Scribe (minutes owner): Masafumi Masuda
Roll Call & Quorum Check
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.
Review and Agree to Minutes of Previous Meeting
Decision: For the 06/23/2021 TOC meeting minutes, motion by @MASAFUMI MASUDA, seconded by @Ganesh Shenbagaraman. Motion passed.
Review of Today's Agenda
Thoralf-to-Jinri: Any news (after your Saturday mail) on the press release on when and in which format we intend to publish?
Discuss WG6 AAL request project and repo using BSD-3
Release Votes and Approval
D Release
Jack: Matti, are we ready on RICAPP?
Matti: No. We have to decide how much integration testing we want do for the release.
Jack: What about RIC?
Thoralf: We are ready. Integration test is also limited, but we can deploy.
Jack: Did you branch the code?
Thoralf: Yes.
Jack: ODUHIGH?
Manasi: We are ready to branch the code with limited integration.
Jack: ODULOW?
David Kinsey: There was an issue with alignment between ODULOW and Viavi.
Jack: OAM?
Matti: We are ready to branch.
Jack: SIM?
ALex: We are ready to branch.
Jack: INF?
Xiaohua: The code has been branched.
Jack; NONRTRIC?
John Keeney: We have branched.
Jack: SMO?
Mahesh: We have not been able to test in the lab. We have not branched yet but could.
Jack: CII badging. ODUHIGH has gotten to passing. ODULOW is 91%. SMO is 78%.
Jinri: The major issue is RICAPP.
Jack: It's ODULOW and RICAPP.
Matti: We could say that we do the final integration in the maintenance release.
Jack: What would people's feeling about branching and packaging everything for July-2 release?
Rittwik: We should document by PTLs the flows that have been tested in the release page at least.
Jack: The decision is that all projects should branch that can branch, that the individual projects need to update the release page and that we will postpone the release date and vote for our next Wednesday meeting. How deoes that affect our PR?
Jinri; PR is fine.
Action point; PTLs to branch that can branch and to update the release page.
AAL project
Jack: I had a discussion yesterday with WG6 on their work on the accelerator abstraction layer. It's part of an extension to DPDK contribution in Linux Foundation, but they want do that under O-RAN. The tricky part is that the community specifies BSD-3 as the contribution. What the request was to create a new project for the AAL project.
Trishan: All incoming code on O-RAN SC is Apache 2.0, but for this particular repo, we would make the exception for BSD.
Thoralf: How do you formally sign?
Trishan: I will check.
Jack: We may have to add a CLA. We'll get that clarification.
Action point: Trishan to check if your have to sign a new agreement for the repo.
Jinri: For this project, what is the expected output? Is it traditional coding or documentation?
Jack: It would be both.
Jiniri: If this is a stage-3 work, why is this to be in our software community instead of WG6?
Jack; I believe this is the right way.
Juha; Will we have a project proposal?
Jack: I have a write up from WG6. We will talk about it next week and have a vote.
Action point: Jack to present the write up about the AAL project to have a vote.
John Keeney; Is there any plan to integrate the DPDK and the existing OSC functions?
Jack: That would be a discussion around ODULOW and ODUHIGH.
Ganesh: We will go through the document and will provide an update next week.
Action point: Ganesh to provide an update from ODU point of view.
Copyright update
Jack: O-RAN Board meeting happened on Monday and they approved the 2 items that affect our work in the copyright space. They approved a clarification on the copyright on the IPR statement and also approved the SCCL license for our use in the OSC-P project.
Thoralf: Will there be a written summary?
Jack: Yes. The license and the fact that they approved it will be added to the O-RAN ALLIANCE web site.
Rittwik: What is the OSC-P?
Jack: O-RAN Specification Code Project.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Old business and Status of Open Action Items
Release preparation for "D" Release
Action point: Jinri to organize release statement and PR for "D" Release.
"E" Release timeline.
Action point: Jack to create "E" Release timeline and publish.
Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
Repo clean-up:
Jack: Every repo should be attached to a project with a PTL. House-keeping and due diligence are the responsibility of the PTL.
5G Super Blueprint status - tabled for D and E, will be reevaluated for F release.
PTL company change.
Jack: I got a message from Mahesh, PTL of SMO. He has moved from VMware to Juniper. We have to decide to do going forward. Hopefully he can attend next meeting and have a dialogue.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager @Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
@Former user (Deleted) Requirements Software Architecture Committee
Integration and Test (PTL needed)
Report out from PTL: Stand-Up & Report Out on Blockers
@Mahesh Jethanandani Service Management and Orchestration (SMO)
@John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
@Matti Hiltunen RIC Applications (RICAPP)
@Thoralf Czichy RIC Platform (RIC)
@gusu O-RAN Centralized Unit (OCU)
@Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
@Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
@Martin Skorupski Operations and Maintenance (OAM)
@Alex Stancu Simulations (SIM)
@Xiaohua Zhang Infrastructure (INF)
@Weichen Ni Documentation (DOC)
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
2021 06 23
Recording: link to zoom recording
Agenda
Call for Scribe (minutes owner): Masafumi Masuda
Roll Call & Quorum Check
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.
Review and Agree to Minutes of Previous Meeting
Decision: For the 06/16/2021 TOC meeting minutes, motion by @MASAFUMI MASUDA , seconded by @Former user (Deleted). Motion passed.
Review of Today's Agenda
Release Votes and Approval
Trishan: We have Andrew from the release engineering team to discuss automated self service features.
Andrew: The proposal is that we enable the automated self service.
Thoralf: The only technical change is that after Info Yang model is changed it will be published to the TOC mailing list?
Andrew: Correct. We are proposing here is taking the government body requirement out of picture and moving to a mechanical process but you are still informed.
Thoralf: If we say we want to keep the old process, what would we do?
Andrew: Then we will keep the old process.
Jack: The vote would be to change the process. Approval of the proposed motion is that we would move to the automated process and rejection is to stay with the current process. From my standpoint, more automation is good.
Thoralf: It's a good thing and I don't see risks.
Decision: For the change to the automated process, motion by Andrew, seconded by @huangjinri@chinamobile.com. Motion passed.
Andrew: We will make the change and let the TOC mailing list know.
Copyright update
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Action Point: Jinri to lead O-RAN White paper version 3.
Action Point: All to consider engaging with WG10 for the IM / DM modelling tool chain discussion.
Action Point: @Jack Murray to work with O-RAN SFG to create a procedure for reporting bugs found during security badging in OSC.
Update from TIFG meeting with OSC.
Action Point: All to TOC members to consider working with TIFG on an ongoing basis to represent OSC. @William DIEGOoffered to support this activity with help from others.
Old business and Status of Open Action Items
CII badging.
Jack: We are hoping that the release happens next week. Regarding the CII badging, where are we on ODU HIGH?
Manasi: We need to fix some errors first. We will get it done by this Friday.
Jack: Has anyone from ODU HIGH been working with Intel?
Manasi: We have been.
Jack: How is SMO doing?
Mahesh: It will be somewhere close to 100% this Friday.
Action point: PTLs to complete CII badging process.
Release preparation for "D" Release
Jack: Is RICAPP ready for release?
Matti: No. In the OSC Lab, there are some issues. The latest E2 simulator is not working.
Jack: Does anyone know the status?
Ultan: I can help.
Jinri: Has this integration not happened completely or it's ongoing but blocked by some issues?
Matti: Some of the older versions worked.
Jack: We haven't had volunteers stepping into the broader integration project. Where are you, RIC Team?
Thoralf: We also suffer from the same problem. If somebody could try to deploy the Near-RT RIC platform and put xApp there, it would help.
Jack: OCU is not active. Where are we on ODU HIGH?
Manasi: After today's develop session, we should be able to declare completion for the "D" Release and cut the branch.
Jack: OAM?
Martin: We deployed the closed loop use case with Non-RT RIC Team and have configured with ODU HIGH using IPv4.
Jack: Who are you working with on IPv6?
Martin: Network setup team.
Jack: SIM?
Alex: We are good to go.
Jack: INF?
Xiaohua: It's ready to go by the end of this week.
Jack: NONRTRIC?
John Keeney: We are able to go.
Jack: SMO?
Mahesh: Issue has been testing in the OSC Lab.
Jack: If we list out the functionality and note in the release documentation we've got this with the simulator, it's OK.
Rittwik: Maybe in the maintenance release we can try non simulated way.
Jack: Rittwik, did you get information about the switch?
Rittwik: We are planning to insert the FH switch after the release.
Jack: Jinri, have you hade any progress on writing?
Jinri: We discussed "D" Release statement in the last EC. It has not decided whether we include it in the O-RAN PR or we need a separate PR. We still need contributing companies' quote.
Action point: PTLs to wrap up "D" Release preparations.
Action point: Jinri to organize release statement and PR for "D" Release.
"E" Release timeline.
Action point: Jack to create "E" Release timeline and publish.
Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
Repo clean-up:
Jack: Every repo should be attached to a project with a PTL. House-keeping and due diligence are the responsibility of the PTL.
5G Super Blueprint status - tabled for D and E, will be reevaluated for F release.
PTL company change.
Jack: I got a message from Mahesh, PTL of SMO. He has moved from VMware to Juniper. We have to decide to do going forward. Hopefully he can attend next meeting and have a dialogue.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager @Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
@Former user (Deleted) Requirements Software Architecture Committee
Integration and Test (PTL needed)
Report out from PTL: Stand-Up & Report Out on Blockers
@Mahesh Jethanandani Service Management and Orchestration (SMO)
@John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
@Matti Hiltunen RIC Applications (RICAPP)
@Thoralf Czichy RIC Platform (RIC)
@gusu O-RAN Centralized Unit (OCU)
@Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
@Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
@Martin Skorupski Operations and Maintenance (OAM)
@Alex Stancu Simulations (SIM)
@Xiaohua Zhang Infrastructure (INF)
@Weichen Ni Documentation (DOC)
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
2021 06 16
Recording: link to zoom recording
Agenda
Call for Scribe (minutes owner): Masafumi Masuda
Roll Call & Quorum Check
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.
Review and Agree to Minutes of Previous Meeting
Decision: For the 06/09/2021 TOC meeting minutes, motion by @MASAFUMI MASUDA , seconded by @Juha Oravainen . Motion passed.
Review of Today's Agenda.
Thoralf-asks for: approval of this request https://lists.o-ran-sc.org/g/toc/message/463 (related to com/asn1c)
Decision: For the request for archiving the repo, motion by @Thoralf Czichy , seconded by @John Keeney (Ericsson EST) . Motion passed.
John Keeney: We are still blocked on adding the PTLs as committers to the IT/DEP repo. I' d like to raise the motion to explicitly approve the change.
Decision: For the request for the addition, motion by @John Keeney (Ericsson EST) , seconded by @Juha Oravainen . Motion passed.
John Keeney: Thoralf or I will open a LF support ticket.
Jack: Matti, you can follow up Felix?
Matti: Yes.
Release Votes and Approval
Copyright update
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Collaboration between OSC and O-RAN Alliance on an SMO project definition.
Rittwik: I've been attending the SMO meetings. I'm trying to see if I can encourage EC to put priorities.
Jack: What's the ask to the EC?
Rittwik: EC is going to take a look at the summary and say go ahead with the MVP package.
Action Point: Jinri to lead O-RAN White paper version 3.
Action Point: All to consider engaging with WG10 for the IM / DM modelling tool chain discussion.
Action Point: @Jack Murray to work with O-RAN SFG to create a procedure for reporting bugs found during security badging in OSC.
Update from TIFG meeting with OSC.
Action Point: All to TOC members to consider working with TIFG on an ongoing basis to represent OSC. @William DIEGOoffered to support this activity with help from others.
Jack: There are only 2 plugfest applications responded to the Call for Hosting. I want to make sure people are aware.
Old business and Status of Open Action Items.
Release process for "D" Release.
Action point: Jack to talk to Felix and move forward the releae process for "D" Release targeting the release date of June 30 and TOC voting for approval on June 23.
Action point: Jinri to organize release statement and PR for "D" Release.
Rittwik: We have made some progress including closed-loop process usecases.
Jack: We are in the process of getting FHGW in place?
Rittwik: Thanks to Nokia.
Jack: PTLs, any other items we need to address?
Rittwik: Mahesh was buliding a SMO.
Martin: He has artifacts on the same VM.
Rittwik: I have a request to PTLs. If all the PTLs do the release process in the similar way, Felix's job will be easy.
"E" Release timeline.
Action point: Jack to create "E" Release timeline and publish.
Jack: After the "D" Release is out, let's get a short presentation to make sure we understand how the architecture looks like.
CII badging.
Action Point: PTLs to wrap up CII badging.
Jack: We are still pending on ODU HIGH.
Manasi: We are waiting for a few responses from Near-RT RIC.
Thoralf: I can ask them again.
Jack: I have to follow up Intel.
Repo clean-up:
Jack: Every repo should be attached to a project with a PTL. House-keeping and due diligence are the responsibility of the PTL.
5G Super Blueprint status - tabled for D and E, will be reevaluated for F release.
PTL company change.
Jack: I got a message from Mahesh, PTL of SMO. He has moved from VMware to Juniper. We have to decide to do going forward. Hopefully he can attend next meeting and have a dialogue.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager @Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
@Former user (Deleted) Requirements Software Architecture Committee
Integration and Test (PTL needed)
Report out from PTL: Stand-Up & Report Out on Blockers
@Mahesh Jethanandani Service Management and Orchestration (SMO)
@John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
@Matti Hiltunen RIC Applications (RICAPP)
@Thoralf Czichy RIC Platform (RIC)
@gusu O-RAN Centralized Unit (OCU)
@Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
@Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
@Martin Skorupski Operations and Maintenance (OAM)
@Alex Stancu Simulations (SIM)
@Xiaohua Zhang Infrastructure (INF)
@Weichen Ni Documentation (DOC)
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
2021 06 09
Recording: 2021-6-9.m4a
Agenda
Call for Scribe (minutes owner): Masafumi Masuda
Roll Call & Quorum Check
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.
Review and Agree to Minutes of Previous Meeting
Decision: For the 06/02/2021 TOC meeting minutes, Motion by @MASAFUMI MASUDA, seconded by @huangjinri@chinamobile.com. Motion passed.