2020 04 08
Recording: 2020-04-08_toc.mp4
Agenda
- Call for Scribe (minutes owner) Farheen Cefalu
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji Jinri Huang Co-Chair
x Weichen Ni David Streibl
x Ondřej Hudousek Masafumi Masuda
x Anil Umesh Orange William Diego
x Vincent Danno Viswa Kumar
Kristen Young Juha Oravainen
x Ganesh Shenbagaraman
x John-Paul Lane
*Quorum: 50% or more of total TSC voting members unless excluded due to attendance. We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
- The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
- Vote to approve minutes for
- On motion made by user-2057e
- Seconded by Juha Oravainen
- VOTE: Vote taken, item passed
- The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
- Review of Today's Agenda
Issue of licensing and code contributions in O-CU gerrit repos
LF investigated also
taking an unusual activity for our community, code needs to be removed
will restart the O-CU project with new, empty repos
rebuilding is the easiest way to clean up and address all concerns
re-examining some best practices
concerns?Rittwik asked, integrated eNodeB OCU or distributed eNodeB OCU?
Jack answered, Affects all OCU repos.
Jack asked, how much OCU is used in this release?
Rittwik answered, not very much.
William asked, new contributors in OCU?
Jack answered, contributors to area of concern have changed; 4G area
has been reexamined; 5G area has different contributors; focusing on
5G portion which didn't have code/licensing issues
William asked, only 4G code is impacted? 5G also?
Jack answered, going thru process for both as everything is
re-submitted, adhering to guidelines; LF giving guidance how best to
proceed.
John Paul asked, how to capture lessons learned from OCU project,
publicize to other projects?
Jack answered, this gives us an opportunity to review best practices
and make sure people are aware & complying, following well-established
open source guidelines for all projects, so other projects can avoid
complications. Rely on contributors to follow guidelines, sometimes
have to clean things up, taking a strong step to address the
concerns.
John Paul asked, these principles and guidelines, where are they
published?
Jack answered, the O-RAN-SC wiki has the page, not easy to find,
https://wiki.o-ran-sc.org/display/ORAN/Best+Practices
- Release Votes and Approval
- Vote is active to choose name of "D" release.
Leading candidate today is "Dawn"
What color is Dawn? Nobody was quite certain.
- Vote is active to choose name of "D" release.
- Marketing of the current release (WG, LF, PR)
- ONES = LF Networking Conference tentatively August/ September (Los Angeles). Open Networking & Edge Summit Event
- Status of Open Action Items (Old Business)
- Action/ new TOC members provide an alternate contact for TOC calls when they are unable to attend.
- Action / ENGWEI KOO - will add a deck to RSAC wiki.
- Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
- Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America
- Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests.
- Action/ user-59b16 upload the UE emulator short/long term slide deck to the RSAC page.
- Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
- Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times. There are 3 trains for the specifications.
Action/ user-2057e update Vote Release Name page with the D release name options.you can now vote on name for release D here: https://wiki.o-ran-sc.org/display/REL/Vote+Release+Name
- Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.
- Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney opened regarding the Calendar synchronization.
- Action/ PTLs update your project summaries with your sprint 2 status updates. Be prepared to review your sprint 2 deliverables with the TOC.
- Action/ Jack will review Thoralf's How to request committer changes
- Action/ user-d3360 add the wiki link for SONAR to the Integration and Test wiki where people can easily find.
- Action/ user-59b16 set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.
- Action/ William DIEGO we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups
- Action/ user-d3360 add the link in the Integration and Test wiki to the SONAR instructions that you discussed on TOC meeting.
- Action/ PTLs provide user-d3360 with your sprint 2 demos.
- Standing Agenda Items (Brief Status of Ongoing Activities)
- Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
- Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list. Are there any major items that anyone would like to raise to the TOC this week?
- Matti Hiltunen RIC Applications (RICAPP)
Ongoing activity RIC applications -
Matti H. gave update that a person is assigned for simulator
- Thoralf Czichy RIC Platform (RIC)
- note I updated the committer change process as per discussion last week: How to request committer changes.
Thoralf C. gave update
. many epics in Bronze release
. 8 done, 6 in progress, 38 not started
. 2 new epics related to ASN.1 problemThoralf C. asked, is there progress on ASN.1 legal issues with 3GPP and
ORAN Alliance?
Jack M. answered, writeup is being reviewed, process is onerous, have to
go to board for permission
Jinri H. answered, EC has reviewed, (?) has approved, then will forward
request to board
Jack M. answered, once approved it can be used by all ORAN projects, not
just one
Jinri H. clarified, this is for ASN.1; Hank wants to broaden request.
Current request is from Thoralf targeting specific ASN.1 content in
one ORAN specification. Want to broaden this to apply to all the
ASN.1 content from ORAN alliance. Hank wants to improve/refine the
proposal so it's a bit on hold. Expect to hear tomorrow. Once the
specific request is approved, it will apply to all projects.Held demo of development sprint 3, recording is available for people to
view
- user-a934b O-RAN Centralized Unit (OCU)
- Ongoing activity - OCU
skipped, have discussed the exception being handled there
- Ongoing activity - OCU
- Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
- Ongoing activity - ODUHIGH
Sachin of Radisys gave update
Demonstrated F1-U and F1-C
working on traffic steering implementation, that will be in next
demonstration, with limitations based on specification
working with Intel team on IPC mechanisms and L1
might have to push some content to Cherry release due to recent late
changes
expect to be formally available in ORAN wiki
Jack asked, please update wiki page to capture progress
Sachin added, seeing lots of effort required here
Jack asked, are working group specifications coming out, how is the
interface to the WGs functioning?
Sachin answered, they are aligning to specifications; also dependent on
E2 SM specifications, may have to adapt
- Ongoing activity - ODUHIGH
- Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
- Ongoing activity - ODULOW
Zhimin Yuan of Intel gave update
working on shared memory feature between ODULOW and ODUHIGH
Jack asked, have you updated wiki pages with status?
Zhimin answered, have updated for front haul library; other pieces in
development
Rittwik asked, for the WLS binary files, this is not exactly open
source, cannot see the IPC mechanisms used, is this done or in
progress?
Zhimin answered, in progress, shared with Radisys
Rittwik asked, how will it work eventually?
Zhimin answered, get approval from Intel, pass legal check
Rittwik asked, will be approved for Bronze release?
Zhimin answered, it is possible but not definite
Rittwik noted, this is a bilateral arrangement today; unclear how it
will work in the future
Zhimin answered, working for approval by end of May
- Ongoing activity - ODULOW
- Martin Skorupski Operations and Maintenance (OAM)
- Ongoing activity - OAM
Martin S. of Highstreet gave update
Working to finalize the deployment
Contribution depends on YANG models
Got in contact with 3GPP YANG developers directly for assistance
Hoping to use YANG models as basis in Cherry release
Identified use case to be proposed for Cherry, a software update from
XRAN device, becomes ORAN front-haul device, maybe O1 device
Jack suggested, get this in early to requirements group
Martin noted, Jira pages are very slow to load
Jack asked, how are demonstrations of health check going?
Martin answered, demonstration tomorrow of using a health check, but
not sure if it can be recorded; demo can be repeated anytime
- Ongoing activity - OAM
- Alex Stancu Simulations (SIM)
- Ongoing activity - simulators
Alex S. of Highstreet gave update
finally have a resource to work on simulator
hope to finish what they need for traffic steering use case
working on build job for Jenkins at LF
health check use case is implemented in the project
John is working on moving A1 stub simulator into repos
Jack asked, stub simulator in this release?
Alex answered, yes only have to move Jenkins jobs
- Ongoing activity - simulators
- Xiaohua Zhang Infrastructure (INF)
- Ongoing activity - infrastructure
Xiaohua Z. of Wind River gave update
By end of March had ARM-based K8S cluster available
Want to use third-party layer1/layer2 to demonstrate
Invites people to look at code in integration repo
working with ODULOW project so their deliverable meets requirements
hope to finish this week, plan to work with integration team in
integration lab
rest of Jira is related to platform services enabling, ongoing
schedule is challenging, have good chance to finish in Bronze
holding biweekly meetings, minutes are in the wiki
Jack asked, will ARM-based system be available to wider community, to
see the demo?
Xiaohua answered, code has been upstreamed into repo, instructions are
uploaded how to build and run demo, but Layer 1/layer 2 applications
are from third-party company, only agreed to use as demo not open
source, shows capability of ARM-based platform
Jack noted, important to have diversity in the project; please follow
best practices around open-source contributions vs test fixtures, make
clear what's open source and what is only a demo test fixture
- Ongoing activity - infrastructure
- weichen ni Documentation (DOC)
- Ongoing activity - documentation
Weichen N. of China Mobile gave update
not many new features
created a label on documentation page to switch between branches
already have amber from last year
when we release bronze release, can have selection button for bronze
next is API documentation
if any project is willing to add API doc, please let Weichen know and
he will collect the doc from different projects to form OSC API
document
Jack asked, need to pull together doc on end-to-end use cases part of
Bronze release; work with RSAC committee to understand where will we
send someone as part of Bronze release to see use cases, also a
description of how to recreate/download/build use cases as end user;
people need to learn from use cases, as projects deliver their pieces
and users come in to see what we have done
- Ongoing activity - documentation
- John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
- Reached 9am, unable to hear John's update on NON realtime RIC,
John will go first at next meeting
- Reached 9am, unable to hear John's update on NON realtime RIC,
- (TBD) O-RAN Radio Unit (ORU)
- Matti Hiltunen RIC Applications (RICAPP)
- user-59b16 Requirements Software Architecture Committee
- user-d3360 Integration and Test
- New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
- New item: OAI John Murray
- Planning for Next Meeting
- Any Other Business (AOB)
- No other new business.
- Meeting Summary (resolutions, new action items, etc.)
2020 04 01
Recording: 2020-04-01_toc.mp4
Agenda
- Call for Scribe (minutes owner) Farheen Cefalu
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji Jinri Huang Co-Chair
x Weichen Ni David Streibl
Ondřej Hudousek Masafumi Masuda
x Anil Umesh Orange William Diego
x Vincent Danno Viswa Kumar
Skand Priya Juha Oravainen
x Ganesh Shenbagaraman
x John-Paul Lane
x *Quorum: 50% or more of total TOC voting members unless excluded due to attendance. We have a quorum and can vote on activities.
- TOC Membership has increased. It has been one year of the O-RAN-SC.
- Action/ new TOC members provide an alternate contact for TOC calls when they are unable to attend.
Review and Agree to Minutes of Previous Meeting
- The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
- Vote to approve minutes for
- On motion made by Jinri Huang
- Seconded by William DIEGO
- VOTE: Vote taken, item passed
- The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
- Review of Today's Agenda
- Email from OAI
- Jack needs to share that Jinri and Jack received an email from Open Air Interface with concerns with this project. Jack forwarded the email to the legal team to review. Jack will be able to address when he has clarification from legal.
- Lusheng: I would like to request a time slot during the 04/01 ToC weekly meeting to present the current plan for integration and testing Bronze release.
It will take about 5 minutes.
- Email from OAI
- Release Votes and Approval
- Marketing of the current release (WG, LF, PR)
- ONES = LF Networking Conference tentatively August/ September (Los Angeles). Open Networking & Edge Summit Event
- Virtual O-RAN demo was about to be activated. The site has been constructed and is being reviewed by EC. Will notify Farheen when the site is public. There are around 20 demos.
- Status of Open Action Items (Old Business)Jack - How does the OSC evolve from where we're at. Every piece is under construction. O-DU Emulation will help with that.
- Action / ENGWEI KOO - will add a deck to RSAC wiki.
- Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
- Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America
- Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests.
- Action/ user-59b16 upload the UE emulator short/long term slide deck to the RSAC page.
- Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
- Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times. There are 3 trains for the specifications.
Action/ user-2057e update Vote Release Name page with the D release name options.you can now vote on name for release D here: https://wiki.o-ran-sc.org/display/REL/Vote+Release+Name
- Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.
- Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney opened regarding the Calendar synchronization.
- Should we set a single to a common time zone?
- projects use UTC.
- Find the best solution to the problem.
- projects use UTC.
- Should we set a single to a common time zone?
- Action/ PTLs update your project summaries with your sprint 2 status updates. Be prepared to review your sprint 2 deliverables with the TOC.
- Action/ Jack will review Thoralf's How to request committer changes
- Action/ user-d3360 add the wiki link for SONAR to the Integration and Test wiki where people can easily find.
- Action/ user-59b16 set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.
- Action/ William DIEGO we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups
- Action/ user-d3360 add the link in the Integration and Test wiki to the SONAR instructions that you discussed on TOC meeting.
- Action/ PTLs provide user-d3360 with your sprint 2 demos.
- Standing Agenda Items (Brief Status of Ongoing Activities)
- Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
- Project Bronze Release
- Rittwik - In the virtual F2F most of the projects met with their working group reviews.
- Jinri - Sees a gap in Cherry. Overlap of WG.
- Jack - We have our ETE use cases that drive what we focus on in a release. Right now we have two. Traffic and self-test. Think of it as something that is driving RAM functionality and OAM functionality. Consider those and other tracks that are meaningful at pushing our community agenda. The RSAC committee can provide the specifications that are changing in the window. People that are interested please engage and help drive what are the important functionality. C and D are important releases in delivering and driving value. It is important that everyone get involved and the use cases in the C and D releases drive value to the O-RAN community participants and service providers otherwise we have to question whether we are going down the right path. Please get involved and help us get there. Let us see what we can do with the RSAC committee and see if our specs are frozen to make recommendations.
- Project Bronze Release
- Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list. Are there any major items that anyone would like to raise to the TOC this week?
- Matti Hiltunen RIC Applications (RICAPP)
- We are working on 6 xapps. 4 are traffic steering, 1 demo, 1 measurement campaign xapp.
- Is there a simulator requirement?
- Even if we decide to go with Viavi I don't think they committed to the E2 interface.
- The strategy was to get offline data. If that is available we can replay the E2 simulator.
- Are there committed resources?
- Alex - This is an open issue no one has volunteered.
- How can we help? Who can step up and work with Alex to get this critical part done? Is Viavi incremental to this need? Is it available in this time frame?
- Not E2, we want the metric that the EU and DU can provide.
- RAN simulation data is critical. We can work the E2 delivery in parallel.
- Is the simulator critically needed or not?
- If we are using the RIC platform and we use the KPI. We say we are using e2 then we need the simulator. If we by pass e2 and kpi mon then we can populate the SDL layer.
- Jack - yes it's needed. Is there anyone on the call who can step up and help in this space?
- Are there committed resources?
- The strategy was to get offline data. If that is available we can replay the E2 simulator.
- Even if we decide to go with Viavi I don't think they committed to the E2 interface.
- Is there a simulator requirement?
- We are working on 6 xapps. 4 are traffic steering, 1 demo, 1 measurement campaign xapp.
- Thoralf Czichy RIC Platform (RIC)
- note I updated the committer change process as per discussion last week: How to request committer changes.
- user-a934b O-RAN Centralized Unit (OCU)
- Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
- Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
- Martin Skorupski Operations and Maintenance (OAM)
- Alex Stancu Simulations (SIM)
- Xiaohua Zhang Infrastructure (INF)
- weichen ni Documentation (DOC)
- John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
- (TBD) O-RAN Radio Unit (ORU)
- Matti Hiltunen RIC Applications (RICAPP)
- user-59b16 Requirements Software Architecture Committee
- David Kinsey, Rittwiki, RSAC team discussed one Dynamic (performance mgt.) data collection set agenda pushed to ONAP. It is the responsibility in SMO. There is no SMO project. We are submitting.
- Action user-59b16 add Martin Skorupski to conversations around dynamic data collection.
- Is there a cutoff point this week for your requirements because the ONAP G release gate is closing.
- Rittwik - Yes, we are working on the requirements.
- Action/ user-59b16 send @John Paul Lane from Ericsson the RSAC requirements.
- WLF files? Zhimin Yuan we are in the process.
- Will that happen once we do the integration
- We are preparing for the Bronze relase.
- David Kinsey, Rittwiki, RSAC team discussed one Dynamic (performance mgt.) data collection set agenda pushed to ONAP. It is the responsibility in SMO. There is no SMO project. We are submitting.
- user-d3360 Integration and Test
- Plan for Integration and Test
- We have one development sprint left. First we will do integration in two separate groups.
- ODU Low and ODU high and
- OTF, OAM, NONRT RIC, Near RT RIC APP, SIM (Cloud), INF, O-DU LOW, O-DU High, SIM (Bare metal deployment)
- Integrated testing is lead by each PTL. Every project is delivering multi-containers. They are expected to do their own integration testing.
- Pairwise testing requires a need to interact. Next level is our use case testing. We will have a working session call and try to run the integrated testing together.
- How we will execute (be mindful of automated cleaning process)
- We have a Nexus Staging Docker Registry (images on this registry only live for 30 days) after that an automated cleaner will remove. There are ways to regenerate but keep the 30 day limit in mind.
- merge jobs are automatically run weekly, which keeps images fresh in the staging registry :)
- There is a container tag.
- Nexus Release Docker Registry. Images on release repo live "forever". Images on release registry CANNOT be overwritten.
- Lusheng proposing to formally adopt semantic versioning for tagging released O-RAN docker containers. After passing the component communicate through wiki, lists, and jira.
- Plan for Integration and Test
- Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
- 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.)