2020 07 01

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair		Weichen Ni	x
Deutsche Telekom	David Streibl		Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda		Anil Umesh
Nokia	Juha Oravainen	x	Thoralf Czichy
Orange	William Diego	x	Vincent Danno
Radisys	Ganesh Shenbagaraman		Sachin Srivastava	x
Verizon	Viswa Kumar		Kristen Young

*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
1. The minutes of the prior meetings were reviewed, and no corrections.
  1. Vote to approve minutes for 24 Jun 2020
  2. On motion made by Juha Oravainen
  3. Seconded by John Paul
  4. VOTE: Vote taken, item passed
Review of Today's Agenda
Release Votes and Approval
Copyright updates
Marketing of the current release (WG, LF, PR)
1. Bronze Release PR
2. Virtual Exhibition.
3. OSC Logo status.
Status of Open Action Items (Old Business)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Timeline
  2. Review Bronze Release Highlights
2. Former user (Deleted) Requirements Software Architecture Committee
3. Former user (Deleted) Integration and Test
4. 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?
  1. John Keeney (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. Former user (Deleted) O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. Weichen Ni Documentation (DOC)
  11. (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.)

2020 06 24

Recording: 2020_06_24_toc .mp4

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
Deutsche Telekom	David Streibl	x	Ondřej Hudousek
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Orange	William Diego	x	Vincent Danno
Verizon	Viswa Kumar		Kristen Young
Nokia	Juha Oravainen	x	Thoralf Czichy
Radisys	Ganesh Shenbagaraman	x	Sachin Srivastava
Ericsson	John-Paul Lane	x	John Keeney

*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
1. The minutes of the prior meetings were reviewed, and no corrections.
  1. Vote to approve minutes for 17 Jun 2020
  2. On motion made by huangjinri@chinamobile.com
  3. Seconded by Former user (Deleted)
  4. VOTE: Vote taken, item passed
Review of Today's Agenda
Release Votes and Approval
1. Samsung released the KPIMON xApp under Apache 2.0 license in the Amber release. However, the team has been advised by Samsung legal team that for the KPIMON enhancement in Bronze release should use O-RAN FRAND S/W license. Since only one license is allowed within a repo and the repo name depends on the license, we request a new repo: scp/ric-app/kpimon. The committers are the same as the existing KPIMON repo.
  KPIMON xAPP:
  - Proposed repository name: scp/ric-app/kpimon.
  - License: O-RAN software license
  - A brief description: This repo will host the source code for the KPIMON xApp. KPIMON uses E2SM (extended KPM service model) to collect information from the RAN and populate it in two name-spaces (one for cell metrics and other for UE metrics) in the RIC SDL layer.
  - A list of committers:
  1. Jeongyeob Oak, jy.oak@samsung.com, LFID: jyoak
    2. Jun Song, junhyuk.song@samsung.com, LFID: junny
    3. Jinwei.fan, jinwei.fan@samsung.com, LFID: jinwei.fan
  2. Jack This is a little different because of the dual license. Is there someone from Samsung project?
  3. Matti: I submitted this request as a RICApp PTL.
  4. Jack: Will the old repo be reitired? Will contributions be split because of dual licenses? Do you know how we are going to treat the new license?
  5. Matti: I was wondering that my self. There are contributions in Amber.
  6. Jack: Once content is released under Apache the content stays. Until we get clarification from Samsung, the way I would categorize is we are leaving the existing repo there and archiving it. Active contributions will go to the new repo and stays in its form.
  7. Peter Moonki Hong: Can I have clarification?
  8. Jack: There has been a request for a new repo and the question I had was what will happen to the old repo. Typically we would archive and close the old repo and have new repo contributions.
  9. Peter Moonki HOng: When it comes to KPI monitoring xApp we want to leave the repo as it is and archiving the repository. We will stop contributing to the old repo and start contributing the new repo for KPI monitoring of xApps.
    1. On motion made by Peter Moonki Hong from Samsung to approve creating the new KPI monitor repo and archiving the existing one
    2. David: Was the archived repo Apache only contributed by other than Apache?
    3. Peter: Motivation is to change their direcition to the FRAND license.
    4. DAvid: All the code is 100% contribution from Samsung.
    5. Matti: It's copyright AT&T and Samsung.
    6. David (DT): This is a lawyer question. If it all code by one company then they can release under new license but if there is code from another company then needs clarification from lawyers.
    7. Jack: This is a new occurrence. The AT&T code would still be under the Apache license and anyone can continue to use it going forward. It is released under Apache. To create the new repo it becomes a mixed repo that has pulled code from the Apache license and made into O-RAN license. I'll have to get clarification on what that means. Action/ Jack Murray get clarification regarding transfer of AT&T Apache code into the new dual license repo. General rule in the past is the most restrictive license dictates the combined code follows the most restrictive license.
    8. Lusheng: Will AT&T continue contributing to the SCP repo?
    9. Matti: No we had the admission control xApp but the person who wrote the code has left AT&T. I don't see any reason for the Amber release repo to carry on.
    10. Jack: It will be archived and the code is available for people to use.
    11. Lusheng: LF does support making a repo read only (archive) to use for the KPIMON.
    12. John Keeney: I presume it's possible for people who have branched the code can continue using?
    13. Jack: That's why it is archived. It follows the Apache usage rules. The new repo will use the new license with the new contributions with what they pull forward from Apache under O-RAN restrictions.
      1. On motion made by Peter Moonki Hong from Samsung to approve creating the new KPI monitor repo and archiving the existing one.
      2. Seconded by huangjinri@chinamobile.com
      3. VOTE: Vote taken, item passed
2. Summary Bronze Release
  1. Lusheng: We have completed the remaining tasks for the release. The detailed status is reported on the Bronze Release (Jun 2020)
    1. New Getting Started guide
  2. Jinri: Expresses his sincere gratitude for the hard work.
Copyright updates
1. Jack: Did we get an official approval of the copyright yet?
2. Jinri: I believe the voting results have come out. The EC has not announced.
3. Jack: We will get clarification on the EC call today and let everyone on this team know about the copyright permission from the O-RAN Alliance material.
Marketing of the current release (WG, LF, PR)
1. Bronze Release PR
  1. Jinri: Preparation for the virtual exhibition is done. I have the website link to the virtual exhibition. There are 13 new demos uploaded to the O-RAN virtual exhibition website. Among the 13 there is one from our open source community provided by Ericsson and their partners.
  2. Jack: Do you have to be an O-RAN member for the virtual space?
  3. Jinri: No it is a part of the O-RAN website.
  4. Jack: The Bronze PR activity is ongoing.
2. Virtual Exhibition https://www.virtualexhibition.o-ran.org/
3. OSC Logo status.
Status of Open Action Items (Old Business)
1. ~~Action~~/ William DIEGO update on the coordination with the O-RAN test group
  1. Jack: There is an open item from for the EC to work with the test group on a discussion around the emulator/simulator needs. We need to coordinate that. I got an email but am not sure where we are in the process of meeting. We need to meet to work out a longer approach.
2. ~~Action~~/ huangjinri@chinamobile.com notify the EC that the Bronze release has been voted on and approved.
3. ~~Action~~/ Former user (Deleted) send Jinri your status slides.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Timeline
    1. Maintenance release is avialable.
    2. Lusheng: We have a request from LF legal to have a formal process to address the use of external source code licenses? Should we use specific attributions or use a blanket statement. Action / Former user (Deleted) add the topic of license attributions to the agenda. We want to start the pairwise testing.
    3. Jack: Use the opportunity to do pairwise testing.
  2. Review Bronze Release Highlights
2. Former user (Deleted) Requirements Software Architecture Committee
  1. Our hope is to get the lab prepped by 6-30. We want to get the KPIMON inserted. We've asked Viavi to monitor a trace file that can be delivered by the end of the month we can make the use case more sophisticated. That will lead to the Cherry release to run with a real time simulator. We are counting on Viavi.
  2. The ML enabled traffic steering xApp I want to get a simulator of RAN topology.
  3. rApps and xApps will detail the onflows. How do you deploy the rApp and put it in run time. We also have to think about what kind of training and the training pipeline.
  4. How is O-CU going to talk to O-DU. Introduction of SMO in regards to LCM and pre-release R-1 interface for Cherry will drive R-1 interface for Dawn.
  5. R-1 interface is for introducing R-Apps. It is still being discussed in O-RAN Alliance. Some of it is pre-release and not set in stone. We can drive requirements down and start the ball roling. The DU Low and HIgh P7 is going to be integrated. R-U, D-U, C-U is a challenge. We've come up with a tentative plan of what the combined configuration. We will attempt to attach one UE and have a functional RAN element working. We have to get all the parameters and time. With HARK disabled can we attach a UE? It is important to get a functional end to end stack working.
  6. Lusheng: Do you mean simulated or physical UE?
  7. Rittwik: O-R is a simulated but with the real RAN we want a physical UE.
  8. Is there anything resembling and R-U stub for DU-Low?
  9. Rittwik: Yes, there is an R-U stub that is there already. That is basic functionality.
  10. Tracy: I think you are aware that AT&T will use SMO in stages? Is it ONAP based SMO?
    1. Rittwik: It will be ONAP based.
    2. I wanted to confirm the basic.
    3. Jack: The SMO is a big box that we've thrown some pieces in. It means different things to different people. The O-RAN Alliance WG1 leaves it to implementation. The challenge for us is to decide do we create a formal SMO project or not? There could be more than one if there's enough support in the community or do we avoid that? The issue we have to figure out is to make a working thing we need to pull together all the pieces. If we wrap it with a SMO label. How do we bring it forward enough so that companies understand how to use the pieces to wrap it together and see how somebody comes out with commercial implementation. The work is useful if it ends up with multiple providers across the globe.
    4. Tracy: The SMO are components or subset of building blocks. It has a few components some are being added and dependent on contributor support.
    5. Jack: The SMO needs to be provided by the software community to do the work.
    6. Tracy: AT&T is not the only operator who wants to start implementing the Phase 1 SMO and have some reassurance that phase 2 SMO can be built on phase 1 SMO.
    7. Jack: Industry trends company's lose interest. The SMO has to support a range of functionality but also make it easy for this community to build, test, demonstrate and move the community forward. We will cue this up for the next discussion.
    8. Jack: How are we going to approach pulling the SMO pieces together. Continue to get the O-DU moving forward. Looking at how the O-DU and O-CU work together. What about the O-RU? Those are more targeted discussions. As we mature a lot of discussions become complex.
    9. Jinri: TSC requested we work Acumos team for near Real Time RIC development.
    10. Jack: I will get someone from the project give a presentation here.
3. Former user (Deleted) Integration and Test
4. 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?
  1. John Keeney (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. Former user (Deleted) O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. Weichen Ni Documentation (DOC)
  11. (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.)
1. Votes
  1. On motion made by Peter Moonki Hong from Samsung to approve creating the new KPI monitor repo and archiving the existing one.
    1. Seconded by huangjinri@chinamobile.com
    2. VOTE: Vote taken, item passed
  2. Vote to approve minutes for 17 Jun 2020
    1. On motion made by huangjinri@chinamobile.com
    2. Seconded by Former user (Deleted)
    3. VOTE: Vote taken, item passed
2. Actions

2020 06 17

Recording: 2020_06_17_O-RAN_SC_TOC.mp4

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
Deutsche Telekom	David Streibl	x	Ondřej Hudousek
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Orange	William Diego	x	Vincent Danno
Verizon	Viswa Kumar		Kristen Young
Nokia	Juha Oravainen	x	Thoralf Czichy
Radisys	Ganesh Shenbagaraman		Sachin Srivastava	x
Ericsson	John-Paul Lane	x	John Keeney

*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
1. The minutes of the prior meetings were reviewed, and no corrections.
  1. Vote to approve minutes for 10 Jun 2020
  2. On motion made by John-Paul
  3. Seconded by Juha Oravainen
  4. VOTE: Vote taken, item passed
Review of Today's Agenda
1. Jack: We will spend time today to vote and approve the Bronze release for 21 Jun 2020
2. Rittwik: What is the suggestion for the Viavi simulator on the lab.
Release Votes and Approval
1. Last week we discussed delaying Bronze for one week. We had the press release. We voted and approved the delay by one week.
2. Lusheng; With the extension we have completed all the flows for the use cases. We have started preparing for the release. A wiki page has been created for tracking the remaining tasks.
  1. Repo must address all finding with the LF legal scan. There were 3 findings. 2 offending references have been removed. 1 for O-DU project has a resolution but it will take some time. The resolution will be on Thursday or Friday. After scan seed code 2 GNR scans have to be addressed. Lusheng will address after O-DU scan has passed.
  2. Binary artifacts will be perpetual.
  3. All the repos must update their release
  4. Bronze branch will be released for all the code.
  5. We are between 80 and 90% completion level for all the remaining tasks.
    1. See Releasing Bronze Tasks to see how we keep track of where everything is.
    2. John Keeney: Which comes first the code or the release?
    3. Lusheng: We have completed one round of passing Bronze release testing. Previously for the non real time RIC there it was yellow. The last round of testing passed. We will do another round of testing after the tasks are complete.
    4. Remaining tasks for Integration and testing teams.
    5. We are also creating a Getting Started wiki page to stand up their own near real time RIC and non real time RIC. We will also provide a video of the flows.
    6. We will have a Bronze Release Page
    7. Deferred to Bronze Maintenance Release
      1. US O-DU Low and O-DU High Use Case
      2. Full Traffic Steering Use Case
      3. RICApp xApp raising alarms Use Case
      4. O-DU-LOW CICD
      5. O-CU CICD
    8. Rittwik: This is pending the emulator decision because the input to the KPIMon is dependent on the emulator or else it is not a full traffic steering use case.
    9. Jinri: Where can I get these slides?
      1. Action/ Former user (Deleted) send Jinri your status slides.
      2. Jack: I wanted to elaborate on the getting started. I asked a team of people to take a look at the process of starting the procedure. We found from other projects that it is easier to have a getting started page for new people who are not familiar with the project.
      3. How do we see updates before release and after release?
      4. The deadline for the release is Sunday 21 Jun 2020
      5. Lusheng: The tarball is the source code for getting the branch at that moment. The images are self service releasing. What does it really mean when people release. We will provide recipe files in the Getting Started. After a repo has been released and more changes are needed we will maintain the head of the Bronze branch as much as we could.
    10. Given the current status Former user (Deleted)made a motion for a go or no go for the Bronze release.
      1. On motion made by Former user (Deleted) to officially release the Bronze code on 21 Jun 2020
      2. seconded by huangjinri@chinamobile.com
      3. VOTE: Vote taken, item passed
Copyright updates
1. Jack: O-RAN copyrite usage for O-RAN specifications.
  1. Jinri: I was late to the last EC. I will follow up with Zybnek.
  2. Jack: We have not gotten official closure for the vote. Next week we will get the exact clarification. On a related topic ETSE approved the O-RAN Alliance use of copyright. In process and making progress for the O-RAN SC to have copyrights.
Marketing of the current release (WG, LF, PR)
1. Bronze Release PR
  1. We are working through establishing some guidelines for that PR release. Some of the feedback is we're trying to keep the statements refined. I was asked to go back and ask the companies to trim to make a crisp statement with a blog are for extended information. We are working through that with the EC and PR teams.
2. Virtual Exhibition.
  1. Jinri: I don't have the progress. I have not seen any email exchange between Zybnek, Paul and me. Zybnek is working on online. I will update the progress next time.
  2. Jack: It will come out along with the board meeting. The opportunity to the community is to show off progress we are making in the O-SC. It is a good place to show the O-SC software.
  3. John Paul: I heard 19 Jun 2020 is the last day for the deadline communication.
  4. Jinri: Gate 1 is to review. Gate 2 is PR which has already past.
  5. John Paul: The submission of the actual demo deadline is this Friday 19 Jun 2020 .
  6. Juha: I see the deadline is 19 Jun 2020
  7. Zhimin: Intel has not given feedback for the PR. Is it already tracked?
  8. Jinri: It is already tracked. I forwarded it to Zybnek.
3. OSC Logo status.
Status of Open Action Items (Old Business)
1. Action/ William DIEGO update on the coordination with the O-RAN test group
  1. https://oranalliance.atlassian.net/wiki/spaces/TTIFG/pages/480542932/1.0+Draft.
  2. William: I will continue to attend the ETE meetings.
2. ~~Action~~/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.
  1. We had some OSC meetings on this topic. One was a F2F of all the WGs. Well over 100 participants attended. We had a second one on a more detailed discussion on the emulator activities. We made a presentation and discussed the values.
3. ~~Action~~/ Vishnu send Rittwik the slides for the ITU / AiML Challenge
  1. Jack: We did not do too much
4. ~~Action~~/ Rittwik: Post ITU / AiML Challenge slides on the wiki and pull together a team. Include Thoralf.
  1. Rittwik: I would like to know where we are with Viavi simulator?
  2. Jack: It is at the EC level. They have been very busy the last few weeks. It is on the agenda but we have not come to a resolution or a vote at this time.
  3. Jinri: Several EC members had dropped the meeting and not enough time to discuss. Tomorrows EC call this has been put at the top priority. The EC members have reviewed the documentation late so they postponed it to tomorrows call.
  4. Jack: More complicated because of the Virtual F2F.
5. ~~Action~~/ Rittwik: I will set up a meeting for ITU AI/ML and pull together a team.
6. ~~Action~~/ Trishan: clear all the legal items for the code and figure out what is needed for the O-CU repo creation so the team can continue.
7. ~~Action~~/ Former user (Deleted) provide Trishan with the O-CU repo trouble ticket.
  1. The repo was created and since then O-CU has uploaded the code and merged.
  2. Jack: The key is to get that repo added to the analytics page.
  3. Trishan: It should be available after 6 hours of adding the
8. ~~Action~~/ huangjinri@chinamobile.com generate an email to inform Zybnek and EC regarding that we will be delaying the release
  1. Jack: Action/ huangjinri@chinamobile.com notify the EC that the Bronze release has been voted on and approved.
  2. Jack: We'll start planning for Cherry and Bronze Maintenance release. We want to look at the end to end use cases that will align the community and O-RAN Alliance forward. I need to ask for people to look at the requirements and test teams. Those teams have done two releases and are small. Typically on projects we rotate people. We will need new people to step up for the Cherry release or else we won't be able to do all the testing. It is imortant for all the oprators, vendors, and participants in the community and look to contribute and find a place where everybody an pitch in. Requirements, Inetgration and Test and requirements will be pulling this all together. These up front and back end teams need participation with the community ore las we will have do more testing. I asked the other TOC members to take time to see if there is any where they can contribute.
  3. Jack: We are at the end of our meeting and thanked the team. DU High and Low made significant progress to make the end to end flow. We have new code coming in from two areas like TR69 and O-CU code that will bring functionality. We are looking to Cherry to add more O1 and A1 support so it looks lie a system and not just stand alone parts. I look forward to new projects such as the SMO work. There is still a lot to do and participate. I wanted to thank everybody for all the progress and look forward to watch Cherry
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Timeline
  2. Review Bronze Release Highlights
2. Former user (Deleted) Requirements Software Architecture Committee
3. Former user (Deleted) Integration and Test
4. 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?
  1. John Keeney (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. Former user (Deleted) O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. Weichen Ni Documentation (DOC)
  11. (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.)
1. Votes:
  1. The minutes of the prior meetings were reviewed, and no corrections.
    1. Vote to approve minutes for 10 Jun 2020
    2. On motion made by John-Paul
    3. Seconded by Juha Oravainen
    4. VOTE: Vote taken, item passed
  2. Given the current status Former user (Deleted)made a motion for a go or no go for the Bronze release.
    1. On motion made by Former user (Deleted) to officially release the Bronze code on 21 Jun 2020
    2. seconded by huangjinri@chinamobile.com
    3. VOTE: Vote taken, item passed
2. Actions:
  1. Action/ William DIEGO update on the coordination with the O-RAN test group
  2. Action/ huangjinri@chinamobile.com notify the EC that the Bronze release has been voted on and approved.
  3. Action/ Former user (Deleted) send Jinri your status slides.

2020 06 10

Recording: 2020_06_10_toc.mp4

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
Deutsche Telekom	David Streibl	x	Ondřej Hudousek
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Orange	William Diego	x	Vincent Danno
Verizon	Viswa Kumar		Kristen Young
Nokia	Juha Oravainen	x	Thoralf Czichy
Radisys	Ganesh Shenbagaraman	x	Sachin Srivastava
Ericsson	John-Paul Lane	x	John Keeney

*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
1. The minutes of the prior meetings were reviewed, and no corrections.
  1. Vote to approve minutes for 03 Jun 2020
  2. On motion made by huangjinri@chinamobile.com
  3. Seconded by Juha Oravainen
  4. VOTE: Vote taken, item passed
Review of Today's Agenda
1. Any further updates for the ITU AI/ML Challenge.
  1. Rittwik: Sent it to John Paul. Action/ Rittwik: I will set up a meeting and pull together a team.
  2. Jack: It is difficult to move quickly. It takes time to ramp up.
  3. Rittwik: Where should I put the challenge?
  4. Jack: Events wiki and post to the reflector.
2. Lusheng wants to post the status of the Integration and Test
Release Votes and Approval
1. Vote on the Bronze Release and Integration and Test Status
2. Jack: The press releases are handled by the O-RAN Alliance. Zbynek is the primary contact and he runs it through the O-RAN Alliance. Jinri is our interface to Zbynek. Zybnek has pulled together a draft. It will be combined with the Virtual Demo and the board meeting that is coming up at the end of the month. The direction is to release the press release at the end of the month like June 30th. That gives us another week for the highlights. That is the feedback from O-RAN Alliance and Zybnek is our contact.
3. Jinri: Does not have the latest.
4. Trishan: Do we need a quote for this release?
5. Jack: Yes, we should.
6. Trishan: Jinri please share.
7. Jinri: I'm not sure we can share but we can pull out a portion and share with this community.
8. Jack: It is a combined press release making it a little complicated. I'm trying to work through how this work than through the traditional open source.
9. Trishan: If it is a press release we keep it close.
10. Jack: If you have input contact Zybnek and he will coordinate with Jinri for the PR Release. That gives us a little window to discuss. Let us go on to the report from the system integration group.
11. Lusheng: Sharing screen.
12. Jinri: OCU PTL informed Jinri they have code ready for quite some time. They are waiting for the repo to be opened by the LF. The request was submitted one month ago. It has been ready for quite some time.
13. Lusheng: I was cc:d on the help desk ticket. LF has added all the information needed for the automation job to create the repo. 7 - 8 hours ago there was a message from LF that the ticket is on hold. Action/ Former user (Deleted) will check the status of the O-CU demo.
14. Lusheng: Scope: We have a number of use case flows. Mainly the flows are RIC , O-1, A-1 healthcheck. O-1 was descoped. Traffic use case is a partial flow that verifies the traffic steering decision. First is without KPIMon. Second phase in the Bronze maint. release will deliver the full flow. O-DU high and low will communicate over FAPI and exchange one MAC message. This is also timed for B maint. release. For integration this is what we deployed for testing. The color coding represents different code implemented for different projects. There are some pieces that are grayed out and will be deoployed in Bronze maint release. We deployed two k8 clusters in the lab. We deployed SMO real time one towards edge. Status: We have completed two of the four flows A1 RIC healthcheck. Long with more than 60 calls. The long chain will interact with non Real Time down to A1 mediator and distributor to the Hello World xApp. To support xApp near Real Time RIC complex flow passed.
15. Proposals for 4 flows deliverables.
  1. Lusheng would like to recommend option 1
  2. Lusheng requesting a vote from the TOC.
  3. Jack: Floor is open for questions.
    1. Jack: if we go with where we are right now. What percentage of work that's been tested. All flows have not been tested. There are only certain things that we can test. It is driven by end to end flows. When you say for the overall testing plan what percentage would you put on the testing overall. What percentage of testing of flows will one week give you?
    2. Lusheng: We are between 80 - 90% Blocker is the alarm flow that is blocking the two healthcheck. We are not able to complete the test however the dev teams were successful. That is why I think it is a configuration mismatch and not a feature missing. There is a feature missing but will be provided. The one week extension will help us to complete the alarm process and we will have the 4 flows. The alarm processing flow involves O1 mediator and Prometheus and Prometheus manager. Prometheus are external components of the upstream so configuration is tricky.
    3. Jinri: if we can address can we include O-CU with the one week extension?
    4. Lusheng: The code will not be a part of testing.
    5. Jack: Has the license scan been completed and accepted?
    6. Lusheng: Yes, LF attorney conducted a scan and came back with questions. I distributed to the PTLs. I have to pull that report and return to legal. The issues have been resolved but we don't have LF legal final approval to release the code.
    7. Lusheng: We are putting together a Getting Started guide. It is a work in progress. We will have the test documentation and a video tutorial. The video will be on the tutorial. After the Bronze release will be off. the landing page. The quick start will be for end users of how to configure and run. What are the commands to run. We have the first part all the way up to deploying near completion.
    8. Jinri: Have you considered a two week extension for safety?
    9. Lusheng: No I did not.
    10. Jack: We try to stick as close to our schedule as possible because people will start moving into. the maintenance release. We try to focus to validate through testing. That is what is most useful to the software community vs. diving into code that they are not familiar with and they don't have a lot of support. It's progress for the community but not for downstream users. You still have to clean things up.
      1. finishing completing testing
      2. getting through scans
      3. make the getting started guide for people to understand what the Bronze release is all about.
      4. Let the team take on a host of issues for the maintenance release rather than working the team week to week.
      5. Former user (Deleted) agrees with Jack to complete in a week and clean up in the maintenance release.
      6. Ganesh and Juha agree.
      7. Jinri: The reason i raised the comment because I think O-CU is critical for the release. If we have a two week window extension we can get the O-CU part done. The code is ready and waiting to be uploaded. If we can do it in two weeks we can include the O-CU.
      8. Jack: We should get it scanned and address the legal issues in time I doubt two weeks... It will either pass or need more time to resolve that will push into maintenance release.
      9. Jack: Martin Skorupski provide the status for the TR-69 adaptor is included.
      10. Lusheng: The previous scan did not include.
      11. Jack: Those are two items we should put on the list for the maintenance release.
16. Vote: On motion by Former user (Deleted) to move the Bronze release from 14 Jun 2020 to 21 Jun 2020 add one week extension to the Bronze release. Delay the release by one week.
  1. Seconded by Former user (Deleted)
  2. VOTE: Vote taken, item passed
17. Jack: Action/ Trishan: clear all the legal items for the code and figure out what is needed for the O-CU repo creation so the team can continue.
18. Action Former user (Deleted) provide Trishan with the O-CU repo trouble ticket.
19. Action/ huangjinri@chinamobile.com generate an email to inform Zybnek and EC regarding that we will be delaying the release
20. Zhimin: We decided to release next week. I have questions for development on the branch. What is the way for us to implement.
21. Lusheng: I will send out a separate email for the release and action items.
22. Jack: For pieces that are complete as far as Bronze is concerned they can branch their code and move on to maintenance.
23. Lusheng: Yes, the release process, 1 you need to make sure as PTL that the artifacts exist in release repo registries and not in staging. 2. xApp descriptors contain a link to the docker image. After that you can make the branch. We will use the bronze branch. All lower case for the branch name. bronze will be the bronze name. The repo owners can make the branch. Please make sure the release notes in the repo docs section is up to date and contains the bug fixes in the release notes. This is the high level process.
24. Jack: Everyone should update their bronze release table for features and capabilities so that it is on the web site as well.
Copyright updates
Marketing of the current release (WG, LF, PR)
1. Bronze Release PR
2. Virtual Exhibition.
3. OSC Logo status.
Status of Open Action Items (Old Business)
1. Action/ William DIEGO update on the coordination with the O-RAN test group
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Timeline
  2. Review Bronze Release Highlights
2. Former user (Deleted) Requirements Software Architecture Committee
3. Former user (Deleted) Integration and Test
4. 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?
  1. John Keeney (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. Former user (Deleted) O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. Weichen Ni Documentation (DOC)
  11. (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.)
1. Votes
  1. The minutes of the prior meetings were reviewed, and no corrections.
    1. Vote to approve minutes for 03 Jun 2020
    2. On motion made by huangjinri@chinamobile.com
    3. Seconded by Juha Oravainen
    4. VOTE: Vote taken, item passed
  2. On motion by Former user (Deleted) to move the Bronze release from 14 Jun 2020 to 21 Jun 2020 add one week extension to the Bronze release. Delay the release by one week.
    1. Seconded by Former user (Deleted)
    2. VOTE: Vote taken, item passed
2. Actions
  1. Action/ William DIEGO update on the coordination with the O-RAN test group
  2. ~~Action~~/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.
  3. Action/ Vishnu send Rittwik the slides for the ITU / AiML Challenge
  4. Action/ Rittwik: Post ITU / AiML Challenge slides on the wiki and pull together a team. Include Thoralf.
  5. Action/ Rittwik: I will set up a meeting for ITU AI/ML and pull together a team.
  6. Action/ Trishan: clear all the legal items for the code and figure out what is needed for the O-CU repo creation so the team can continue.
  7. Action/ Former user (Deleted) provide Trishan with the O-CU repo trouble ticket.
  8. Action/ huangjinri@chinamobile.com generate an email to inform Zybnek and EC regarding that we will be delaying the release

2020 06 03

Recording: 2020_06_03-toc.mp4

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair		Weichen Ni	x
Deutsche Telekom	David Streibl		Ondřej Hudousek
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Orange	William Diego	x	Vincent Danno
Verizon	Viswa Kumar		Kristen Young
Nokia	Juha Oravainen	x	Thoralf Czichy
Radisys	Ganesh Shenbagaraman	x	Sachin Srivastava
Ericsson	John-Paul Lane	x	John Keeney

*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
1. The minutes of the prior meetings were reviewed, and no corrections.
  1. Vote to approve minutes for 27 May 2020
  2. On motion made by John-Paul Lane
  3. Seconded by Weichen Ni
  4. VOTE: Vote taken, item passed
Review of Today's Agenda
1. Juha - Last week discussed Virtual meeting.
  1. Jack: Jinri has been involved in setting it up. It was mostly Jinri.
    1. Action/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.
    2. ```
    https://oranalliance.atlassian.net/wiki/spaces/OAH/pages/644448276/Virtual+F2F+Meetings+June+8-19+2020
    https://wiki.o-ran-sc.org/pages/resumedraft.action?draftId=1179657&draftShareId=102136bc-a84f-4418-bf53-c4fbd986063a&
```
2. ITU / AiML Challenge
  1. Vishnu: This is an invitation to collaborate.
  2. ITU has launched a 5G challenge. We request O-RAN SC to consider collaboration or a problem statement for the challenge.
  3. We are trying To create platforms using open source.
  4. We provide feedback and collaborate with ITU specifications.
  5. Who? Open to everybody 5GU. And also include you as a nominee.
  6. LFAI and NGNM.
  7. I discussed two plans with Rittwik two plans.
  8. Tool set
3. Jack: Dates to get back to you by?
  1. Vishnu: June second week around 10th or 15th. You can provide a date for your collaboration window. If you need to come in the next window will be midSeptember. I can stretch it to 3rd week of June.
  2. Jack: I would like to get a few people to get involved.
    1. Matti and Rittwik.
  3. Is it only for xApps?
    1. Vishnu: It is open contact Vishnu.
  4. Jack: is there anyone else who would like to get involved?
    1. John-Paul we would like to know more.
    2. Thoralf: slides?
    3. Action/ Vishnu send Rittwik the slides.
    4. Action/ Rittwik: Post it on the wiki and pull together a team. Include Thoralf.
Release Votes and Approval
1. Jack: Saw Zbynek's draft with information for the release. Several people asked for supporting statements. Please contact Jack or Zybnek for release highlights. The company's that have statements send Jack requests and he will pass along to Zbynek.
2. John Keeney: Will it be possible to see the press release before it goes out?
  1. Action/ Jack: Will share the document through the reflector. Jack and Jinri provided the input.
  2. John: When is the deadline for the highlights?
    1. Jack: We try to be ready by 6/14. The press release will come out any time after that. They will make the final decision on the exact. Have to them by the end of this week.
    2. We will focus next week on the final vote to approve the release.
Copyright updates
1. Jack: The updated statement is still in the process of being voted upon at the board level. I don't see the details. I am not in the email pool. I get some information back but it's in process. The board votes take a little more time to gather the input from everyone and they try to get everyones vote. I will get an update as soon as I return.
Marketing of the current release (WG, LF, PR)
1. Bronze Release PR
2. Virtual Exhibition.
  1. There is a June update to the virtual exhibition coming out. Jinri has been talking about the demos and submitting them to Paul Smith from AT&T. Any questions?
3. OSC Logo status.
Status of Open Action Items (Old Business)
1. Action/ William DIEGO update on the coordination with the O-RAN test group
  1. John-Paul. It will be decision based.
  2. Jack: Yes, O-RAN will look at it and give the thumbs up that we've looked at it and saying it's met their principles.
  3. John-Paul: There is nothing from stopping anyone from using testing simulators but they have to be approved by OTIG.
  4. Tracy: I think what you are saying is consistent with the OTIG guidelines. I am familiar with the one in North America to demonstrate ONAP elements.
2. ~~Action~~/ TOC members vote to approve Martin's email for a new repo request.
3. ~~Action~~/ Rittwik: Share the spreadsheet with Jinri and Yingying. Regarding the topic of O-CU 5G status.
  1. Rittwik: asked Yingying to share Cherry release to pass along.
    1. Jack: This is important that we promote and support in the Cherry release. I am looking for progress in the Cherry release.
    2. Rittwik: ODU OCU ORU are discussing their minimum support that they agree to inside Radisys, Viavi, Yingying are providing input to show they are in consensus.
    3. Jack: That starts to make them more useful.
4. ~~Action~~/ Trishan de Lanerolle provide the Insight slides to Farheen Cefalu
  1. Jack: We got the report last week from Trishan. People saw issues with Unknown attributes. Farheen got most of that addressed. We have improved the unknowns and got them addressed.
  2. In the attribution process one of the challenges we've observed is as an AT&T representative to make a decision, people were contributing from different att.com domain we were seeing code coming from different parts of the company. We were getting a lot of dither inside the AT&T. Even though I can see it and know that contributions are coming from Nokia. As a company think about unifying your subdomains into one company domain to make it easier to see the entire company.
  3. John Keeney: Cross cutting projects such as documentation and tests. Content is driven by other projects. Such as Non real time RIC can we tag some of those changes to certain topics.
    1. Jack: Yes, we are open to that discussion. We can review for example they only had information by each sub project which made it difficult to see progress by sub sections. We can carve out time to talk about it and work with Trishan and team to work with.
      1. John: To make sure everyone gets credited for work they are doing.
      2. Jack: Documentation has it's own set of reports. There is ability to look at that and it is separate.
5. ~~Action~~/ PTLs provide one or two bullet highlights worth including in the press release. It does not have to be long. One or two sentences one or two bullet points. 03 Jun 2020 Should include statements from any company's.
  1. Jack: I will send it out in the reflector.
  2. Matti: What is the process for collecting highlight emails?
    1. Copy Jack in an email.
  3. Rittwik: Put the highlight you think you have received put it on the front Bronze highlights. Put it on the Bronze Release page.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Timeline
    1. We are at the end of the timeline.
  2. Review Bronze Release Highlights
2. Former user (Deleted) Requirements Software Architecture Committee
3. Former user (Deleted) Integration and Test
  1. RSAC defined flows for Bronze. Traffic steering has been completed and successful.
    1. Traffic Steering use case is successful.
    2. For A1 flow under health check segment flows have been successfully tested.
      1. Hello World is not working yet so we are using traffic steering.
    3. ODU High are successfully able to establish heathcheck communication.
      1. O1 alarm flow over healthcheck we have model re-alignment are different. We will set up a meeting with the PTLs of both OAM and Near Real time RIC. We will see if we can close this gap and how long it will take. Thoralf has a conflict and Martin is not available today.
      2. Jack: Do we understand the gap why it happened. How do we address this moving forward? Is this improve communication? Change specs? Or get clarification on the topic?
        Lusheng: There is a short term to see how large the gap is and can we close in this release?
        For longer term pairwise testing on different projects has been minimal. In Cherry improve in the design and architectural phase if somebody can own the ETE flow. Not just a high level agreement at the definition phase. We are finding it at the end of the release.
        We should start pairwise and intercomponent earlier than the last integration and testing phase. We couldn't do much of testing. It would be better if the developer or owners of the inter communication or components throughout.
    4. In terms of sheduling we have until the end of next week. The go/no go will happen next Wednesday. Next week we will have the virtual face to face as well. The projects need to branch the code, documentation, and release notes. We will try our best to target this deadline but we may need some time to cover the final release items.
    5. Jack: TOC please provide input regarding slipping the timeline by one week. This will delay the press release. The TOC members should talk to the participants and getting these items addressed. This is crunch time and look forward and prepare for a slip in the schedule by one or two weeks.
    6. Rittwik: I think you've completed 90% of testing. The 10% can be pushed to maintenance meeting.
    7. Jack: We'll discuss the details in next weeks meeting.
4. 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?
  1. John Keeney (Ericsson EST) Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. Former user (Deleted) O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. Weichen Ni Documentation (DOC)
  11. (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.)
1. Votes:
  1. The minutes of the prior meetings were reviewed, and no corrections.
  2. Vote to approve minutes for 27 May 2020
  3. On motion made by John-Paul Lane
  4. Seconded by Weichen Ni
  5. VOTE: Vote taken, item passed
2. Actions:
  1. Action/ William DIEGO update on the coordination with the O-RAN test group
  2. Action/ Farheen point to the F2F meeting from the Events page to O-RAN Alliance's latest spreadsheet.
  3. Action/ Vishnu send Rittwik the slides for the ITU / AiML Challenge
  4. Action/ Rittwik: Post ITU / AiML Challenge slides on the wiki and pull together a team. Include Thoralf.
  5. Action / Jack send the highlights out on the reflector before the press release.

2020 05 27

Zoom Recording: 2020-05-27_toc_audio_only.m4a

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
Deutsche Telekom	David Streibl	x	Ondřej Hudousek
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Orange	William Diego	x	Vincent Danno
Verizon	Viswa Kumar		Kristen Young
Nokia	Juha Oravainen	x	Thoralf Czichy
Radisys	Ganesh Shenbagaraman	x	Sachin Srivastava
Ericsson	John-Paul Lane	x	John Keeney

*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
1. The minutes of the prior meetings were reviewed, and corrected by Farheen who replaced Jean-Paul name where Juha had seconded last 20 May 2020 meeting minutes approval vote.
  1. Vote to approve minutes for 20 May 2020
  2. On motion made by Juha Oravainen
  3. Seconded by Ganesh Shenbagaraman
  4. VOTE: Vote taken, item passed
Review of Today's Agenda
1. Preparation for Bronze Release
  1. Jack: I added this item for the preparation for the Bronze Release.
  2. Trishan: We have the Insights team on today.
  3. Chat: From Trishan de Lanerolle (LF) to Everyone: (08:30 AM)
     https://lfanalytics.io/projects/o-ran 
2. Insights Team
  1. Shubhra Kar (CTO Insight) sharing a deck.
  2. LF planning to launch Networking Project this year. Reviewing short term and long term roadmap. Have been working with PMs for the Networking Project.
  3. Birdseye view of what they are trying. LF foundations automation platform. Security scanning, single sign on service. Wrap zoom around security layer. Analytics will go deeper today. We have easy CLA tools.
  4. We have been writing automation around asset management, voting, and PM service. We announced crowd funding service and more. The goal it to build a centralized platform to provide services in the platform lifecycle.
  5. There is an IP automation part.
  6. Today we are going to talk about Insights. It is still early. It is our V1 version. What are we trying to solve. 1. members, 2. Projects, 3. contributors. We want to look at employees impact. We want to see activities going up or down. For the projects you want to grow the community you want to measure health. Also, optimization is built in. While youre collecting data is the data secure? Email addresses are they stored in GDPR and privacy policies. Look at contributors commits and backlog working in sprints. However, can the contributor think about security? Are there security metrics available. In the version1 we haven't integrated our license yet.
  7. This is home grown. LF needed to rely on third party tools. This has been built for LF community and all the projects under LF umbrella. Large team supports this from operations perspective. It is GDPR compliant. Features are the multi dimensional views. From a support perspective we are putting a support structure and offer weekly office hours from our engineers.
  8. We are gathering our metrics around commits and issue tracking. We aggregate on a daily basis. We have automated the instrumentation. So if a project adds another data source tomorrow we can add it without a lot of overhead. We are building custom dashboards on kibana. Two challenges are identiy management. No consistency in contributors ids. How do we unify an identity of a user and refer back to one person. For member companies you want that credit to be applied to the company. How do you affiliate the contributors to these companies? There is no source of truth. We have a solution of how we manage through an administrative console. As we build it out we are scaling into a self-serve platform. We have put access rules into place. These are the data sources. We have projects moving into gitlab. Issue tracking systems. Bugzilla in jira. If you are using jenkins in your builds we have instrumentation that is pulling that data. As well as Slack, Jira, Confluence, Github Issues,...
  9. John-Paul does there need to be a design time update from the team or our own reports?
  10. We do create templatized dashboards. If you want to visualize data in a custom view you can download anonymized data and voting dashboard, we have that instrumentation. We have sprints we work on the design and put it on staging get user acceptance and move it to production.
  11. Jonh-Paul so as a company we could run a query across a number of projects.
  12. Shubrah: You can we are coming up with an out of box dashboard that will be released in fall.
  13. Shubrah showing a demonstration. Watch the recording.
  14. When will it be available to use?
  15. V1 is available right now. If you look at the site. There is a roadmap and newer views we are building for code pipelines. There is a role out plan PMs in the Networking team. We are doing waves and sign off. Wave 1 was presented. Wave 2 we want to give to O-RAN. There are others.
  16. Jack: can we have these slides.
  17. Action/ Trishan de Lanerolle provide the Insight slides to Farheen Cefalu
  18. David McBride: We split the schedule into greenfield project that don't have a developer O-RAN tool. Last week we talked to CNTT this week FIDO, O-RAN...
  19. These are the projects that have developer tools.
  20. Shubhra: PMs are validating their data. This is UAT.
  21. Jack: Is there a best procedure for closing these unknowns? How we do that? Is there guidance?
  22. Shubhra: Trishan is one Admin who can work on affiliation. We have a filter list.
  23. Trishan: We can add a couple of members in the community add them and then merge it back in.
3. Bronze Release PR
4. Virtual Exhibition.
5. OSC Logo status.
Release Votes and Approval
1. Jack: Any items open for votes and approvals? What is going to happen here is we are going to have a Go No Go vote on the Bronze release. Today is not the right day yet. The B release is supposed to happen on June 14th. Next week we should have a go / no go vote on the software release and press release. We have work to finish if we plan to release on time. That would mean the press release will come out Monday June15 or Tuesday June16.
2. Jinri: For the press release the O-RAN Alliance is not quite sure if we will have a separate PR for Bronze release or mid year press release for O-RAN Alliance. I plan to bring this up in todays EC call.
3. Jack: That is fine where the mechanics are when we release the info but the preparation of the documentation and released will stick to the time line. We are finishing up end to end testing this week and we'll have to decide if we are ready for a release on the 14th. That will give us time to pull together documentation and additional work for the Bronze release. One of the things we have to finish up gathering for B. We have to have our testing complete and the package to pull together. We'll discuss here how EC wants to release the information but for us we want to make sure we have the information ready for the press release.
4. Jinri: Before hand preparation for information. In the press release we want to see the high lights. It is OK to ask the PTLs to provide 2 or 3 bullet points that they would like for us to highlight in the press release.
5. Action/ PTLs provide one or two bullet highlights worth including in the press release. It does not have to be long. One or two sentences one or two bullet points. 03 Jun 2020 Should include statements from any company's.
6. Jack: I will be out next week. Lusheng will be my proxy. Jinri could you run the meeting?
7. Jinri: Yes, I think so.
Copyright updates
Marketing of the current release (WG, LF, PR)
1. Virtual Exhibition.
  1. Jinri: There was an OSC related demo submitted to working group 1 O-RAN Alliance.
  2. Jiri: There is the virtual exhibition will last 2 weeks. The OSC have two time slots on Monday June 8th. Cherry release kick off discussion. Row #13 OSC line. The first item is the Cherry release kickoff 2 timeslots on Monday. Next topic Viavi on Tuesday. This is based on what I collected before. There is third one that is proposed by WG8 but they request us to join this discussion. The question to you and Rittwik just to confirm that we do need these two slots that we have required. We can attend.
    1. How long is the slot?
    2. One block is one hour. 2 hours for Cherry release. Starting time will be 8AM EST.
    3. Rittwik: Does this clash? You have WG1, 2, 3.
    4. Jinri: They will join this topic. WG1, WG2 is the entitiy who requested across this discussion followed by the topic.
    5. Action/ Farheen Cefalu add the spreadsheet to the Events page.
    6. Jinri: The latest one is the one I sent to you, Rittwik and Lusheng.
2. OSC Logo status.
Status of Open Action Items (Old Business)
1. Action/

2020 Q2 (Apr, May, Jun)

2020 07 01

2020 06 24

2020 06 17

2020 06 10

2020 06 03

2020 05 27