Technical Charter for O-RAN Software Community

2020 06

17

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		Lusheng Ji
   China Mobile	Jinri Huang Co-Chair		Weichen Ni
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar		Kristen Young
   Nokia	Juha Oravainen		Thoralf Czichy
   Radisys	Ganesh Shenbagaraman		Sachin Srivastava
   Ericsson	John-Paul Lane		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.

3. Review and Agree to Minutes of Previous Meeting 

4. Review of Today's Agenda

5. Release Votes and Approval

   Vote for Bronze Release and Integration and Test.

6. Copyright updates

7. Marketing of the current release (WG, LF, PR)

   1. Bronze Release PR

   2. Virtual Exhibition.

   3. OSC Logo status.

8. Status of Open Action Items (Old Business)

   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.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/ user-d3360 provide Trishan with the O-CU repo trouble ticket.
   8. Action/ Jinri Huang generate an email to inform Zybnek and EC regarding that we will be delaying the release 

9. 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. user-59b16 Requirements Software Architecture Committee

   3. user-d3360  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 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. user-a934b O-RAN Centralized Unit (OCU) 

      5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      6. Zhimin Yuan 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)

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

11. Planning for Next Meeting

12. Any Other Business (AOB) 

13. Meeting Summary (resolutions, new action items, etc.)

2020 06

10

Recording: 2020_06_10_03-toc.mp4

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	Lusheng Ji
   China Mobile	Jinri Huang Co-Chair	x	Weichen Ni

   x

   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.

3. Review and Agree to Minutes of Previous Meeting Meeting 

   1. The minutes of the prior meetings were reviewed, and no corrections.
      1. Vote to approve minutes for 27 May 03 Jun 2020 
      2. On motion made by John-Paul Laneby Jinri Huang
      3. Seconded by weichen niJuha Oravainen
      4. VOTE: Vote taken, item passed

4. 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.

5. 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.
6. 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.

7. 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.

8. 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.  
9. 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 

10. 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/ user-d3360 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. user-2057e 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 user-d3360 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 user-2057e
        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 user-d3360 provide Trishan with the O-CU repo trouble ticket.
    19. Action/ Jinri Huang 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.
11. Copyright updates

12. Marketing of the current release (WG, LF, PR)

    1. Bronze Release PR

    2. Virtual Exhibition.

    3. OSC Logo status.

13. Status of Open Action Items (Old Business)

    1. Action/ William DIEGO update on the coordination with the O-RAN test group

14. 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. user-59b16 Requirements Software Architecture Committee

    3. user-d3360  Integration and Test

    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. user-59b16 Requirements Software Architecture Committee

    3. user-d3360  Integration and Test

       RSAC defined flows for Bronze.  Traffic steering has been completed and successful. 
    4. Traffic Steering use case is successful.
    5. 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.
    6. 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?
          1. Lusheng: There is a short term to see how large the gap is and can we close in this release?
          2. 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.
          3. 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.  
    7. 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.  
    8. 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.
    9. Rittwik: I think you've completed 90% of testing.  The 10% can be pushed to maintenance meeting.
    Jack: We'll discuss the details in next weeks meeting.

    10. 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 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. user-a934b O-RAN Centralized Unit (OCU) 

        5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

        6. Zhimin Yuan 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)

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

16. Planning for Next Meeting

17. Any Other Business (AOB) 

18. 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. , and no corrections.
          1. Vote to approve minutes for 03 Jun 2020 
          2. On motion made by Jinri Huang
          3. Seconded by Juha Oravainen
          4. VOTE: Vote taken, item passed
       5. On motion by user-d3360 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 user-2057e
          Seconded by weichen ni
          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.Action / Jack send the highlights out on the reflector before the press release.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/ user-d3360 provide Trishan with the O-CU repo trouble ticket.
       8. Action/ Jinri Huang generate an email to inform Zybnek and EC regarding that we will be delaying the release 

Archived Meetings