Technical Charter for O-RAN Software Community

Heads Up! Different International Timings for Daylight Savings (Fall back one hour)

VOTE for the B Release!

2019 11 13

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair	x
   China Mobile	Jinri Huang Co-Chair
   Deutsche Telekom	David Streibl	x
   NTT DOCOMO	Masafumi Masuda	x
   Orange	William Diego	x	Vincent Danno
   Verizon	Viswa Kumar

   *Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quorum and can vote on activities.

3. Review and Agree to Minutes of Previous Meetings

   1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   2. Vote to approve minutes for 06 Nov 2019 
   3. On motion made by user-2057e
   4. Seconded by MASAFUMI MASUDA
   5. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Marketing of the Amber release (WG, LF, PR)
   1. Jack saw the initial draft of the framework for the O-RAN SC marketing plan and needs to review.  Comments from participating companies is encouraged.  We are entering the window of time to get approvals to get a quote.  Those interested reach out to Jinri Huang and copy John Murray.
6. Status of Open Action Items (Old Business)
   1. Action/Jinri Huang  will create a framework  for the O-RAN SC marketing plan.
   2. Action / Farheen Cefalu send out a note today of when we have to have our votes in by 08 Nov 2019 .  Update the site
      1. B release name is Bronze
      2. C release name is Cherry
   3. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      1. Samsung will not participate.  Ongoing
   4. Action/ Jinri Huang  will add the F2F meeting minutes to the events page. 27 Nov 2019 
   5. Action/ John Murray to work with OAI interface.
      1. This was opened at the f2f and discussions going on with the EC.  We got the presentation from last weeks meeting.  Challenge is Jack needs a readout from legal team to understand what options and work needs to take place.  No official move in O-RAN Alliance and what we are going to do in Open source.  They have their own licensing.  
         1. Rittwik assigned but not sure.
            1. Architectural alignment and where we are aligned and where are we mis-aligned with our architecture.
            2. Christian Gallard  - If OAI current requirements meet the O-RAN Alliance architecture?
               1. Jack - recommendation from a technical review vs. the legal review.
   6. Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
   7. Action/user-59b16 send the B release epics to user-bc668
      1. Who is taking care of the dashboard epics?  Will it be OAM?
         1. Jack - Right now that makes the most sense to put them in the OAM project.  We want the team to decide what reports should be presented in the dashboard.  OAM teams need to access and utilize dashboards without having to read a manual.
            1. Tracy Van Brakle  wants an offline conversation about traceability.This is for OA-Bronze.  We need distinguish between OAM and dashboard.  
               1. We can add this topic to the architecture meetings or have a separate meeting.  Tracy Van Brakle will set it up.
   8. Action/ John Murray closing the remaining the TOC slots.
      1. We are working with LF to close on the reporting for contributions and activities but we had a set back last week on gathering information.  They were reporting that there would be an update early this week.  
   9. Action/ user-d3360 add the link of the Jenkins instructions from the the Jenkins status page to the top of the Project Readiness for Amber Release wiki page. 
   10. Action/ PTLs must update their release notes in their documentation by 13 Nov 2019 .
       1. weichen ni there is an issue on the documentation.  There is an inter-sphinx issue and working with Aric (LF) and Chris from AT&T to solve the issue.  
   11. Action/ TOC Docker hub prefix naming vote due 13 Nov 2019 .  Suggestion was made to call the prefix o-ran-sc.
       1. Jack suggested we use o-ran-sc and o-ran-scp.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Readiness for Amber Release
         1. we are in week 44. At this point we should be preparing to branch the code.
            1. Yes, branching now vs. later.  Now there will be significant changes made on both branches vs. later less items to change.
               1. No prepare for branching.  Not actually branching.  We are fixing and freezing that has to be wrapped up by the end of next week so we have one week to address any issues in the package.
   2. user-d3360 Test & Integration Planning (INT)
      1. Project Readiness for Amber Release 
      2. The teams have made good progress in turning the cells in the link above to green.
      3. What areas should we focus on to close.
         1. Producing the documentation and the minimum requirement for documentation are the release notes.
      4. Licensing License Attribution Records.  LF has a scanning process for code licenses. They will be scanning licenses that we are pulling from an upstream source are being generated by a tool.  The community should take the time to review License Attribution Records.
      5. What is the next milestone to hit by this Friday from the TOC?
         1. Was hoping to have all the cells green by today but will wait until Friday 15 Nov 2019 .  We need this done to branch the Amber code.  We need to complete the branching by next weeks meeting. 20 Nov 2019 .  Action/ user-d3360 update the TOC with the status of branching Amber on 20 Nov 2019 
         2. Action / John Murray We will vote on the licensing next week 20 Nov 2019 
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC)
         
         1. request to approve one new repo and committer changes for two existing repos as per this e-mail
            1. When we request changes from LF Aric Gardner has info.yml files for committer management.  This will be done through gerrit.  Need TOC and LF approval. 
               1. This will be handled in Bronze.
      3. user-a934b O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
         1. Thoralf: need to discuss how we know when a repo/subproject is done. So far not all is visible in readthedocs it seems.
            
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
          1. Henrik Andersson as a committer for the Non-RealTime RIC . 
          2. Motion made by John Keeney 
          3. Seconded by user-2057e
          4. VOTE: Vote taken, item passed
      11. (TBD) O-RAN Radio Unit (ORU)
   4. user-59b16 Requirements Software Architecture Committee
8. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
9. Planning for Next Meeting
10. Open Discussion
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)

2019 11 06

Zoom Meeting: 2019-11-06_toc_audio_only.m4a

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair	x
   China Mobile	Jinri Huang Co-Chair	x
   Deutsche Telekom	David Streibl
   NTT DOCOMO	Masafumi Masuda	x
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar	x

   *Quorum: 50% or more of total TSC voting members unless excluded due to attendance.  We have a quorum and can vote on activities.  

3. Review and Agree to Minutes of Previous Meetings
   1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   2. Vote to approve minutes for 30 Oct 2019 
   3. On motion made by MASAFUMI MASUDA
   4. Seconded by user-bc668
   5. VOTE: Vote taken, item passed
4. Review of Today's Agenda
5. Marketing of the Amber release (WG, LF, PR)
   1. Action/Jinri Huang  will create a framework for the marketing plan.
      
      1. A message from the call this Monday is this will be a joined release with the Linux Foundation.  We can have one quote from O-RAN leadership.
      2. user-59b16  send Jinri information about the overall targeted use case and functionality as targeted working material.  Announce the first release about the features we are delivering.  What is the main functionality and how we pull this together as a community as a milestone.
      3. The tone is important in the first press release.  We don't want to oversell.  We want to depict it as a milestone.  
      4. The LF leans towards talking about the current release and not the next release.  Hopefully we can pull together the voting for the B release and the time frame.  Trishan de Lanerolle volunteered to help.
6. Status of Open Action Items (Old Business)
   1. Action/ Community Vote for a "B" Release Name deadline. 
      1. Vote to approve closing the B release name end date 08 Nov 2019 noon UTC
      2. On motion made by Thoralf Czichy
      3. Seconded by user-bc668
      4. VOTE: Vote taken, item passed
   2. Action / Farheen Cefalu send out a note today of when we have to have our votes in by 08 Nov 2019 .  Update the site
   3. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      1. No updates .  We are in the process of setting up the VPN to the process.  Up and running.
      2. Tracy - Thinks the time is right to include the names of the participating written vendors.  Does anyone have an opinion or should I include their names in our documentation.
         1. How many participants?
            1. For the OSC POC there are additional vendors (open front haul) 5 committed members.  I have confirmation from Conscope Ericsson NEC and Nokia.  OSC O1 related use cases from slides on wiki.  Others are captured from Beijing captured on their slides.   
               1. From OSC perspective I think it is OK to put their names.  
                  1. They confirmed in writing.  I will put their names.
                     1. We have to avoid words like compliance because they're participating.  
                        1. Agree this is a demo proof of concept un-certified non-compliant.
   4. Action/ Jinri Huang  will add the F2F meeting minutes to the events page. 27 Nov 2019 
   5. Action/ John Murray to work with OAI interface.
      1. EC discussed this.  Orange proposed dividing this corporation into two stages.  Short and long term targets.  First term have a joint proof of concept.  Bad news is they don't have details of code distribution tools, integration.  One of the requests from Hank is to require Orange to come up with detailed mechanics of POC.  Long term is to have a third license from OAI.  Desire is to put this under O-RAN SC so that it will encourage O-AI community to contribute to O-RAN SC.  For this long term cooperation is not very clear.  Uncertainty whether O-AI give up their work in their own community and assign their resources to O-RAN SC.  My understanding is if we want to cooperate we should concentrate on the short term solution.
         1. The question on the short term.  Were they targeting that cooperation with O-RAN Alliance test group? O-SC test?
            1. OSC.  The software development work is mainly under our community.  Their corporation will cover our software community.
               1. We need to gather people of interest to work on this.  user-59b16 set up an architecture team.  We need to sit down and see how to use it as a target to see how to make it work.  We should create a plan.  Action/ user-59b16 Alignment and adjust their code to be compliant with O-RAN Alliance.  The time frame is as part of B release what can we achieve as interoperability.  Can we id a task with some level of interoperability with OAI.  
                  1. Rittwik - My expectation is E2 adaptors.  
                     1. Jack - These need to be listed out and agreed upon so everyone is on the same page.  We need a some statement out so we can 
                        1. Jinri - Maybe we should wait for Orange.  
                           1. Jack - They will need some support from us.
                              1. Jinri - OK 
         2. Details 
            1. There is a spreadsheet that ids the B Epics.  Action/user-59b16 send the epics to user-bc668 .  December 4 or 6 the TOC will take a vote to approve the spreadsheet.  We have this month to clean up all the epics and end to end use cases.
               1. Viswa - Will there be a vote for seed code in the repo?
                  1. We got original seed code.  We formed the individual projects with the PTLs.  The community decided what they will pull in.  We deleted some seed code.  We left that to each of the working teams.  The epics are pre- O-RAN Allliance specification.  We are working towards.  As we bring in code compliance with spec, some code may be depricated or changed to meet the specifications.
                     1. What is there is questionable code?  Are we going to getting all the code or lifecycle only?
                        1. All the integration and test drives the package.
                           1. Lusheng's team is packaging up different projects that will be included in the release.  Though some projects have not contributed enough code for detailed functionality.
                              1. Lusheng - we are asking each repo for a binary image or LF package for this release.  For next release we will run those binary artifacts and end to end stories.
                                 1. Viswa - If someone wants to check out the Amber release do they have to download from each repo?
                                    1. Yes they will have to download from each repo and we can offer the Amber branch.
                                       1. Now that we have pieces we will start to build the "B" release.  The E2E use cases will drive the build.
                                          
                                          1. If needed we can create automated script to grab the Amber release branch and put it into a big tar ball.  However for A release not everything is integrated.
                                 2. Earlier we had a word document that detailed the scope of A release.  Now that we heard there is a project will there be one for B release.
                                    1. The release architecture team should pull together and close software development and write detailed release notes.  These are a part of the documenation for the release.
   6. Action/ John Murray closing the remaining the TOC slots. 
      1. Jack sharing tes.lfanalytics.io/projects/o-ran.
         1. We are not releasing it yet because the data that is presented is not accurate. This is progress.  When clicked on we get metrics.  The site is not fully released yet.  We are continuing to work it.  Trishan de Lanerolle  there needs to be an overview.  I wanted to show the progress.  Lusheng is working with them on the first level.  Getting the public release of metrics is important to show because we want to fill in the TOC slots.
   7. Action/ user-d3360 add the link of the Jenkins instructions from the the Jenkins status page to the top of the Project Readiness for Amber Release wiki page.
      1. Chris Lott has written a very good page and I still have to create a link to it.  
   8. Action/ weichen ni  will provide PTLs with the steps that they need to view their converted docs on the documentation wiki.  He will add the link to the top of the Project Readiness for Amber Release .
   9. Action/ Each PTL write up a small clear statement about their license attribution that they can post to the email list. 
      1. This is from the license scan that the LF provided.  There is code with DSD or MIT licenses.  
      2. These licenses can be used in upstream projects. 
      3. BSD-3-Clause need to be clearly marked of which directory from the external source.  This was the assignment for PTLs to provide so TOC can approve.  
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Lusheng demonstrated the spreadsheet with the copyright and copyleft items.
      2. Project Readiness for Amber Release
      3. Do we allow an extension to the code freeze?
         1. At this point they should put the code in and it will be a part of the maintenance release if we choose to have one.  At this point freeze the code and document.  That repo won't be a part of this release.  It will be a part of maintenance release if they are green.
      4. Action/ PTLs update Project Readiness for Amber Release red rows as soon as possible.  We want to move ahead.
      5. Regarding support contact user-d3360 or Chris Lott for CICD.
      6. Action/ PTLs must update their release notes in their documentation by 13 Nov 2019 .  We will review the red rows on Project Readiness for Amber Release.  If you haven't completed give us a percentage complete.  We need a good faith demonstration.
      7. As we are preparing for releasing docker images to docker hub prefix the organization with the docker name.  TOC Co chairs have been asked for how to name this.  ORAN is NYSE for Orange.  Use o-ran.  Jack - We should use o-ran-sc or scp.  This makes it clear which license gets what.  They both begin with O-RAN.
         1. Concern about confusion around sc and scp.  I would call it o-ran-sc. Once in binary the licensing is not important.
         2. Action / TOC We need to confirm this by 13 Nov 2019 .  
   2. user-d3360 Test & Integration Planning (INT)
   3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC)
         
         1. request to approve one new repo and committer changes for two existing repos as per this e-mail
      3. user-a934b O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
   4. user-59b16 Requirements Software Architecture Committee
8. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
   1. Lusheng - email request for release status review.
9. Planning for Next Meeting
10. Open Discussion
    1. Sonia Sangari  needs access to build Jenkins jobs.   Sonia Sangari  send user-d3360  a request for Jenkins jobs access.
11. Any Other Business (AOB) 
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes
       1. Vote to approve minutes for 30 Oct 2019 
          1. On motion made by MASAFUMI MASUDA
          2. Seconded by user-bc668
          3. VOTE: Vote taken, item passed
       2. Vote to approve closing the B release name end date 08 Nov 2019 noon UTC
          1. On motion made by Thoralf Czichy
          2. Seconded by user-bc668
          3. VOTE: Vote taken, item passed
    2. Actions
       1. Action/Jinri Huang  will create a framework for the O-RAN SC marketing plan.
       2. Action / Farheen Cefalu send out a note today of when we have to have our votes in by 08 Nov 2019 .  Update the site
       3. Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
       4. Action/ Jinri Huang  will add the F2F meeting minutes to the events page. 27 Nov 2019 
       5. Action/ John Murray to work with OAI interface.
       6. Action/ user-59b16 Alignment and adjust their code to be compliant with O-RAN Alliance.
       7. Action/user-59b16 send the B release epics to user-bc668
       8. Action/ John Murray closing the remaining the TOC slots.
       9. Action/ user-d3360 add the link of the Jenkins instructions from the the Jenkins status page to the top of the Project Readiness for Amber Release wiki page. 
       10. Action/ PTLs must update their release notes in their documentation by 13 Nov 2019 .
       11. Action/ TOC Docker hub prefix naming vote due 13 Nov 2019 .  Suggestion was made to call the prefix o-ran-sc

Return to Todays Agenda ^

Archived Meetings