Technical Charter for O-RAN Software Community

TOC Meeting Info

Technical Oversight Committee meetings are open to the public and held on Wednesdays at 8 AM Eastern Time USA.  World Time Zone Map

Zoom 2 Info:

• Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/6540568082
• Or Telephone: Dial (for higher quality, dial a number based on your current location)
  • 855 880 1246 (Toll Free), 877 369 0926 (Toll Free)
  • Meeting ID: 654 056 8082
  • International numbers available: https://zoom.us/u/acyy3hylQi

2019 08 28

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu (AT&T)

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair
   China Mobile	Jinri Huang Co-Chair	x
   Deutsche Telekom	David Streibl	x
   NTT DOCOMO	Masafumi Masuda	x
   Orange	William Diego	x	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 Meeting
   1. he minutes of the prior meeting were reviewed, and there were no corrections. On motion made by user-2057e  and seconded by William DIEGO  the minutes of the August 21, 2019 meeting were the approved by the TOC members. 
      1. VOTE: Vote taken, item passed.
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
   1. Action/ Farheen Cefalu correct audio recording of previous minutes.
   2. Action/ Thoralf Czichy  open a ticket with LF regarding your issues with CLA instructions.  Or email Trishan de Lanerolle directly.
      1. Issues are related to CLA.  Lusheng - Companies problems with signing of CLA.  When our contributors try to sign most companies have already gone thru the process. They see their company already listed because of previous signing of ONAP.  CLA manager who has already signed the document for ONAP.  When they sign they get a message that the company has not signed with O-RAN. Resolve by having the company to sign both O-RAN and ONAP by the same legal entity or have LF support the process.
         1. Trishan - We have been working the issue.
         2. Thoralf - We had discussion with Jacob.  Seems to work to the extent that the CLA manager can add individual emails to the white list.  Issue is progress.  White list requirement is signing of CLA.  Keeping the ticket open until we confirm it works.
         3. Jinri - Lusheng has written a tutorial on the CLA but it is only for a sunny day scenario.
   3. Action/ Farheen Cefalu  add link to other upstream projects such as ONAP on the Release Planning page.
   4. Action/ Brian Freeman will send Architecture link to Jack Murray.
   5. Action/ Farheen Cefalu update the navigation bar and the TOC page.
   6. Action/ user-d3360 post the recorded test and integration team meetings on the wiki.
   7. Action/ Farheen Cefalu  take a look at email from yesterday to main@list regarding the Events page. Encouraged to register.
      1. Will the meetings in Costa Rica be available remotely?
         1. Yes.
   8. Action/ user-d3360 discuss new Linux Foundation process for repo/committer management using an INFO.yaml file at TOC.
      1. LF is stream lining the process by updating the INFO.yml file added to the root of each repo.  We need TOC support to switch to the new operating procedure.  Trishan and Andy can support us with the new automated procedure.
         • Andrew Grimberg - Info.yml how to see who the committers on the project are.  Current schema was worked on for six months.  The initial schema was built out last year long before O-RAN.  Info.yml is simple file that defines the repo who the committers are and regular meeting info and mailing lists.  Well defined schema.  Automation - self automation for committers.  Committers can vote amongst themselves and notify the TOC and can allow committers to self commit and add the governing body as well.  We have a job on jenkins that checks if there are enough people to vote such as plus 1 and plus 2 and quorum before it can be merged.  Back end gives committer rites.  Not quite ready with the automation yet.
           • Thoralf - How can TOC approval be done?
             • committer voting is plus one and plus two.
             • repo creation will hold the initial seed info.yml files and the TOC will be able to vote.
             • How will the TOC approval for committers be done?
               • The TOC approvers will be able to do the plus one in gerrit.  This is in beta.  
             • What about multiple sub-repos?
               • Each repo will have to have this info.yml file. Heirarchical inheritance is not viable in github.
             • Lets say verify job passes doe we need to explicitly add the committers or will the system auto-add the reviewers?
               • Action/ Andrew Grimberg will check with the engineer of whether or not the automated process to auto-add the reviewers.
             • When will it be ready?
               • Technically it is being used now.  Chris Lott made a push to get most of the info.yml files but there was no documentation.  Documentation has to be added.
               • Action/ Andrew Grimberg provide documentation and proposal.  
               • Action/ Andrew Grimberg vet the TOC process with the TOC members.
                 • Issue with TOC members who don't log into gerrit.  Not difficult but the TOC have logged in at least once.
                 • Martin Skorupski  - Having issues with invalid info.yml file.  
                   • Send it directly to Andrew Grimberg
               • Action/ Andrew Grimberg provide clear instructions on how TOC members to get a gerrit account and the process through email list.
   9. Action/ user-59b16 discuss MWC americas 2019 demo plan
      1. Demo got gate 1 approval. 
      2. Pending booth approval.
      3. Thoralf check with Ramsey for approval.
         1. Thoralf - I sent him a reminder.
         2. Rittwik - it is an urgent request.
         3. Jinri - next meeting is September 9.  Paul will bring this.

1. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
   2. Release planning link.
      1. Ganesh (Radisys) - assistance with Jira access for Sachin?
         1. Lusheng - I can assist. 
2. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non real time RIC (RAN Intelligent Controller) - John Keeney
      1. We are struggling with multiple java versions.  Such as ONAP is running with java 8 and O-RAN is running with java 7.  This may be an issue for the test and integration planning.
         1. Lusheng - Let's discuss at test meeting.  We will try to provide base doc image layers to unify the platform but not prepared to do this in release Amber.
   2. RIC Applications - Matti Hiltunen
   3. RIC Platform - Thoralf Czichy
      1. Add committer request for Hila Anina  ric-plt/nodeb-rnib. On motion made by Thoralf Czichy and seconded by user-2057e
         1. VOTE: Vote taken, item passed.
   4. O-RAN Centralized Unit user-a934b
   5. O-RAN Distributed Unit High Sachin Srivastava
   6. O-RAN Distributed Unity Low Zhimin Yuan
   7. O-RAN Radio Unit (TBD)
   8. Operations and Maintenance - Martin Skorupski
   9. Simulations - Alex Stancu
   10. Infrastructure - Xiaohua Zhang
   11. DOC - weichen ni

3. Test & Integration Planning - Lusheng

   1. Sonar reporting issue.  No longer blocked.  
      1. Thoralf - We are blocked for two weeks but it is complicated.
         1. Andrew is OK with getting the repo in pieces.  Include Thoralf.
4. Requirements Software Architecture Committee - Rittwik

5. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

   1. An AP from Executive Committee: to evaluate & identify any content during our SW development requiring 3GPP's permission and, to estimate when it needs interaction with 3GPP;
   2. Jinri - 3GPP copyrite issue.  during software development for O-CU some content such as a table from 3GPP specs. Table is from 3GPP spec.  Before implementing this code it needs to be approved by 3GPP.  Jack brought this to EC.  Two ways.  Treat this issue case by case.  EC to EGPP.  O-RAN Alliance is seeking an umbrella agreement with 3GPP that will cover all the cases.
      1. Development focus member will have a general discussion.  Evaluate and identify content that requires 3GPP conditions.  We do have a lot.  If so we have issues.  
         1. What does 3GPP permission mean?
            1. Lets say we have modulation scheme index (table) will be defined in 3GPP.  We need to implement something with this table then we need the copy-rite permission from 3GPP to permission.
            2. This is pre-spec.  Concerned that we will have to get permission from every table on a case by case basis.
               1. Team is investigating an umbrella agreement to simplify the process.
6. Any Other Business (AOB)
   1. Jinri will talk to Jack about covering progress as well as blockers from the PTLs.  Suggestion to make it monthly or use release milestones.
7. Meeting Summary (resolutions, new action items, etc.)

2019 08 21

Zoom meeting: 2019-08-21.mp4 audio only

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu (AT&T)

2. Roll Call & Quorum Check 

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair
   China Mobile	Jinri Huang Co-Chair	x
   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 Meeting.
   1. Action/ Farheen Cefalu correct audio recording of previous minutes.
      1. The minutes of the prior meeting were reviewed, and there were no corrections. On motion made by user-2057e  and seconded by William DIEGO  the minutes of the August 14, 2019 meeting were the approved by the TOC members. 
         1. VOTE: Vote taken, item passed.
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
   1. Action/ John Murray CLA status.  Thoralf-2018-08-21 (RICP): new CLA process causes some issues (many committers can't commit to master (even if we can push)). Want to use CLA manager approach, but did not yet find the correct way to add additional CLA managers (current one was on an inter-continental flight yesterday). We try now via existing CLA manager and via email to docucla@linuxfoundation.org .
      
      1. The lfai is turned on and ready for use.
      2. CLA is having issues.
      3. Action/ Thoralf Czichy  open a ticket with LF regarding your issues with CLA instructions.  Or email Trishan de Lanerolle directly.
   2. Action/ John Murray will send Farheen Cefalu the link to CLAs that will link to from here. https://lfcla.com
   3. Action/ Farheen Cefalu set up the page for the face to face O-RAN meeting and put the power point slide from  Zbynek  on the schedule.
   4. Action/  Ganesh Shenbagaraman and Alex Sun decide on a names for Layer 1 and Layer 2.
      1. Alex and Ganesh are good with the two project names.  We had one project called O-DU we have proposals from Radisys and Intel.  It is difficult for one PTL to cover.
         1. O-DU-High (ODUHIGH)
         2. O-DU-Low (ODULOW)
         3. On motion made by to made by Alex Sun   seconded by user-2057e to approve  Sachin Srivastava PTL for O-DU Hi  Zhimin Yuan PTL for O-DU Low
            1. VOTE: Vote taken, item passed.
      2. On motion made by user-2057e  seconded by Ganesh Shenbagaraman to agree on the project keys to be ODUHIGH and ODULOW
         1. VOTE: Vote taken, item passed.
   5. Action/ Farheen Cefalu  add link to other upstream projects such as ONAP on the Release Planning page.
   6. Action/ Brian Freeman will send Architecture link to Jack Murray.
   7. Action/ user-59b16 will discuss with Matti Hiltunen and Tracy Van Brakle regarding the near and non real time RICs about demos for MWC North America.
      1. ORAN Alliance will have demos at MWC North America
      2. Rittwik spoke to Matti about doing a near real time RIC demo.  It will be recorded.  MWC-A we can promise a recorded video for near real time RIC.  Are the demos presented by individual companies or by O-RAN SC?
         1. O-RAN SC
         2. Is this an O-RAN demo or something under AT&T?
            1. O-RAN demo and the contributing companies are AT&T and Nokia.
            2. There is an email from Paul to do a gate 1 check.  Jinri Huang send Rittwik the email.
   8. Action/ TOC voting members please vote through email reflector on any approvals for committers and new repo requests.
      1. RICAPP Matti Hiltunen  this is TS light gigascope.  A streaming library in the mcXapp.  It can be used as a common library for the software stack to use.  
         1. Does it have it's own upstream. yes
         2. Why is it lite?  Streamlined to purchase high volume of data with half a core.  Lite weight in resource consumption.
         3. Initial committers are listed in the email sent by Matti Hiltunen about 20 hours ago.  
         4. On motion made by Matti Hiltunen  seconded by user-2057e approve the request to create a gs-lite repo.
            1. VOTE: Vote taken, item passed.
         5. OTF - open testing framework allows orchestration on the framework.  Design test flows and test cases.  To host the related code and configurations we would like to request it/off.  Three committers have been involved with the OTF.  OTF is inside AT&T and is moving forward to become open.  Lusheng is the PTL for test.  In Alliance there is a test integration group.  They will be responsible for the end to end test.  Some partners are planning to establish and open test and integration center. 
            1. David Kinsey spoke to focus groups.  WG4 has a test spec graph available.  We are looking into how to perform a test exercise between the two test groups.
            2. David - ONAP wiki framework?  OTF integration with ONAP did not go forward.  This will be OTF as a design entity.  We are proposing to bring it in stand alone.  If ONAP wants to adopt they will upstream to us.
               1. On motion made by user-d3360  seconded by user-2057e to create a repo for if/otf and the following committers.
                  1. Eliza Celenti 
                  2. Qun Luo
                  3. Rohan Patel
                     1. VOTE: Vote taken, item passed.
6. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager/Release Planning: Weekly TOC Scheduling
   2. Release planning link.
      1. Three months left for the release schedule.
7. Report out from PTL: Stand-Up & Report Out on Blockers
   1. Non real time RIC (RAN Intelligent Controller) - John Keeney
      1. No issues.  Can we replace RICNRT with NONRTRIC.
         1. Action/ Farheen Cefalu update the navigation bar and the TOC page.
   2. RIC Applications - Matti Hiltunen
   3. RIC Platform - Thoralf Czichy
   4. O-RAN Centralized Unit user-a934b
   5. O-RAN Distributed Unit (TBD)
   6. O-RAN Radio Unit (TBD)
   7. Operations and Maintenance - Martin Skorupski
   8. Simulations - Alex Stancu
   9. Infrastructure - Xiao
   10. DOC - weichen ni

8. Test & Integration Planning - Lusheng

   1. We will tap into a US funded project for Advanced networking and cellular networking infrastructure.  We will allow access to hardware that the community can share and test.  We will further pursue.  AT&T can provide virtual resources for supporting this project.  Call to action to any other companies to get involved. 
      1. Was the meeting recorded? 
         1. yes, haven't have a chance to update the wiki.  Action/ user-d3360 post the recorded.
      2. Is it a regular meeting?
         1. Yes, same bridge after this meeting.
   2. OTF discussion of how it can be used to test O-RAN SC development to use for demos.  The OTF team will be making a presentation in the next hour regarding OTF.Report Out of Sub-Committees
9. Requirements Software Architecture Committee - Rittwik
   1. We started Release B planning.  Bring items to the RSAC meeting on Thursday.
   2. We are altering between Tuesday and Thursday.
   3. Once a week rucurring meetings.  It is Tuesday one week and Thursday the alternate week.

10. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items

    1. O-RAN October f2f meeting update (Jinri Huang)
       1. Action/ Farheen Cefalu  take a look at email from yesterday to main@list regarding the Events page. Encouraged to register.
    2. LFN Developer Days (Jinri Huang)
       1. ONAP developer day.  Jinri will talk at this event.  He will talk about software community, O-RAN Alliance.  Jinri will post the speech time tomorrow.  It will be next week.  If anyone wants anything included in the speech reach out to Jinri.
11. Any Other Business (AOB)
12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes
       1. The minutes of the prior meeting were reviewed, and there were no corrections. On motion made by user-2057e  and seconded by William DIEGO  the minutes of the August 14, 2019 meeting were the approved by the TOC members. 
          1. VOTE: Vote taken, item passed.
       2. On motion made by to made by Alex Sun   seconded by user-2057e to approve  Sachin Srivastava PTL for O-DU High  Zhimin Yuan PTL for O-DU Low
          1. VOTE: Vote taken, item passed.
       3. On motion made by user-2057e  seconded by Ganesh Shenbagaraman to agree on the project keys to be ODUHIGH and ODULOW
          1. VOTE: Vote taken, item passed.
       4. On motion made by Matti Hiltunen  seconded by user-2057e approve the request to create a gs-lite repo.
          1. VOTE: Vote taken, item passed.
       5. On motion made by user-d3360  seconded by user-2057e to create a repo for if/otf and the following committers.
          1. Eliza Celenti 
          2. Qun Luo
          3. Rohan Patel
             1. VOTE: Vote taken, item passed.
    2. Actions
       1. Action/ Farheen Cefalu correct audio recording of previous minutes.
       2. Action/ Thoralf Czichy  open a ticket with LF regarding your issues with CLA instructions.  Or email Trishan de Lanerolle directly.
       3. Action/ Farheen Cefalu  add link to other upstream projects such as ONAP on the Release Planning page.
       4. Action/ Brian Freeman will send Architecture link to Jack Murray.
       5. Action/ Farheen Cefalu update the navigation bar and the TOC page.
       6. Action/ user-d3360 post the recorded test and integration team meetings on the wiki.
       7. Action/ Farheen Cefalu  take a look at email from yesterday to main@list regarding the Events page. Encouraged to register.