Recording: 2020-12-16_toc.mp4

Agenda

1. Call for Scribe (minutes owner): Thoralf Czichy

2. Roll Call & Quorum Check 

   *Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   // Yes, we have a quorum and can vote on activities.

3. Review and Agree to Minutes of Previous Meeting

   1. Decision: Motion by Thoralf, second by Jinri. No objections. 2020-12-09 minutes approved

4. Review of Today's Agenda.

5. Release Votes and Approval.

   1. Cherry release status

      1. All code has been branched. Tar ball already created and included in release page. All docker containers have been released. Ready. Most projects have updated their documentation. Felix working on "getting started" page. tar ball and getting started page link is available on Cherry page: Cherry Release (Dec 2020)

      2. Discussion on documentation

      3. Jack: Is it clear where to ask questions? Felix proposed that the integration team acts as contact as well as the PTLs of the individual subprojects.

      4. Jinri is working on blog/press release, but seems not yet approved by EC, but plan is to get it released today in the blog. Still discussion related to quotes from Radisys and WR (Gil H. asked about this in the meeting). EC makes final decision and we might not include quotes from everyone in every release to balance this out. Jack trying to see what EC policy on this is. Jinri also provided number of source code commits to EC.

      5. Thoralf commented that the Dawn timeline needs an update for the week numbers and, e.g., Feb-3 should be Feb-1 (as that's a Monday). Jack will fix.

      6. Q: there seems to be still changes? Felix confirmed that documentation and binary artifacts (tar balls, and release images) are fixed and available.

      7. Jinri: What is the official release data for Cherry? Jack: depends on what you want to call it. Press release date vs last artifacts uploaded (Tue, Dec-15 confirmed by Felix): We decided on release date as Dec-15-2020. Jinri will update PR accordingly.

6. Copyright update. 

   1. Copyright permission proposal to be approved by O-RAN EC.

      1. Jack: shared the proposal to TOC members. Action point: TOC members Please review copyright permission proposal and provide feedback and  setup a meeting with Jack to discuss if needed

      2. 2020-12-16:

         1. Jack shared with TOC members the draft (last week). There's an update to the draft, which Jack will send out (post-meeting update: this was sent about 10min after the meeting). Refinements happened based of comments by some member (separating code and documentation). Word "copyright" added to the title.

         2. John-Paul asked for purpose of separating code and documentation. Jack: seemingly because they (the licenses) are structured differently. John-Paul might still send comments to Jack.

         3. Jack says he hopes this to be acceptable to 3GPP as well. But Jack not involved in 3GPP discussions.

         4. Jack hopes for end of January this being finalized and posted by O-RAN alliance, e.g., visible under the same page as the other "o-ran.org/software" page talking about licenses.

   2. Copyright case to be resolved with 3GPP.

7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. WG1 MVP proposal by early December.

   2. OSC Cherry blog post and PR

      1. Gu Su has draft PR 

   3. PoC on Dec 3.

   4. 2020-12-16: Re-election in O-RAN EC. The one going out is also sitting in O-RAN-SC TOC as well. We might have to talk about O-RAN-SC TOC composition.

      1. need to go back to our charter.

      2. we might want to do elections and work on this in the beginning of next year.

   5. 2020-12-16: MVP (minimum viable product) was discussed as well in EC. We need to pay attention to that plan. 2021 will be a critical year. For example, OCU being important. More participation is needed. More companies. We do have a challenge around the integration team, also on SMO side. We do need a PTL for the integration and test project ideally with five participants and better alignment with test focus group on O-RAN alliance side. Dawn will need an improvement in this area, also because use cases become more complex.

   6. 2020-12-16: once we come back next year we need to produce a session (middle/end of Jan) for O-RAN alliance to show what we achieved in Cherry and look for their feedback.

      1. Rittwik: traffic steering and network slicing was discussed in earlier O-RAN - O-RAN-SC virtual face-to-face, but unsure what actually makes up the MVP

      2. Jack promised to set up a call, probably part of Rittwik's architecture sessions.

      3. Jinri: end of Jan or beginning of Feb is next virtual f-2-f on O-RAN alliance side.

      4. key is to make sure what we aim for in Dawn and "E" release.

8. Status of Open Action Items (Old Business).

   1. O-CU development and O-CU for Cherry traffic steering use-cases.

      1. New O-CU PTL onboarding.

      2. Binary version of Radisys O-CU.

         1. Radisys legal document to be sent to Jack and Jinri in week of Nov 30.

         2. 2020-12-16: Ganesh sent the agreement to Jack and Jinri. Jinri to forward this to Stefan and follow up with Stefan to get this finalized. Use of a binary as a test fixture for OCU. Still a challenge to get an OCU implementing the O-RAN alliance interfaces.

   2. Cherry deliverable summary page (see  Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.

      1. PTLs to keep summary page for Cherry release current and up-to-date. 

      2. 2020-12-16: Close this

   3. Dawn Release requirement

      1. 2020-12-16: still open

   4. "E" Release naming.

      1. "E" Release voting ongoing.

      2. 2020-12-16: Jack proposed to continue with only letters. To remove any possibility of potential negative associations with colors in the diverse cultural backgrounds we operate in.

   5. CII Badging

      1. Action Point PTLs to go through the questionnaires to know gaps by Jan 2.

      2. Liaison with Security TG to be set up.

   6. Cooperation with ONF, OAI and ONAP.

      1. ONAP alignment to be discussed.

9. Standing Agenda Items (Brief Status of Ongoing Activities)

   1. Release Manager @Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. CherryTimeline

   2. @Former user (Deleted) Requirements Software Architecture Committee

   3. @Zhe Huang (Felix) (Felix) Integration and Test

      1. Decision: Move by Jack , second by Jinri. No objections. Felix approved as a committer to it/int, it/otf and it/test repositories 

      2. O-DU low contributions. Action point Felix please resolve with Trishan

   4. Report out from PTL: Stand-Up & Report Out on Blockers

      1. @John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      2. @Matti Hiltunen RIC Applications (RICAPP) 

      3. @Thoralf Czichy RIC Platform (RIC)

      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. @Mahesh Jethanandani Service Management and Orchestration (SMO)

      12. (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) 

    1. This week will be the last TOC meeting of the year and we will continue on January 6th and begin the process for Dawn release. Juha will be scribe of Jan 6th meeting

       1. Next meeting: January-6-2021

    2. Tracy: not sure if press release will include reference to proof-of-concept. But note that PoC included WG1 November train output. Jinri to close out the press release.

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

Recording: 2020-12-09_toc.m4a

Agenda

1. Call for Scribe (minutes owner): Juha Oravainen

2. Roll Call & Quorum Check 

   *Quorum: 50% or more of total TOC 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. Decision: Move by Juha, second by John-Paul. No objections. 2020-12-02 minutes approved.

4. Review of Today's Agenda.

5. Release Votes and Approval.

   1. Cherry approval vote on Dec 9.

      1. Cherry release status

         1. Felix presented O-RAN Cherry Release Integration and Testing readout: Cherry-release-readout.pptx

         2. Felix presented highlighted use cases

         3. Rittwik: Use cases are ok from RSAC point of view

         4. Felix: Delivery Status Overview

            1. Release recommendation is green for all the other projects except for Integration/OTF, OAM and O-CU

         5. Jack:How many use cases did not get validated at this point?

         6. Felix: Use cases highlighted by RSAC are all validated

         7. Rittwik: Within the realms we have in open source we have got it to make it work. If the component doesn't exist, we can't make the full stack work.

         8. Jack: And it is documented what works and what doesn't?

         9. Rittwik: Yes

         10. Jack: Is there anything that has the light green tick, which won't be completed by Saturday

         11. Felix: No

         12. Jack: Let's see red boxes, O-CU clearly is not being released as part of Cherry release. Does anybody has any concerns to exclude O-CU from the release?

         13. Decision: O-CU is not supported in C-release, no objections

         14. Integration/OTF

             1. Felix: My proposal is to defer OTF Framework to Dawn release because OTF Helm charts needs further integration

             2. Jack: Do we defer this to Dawn or can we complete this in maintenance release? Does this require new code?

             3. Felix: New code is needed but is doable by the end of January 2021

             4. Jack: Proposal is to acknowledge that OTF Framework has some defects and will be postponed to maintenance release. Does anybody has any concerns with this?

             5. Decision: OTF has been postponed to maintenance release, no objections

         15. OAM

             1. Jack: EC raised some concerns how dependant OAM is from ONAP

             2. Tracy: This will be discussed on Friday TSC meeting.

             3. Jack: We are trying to find the right path through this and make sure both communities get what they need and move forward

             4. Felix: OAM contains EPL-1.0 license. LF can't exactly identify which pieces of the code is under this license and they raised a question how code is downloaded from the upstream project? Could we use Apache-2 license instead? 

             5. Jack: Who will resolve this question because we can't release that particular repository until we get this resolved?

             6. Martin: My proposal is not to release this part of the code

             7. Tracy: I'm optimistic that this issue will be solved but not in this release

             8. Jack: Proposal is not to release this part of the code

             9. Jack: Two actions. 1. To remove TR69 part from the release and 2. to address the licensing issue

             10. Felix: Most of the OAM code is in ONAP repositories. All container images and Helm charts are contributed to ONAP. My biggest concerns are that there is no source code in OSC, binaries are pointing to ONAP projects, platform integration and deployment are done through ONAP OOM, there are challenges in releasing E2E flows due to data model licensing issues (3GPP) and it is hard to recreate E2E flows in OSC labs. I need guidance from TOC on release strategy

             11. Jack: There is minimum ONAP build you use. How many components you are using?

             12. Martin listed the components

             13. Rittwik: Why don't you fork the code?

             14. Martin: I don't need to fork it because all the functionality is already existing and the problem is that we are now in the level and working more closely with ODL teams and we are now moving more from ONAP towards ODL. I'd not like to fork ODL.

             15. Mahesh: SMO has also lot of dependencies and I'm not sure why we have SMO project?

             16. Jack: OAM and non RT-RIC are very big components of SMO. If there is no code in OSC repos then there is nothing to release. We need to continue this discussion and figure out what is the best way to continue the structure of this work going forward

             17. Jack: In Cherry there is no code or processes in OSC Cherry that need to be released for OAM?

             18. Martin: There is something for YANG validation. One repository and one folder

             19. Jack: There will be a minimum OAM released and documentation needs to be setup that way. The bigger issue is how this should work over time.

             20. Tracy showed a slide, which was prepared for O-RAN TSC: Attachments - Use case demonstration - OAM - Confluence (o-ran-sc.org)

             21. Jack: We are going to release Cherry. I make the motion to approve C-release, exclude O-CU, footnote OTF that it will be corrected in maintenance release and OAM will be minimised to repositories to support SMO. Does any TOC members have any concerns with this path?

             22. Rittwik: Which Yang model we are using in open FH?

             23. Martin: We can release like in B-release

             24. Decision: Move by Jack, second by Jinri. No objections. C-release approved with exceptions

6. Copyright update. 

   1. Copyright permission proposal to be approved by O-RAN EC.

      1. Jack: shared the proposal to TOC members. Action point: TOC members Please review copyright permission proposal and provide feedback and  setup a meeting with Jack to discuss if needed

   2. Copyright case to be resolved with 3GPP.

7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. WG1 MVP proposal by early December.

   2. OSC Cherry blog post and PR

      1. Gu Su has draft PR 

   3. PoC on Dec 3.

8. Status of Open Action Items (Old Business).

   1. O-CU development and O-CU for Cherry traffic steering use-cases.

      1. New O-CU PTL onboarding.

      2. Binary version of Radisys O-CU.

         1. Radisys legal document to be sent to Jack and Jinri in week of Nov 30.

   2. Cherry deliverable summary page (see  Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.

      1. PTLs to keep summary page for Cherry release current and up-to-date. 

   3. Dawn Release requirement

   4. "E" Release naming.

      1. "E" Release voting ongoing.

   5. CII Badging

      1. Action Point PTLs to go through the questionnaires to know gaps by Jan 2.

      2. Liaison with Security TG to be set up.

   6. Cooperation with ONF, OAI and ONAP.

      1. ONAP alignment to be discussed.

9. Standing Agenda Items (Brief Status of Ongoing Activities)

   1. Release Manager @Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. CherryTimeline

   2. @Former user (Deleted) Requirements Software Architecture Committee

   3. @Zhe Huang (Felix) (Felix) Integration and Test

      1. Decision: Move by Jack , second by Jinri. No objections. Felix approved as a committer to it/int, it/otf and it/test repositories 

      2. O-DU low contributions. Action point Felix please resolve with Trishan

   4. Report out from PTL: Stand-Up & Report Out on Blockers

      1. @John Keeney (Ericsson EST) Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)

      2. @Matti Hiltunen RIC Applications (RICAPP) 

      3. @Thoralf Czichy RIC Platform (RIC)

      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. @Mahesh Jethanandani Service Management and Orchestration (SMO)

      12. (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) 

    1. Next week will be the last TOC meeting of the year and we will continue on January 6th and begin the process for Dawn release. Juha will be scribe of Jan 6th meeting

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

    1. Decision: O-CU is not supported in C-release

    2. Decision: OTF has been postponed to maintenance release

    3. Decision: Approve C-release, exclude O-CU, footnote OTF that it will be corrected in maintenance release and OAM will be minimised to repositories to support SMO

    4. Action point: TOC members Please review copyright permission proposal and provide feedback and  setup a meeting with Jack to discuss if needed

    5. Decision: Felix approved as a committer to it/int, it/otf and it/test repositories 

    6. Action point Felix please resolve O-DU low contribution issue with Trishan

Recording: 2020-12-02_toc.m4a

Agenda

1. Call for Scribe (minutes owner): Juha Oravainen

2. Roll Call & Quorum Check 

   *Quorum: 50% or more of total TOC 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. Decision: Move by Masafumi, second by Jinri. No objections. 2020-11-25 minutes approved.

4. Review of Today's Agenda.

5. Release Votes and Approval.

   1. Cherry approval vote on Dec 2.

      1. Jack: Rittwik, how is the documentation and preparation work for the C-release proceeding?

      2. Rittwik: Documentation is coming through and we are identifying some Dawn use cases

      3. Jack: Where in the Wiki is the documentation?

      4. Rittwik: We can put the pointers from the regular SW dev page to integration page

      5. Jack: This should be put to Cherry release page. Introduction, how to get started, where to get SW and other relevant documentation/links  should be found from Cherry release page

      6. John: Every project has their own documentation. Please add these links to documentation page

      7. Jinri: Do you need help in documentation?

      8. Rittwik: Yes, I'll contact to Weichen

      9. Jinri: Please copy also me when you contact Weichen

      10. Jack: We have only 10 days left before release date, which is Dec 12th. We are not ready to vote yet but  everything needs to be done by next week's TOC meeting

      11. Integration and Test status, please see chapter 9c below

6. Copyright update. 

   1. Copyright permission proposal to be approved by O-RAN EC.

      1. Jack: Proposal got from the legal team and this will be discussed on Friday how to proceed and after that we start sharing it. Expect me to start to reach out at the beginning of next week with a copy what we are proposing and setting up meetings.

      2. Jack: Anyone who is interested in reviewing the copyright statement, please let me know.

      3. Jack: This should cover all of the O-RAN original copyrighted material but it does not address 3GPP copyright items

   2. Copyright case to be resolved with 3GPP.

      1. Jack: This work is done by standards group. We have some inputs to the process and tracking it but they are the one who are leading the work with 3GPP

7. O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)

   1. WG1 MVP psoposal by early December.

   2. OSC Cherry blogpost draft submission by Dec 2.

      1. Jinri: We are working with the blog post. We already got input from Rittwik but we need still input/highlights/summary from projects.

      2. Jinri: We need also short descriptions to highlight key features from each project. This is mainly for PR

      3. We need also quotes from the contributing companies to PR. So far we have input from WR, Nokia and Ericsson

      4. Jack: Cherry release date is 2020-12-12

      5. Jinri: Deadline for inputs is this Friday as there will be EC meeting next week

   3. PoC on Dec 3.

8. Status of Open Action Items (Old Business).

   1. O-CU development and O-CU for Cherry traffic steering use-cases.

      1. New O-CU PTL onboarding.

      2. Binary version of Radisys O-CU.

         1. Radisys legal document to be sent to Jack and Jinri in week of Nov 30.

   2. Cherry deliverable summary page (see  Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.

      1. PTLs to keep summary page for Cherry release current and up-to-date. 

   3. Dawn Release requirement

   4. "E" Release naming.

      1. "E" Release voting ongoing.

   5. CII Badging

      1. Action Point PTLs to go through the questionnaires to know gaps by Jan 2.

      2. Liaison with Security TG to be set up.

   6. Cooperation with ONF, OAI and ONAP.

      1. ONAP alignment to be discussed.

9. Standing Agenda Items (Brief Status of Ongoing Activities)

   1. Release Manager @Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. CherryTimeline

   2. @Former user (Deleted) Requirements Software Architecture Committee

   3. @Zhe Huang (Felix) (Felix) Integration and Test

      1. Jack: we need more people in Integration and Test project in D release. One person really can't do all this stuff.

      2. Felix: Cherry Release Testing Plans: Cherry Release Testing Plans - Integration and Testing - Confluence (o-ran-sc.org) Here you can find all the flows what we want to test

      3. Felix: near RT-RIC has some new flows

      4. Thoralf: In the worst case scenario we can't test all of these

      5. Jack: Please make sure and say what flow is approved and part of the release and what isn't 

      6. Jack: It is important to map use cases and e-2-e flows we are testing

      7. Rittwik: There is not one to one mapping

      8. Jack: It doesn't have to be but there should be a place where we can see which work flows support which use cases

      9. Felix: Some part of the non RT-RIC code is contributed to ONAP, which means we need to use artifacts from ONAP

      10. John: I see no problems here as code is copied from ONAP and re-released via OSC + both releases use Apache-2 licence. So, licenses are compatible

      11. Jack: This is ok from open source point of view. The only question is, if they make changes to that code we are referencing in OSC and it breaks our downstream usage. PTL and the team is responsible to make sure it builds and works properly and delivers it to Integration and Test project

      12. David Kinsey: Why can't we use the boundary or container of that it is part of ONAP?

      13. John: There are several possibilities but we see this the most feasible and flexible option at the moment

      14. John: We can use the code in two different projects

      15. Felix: There is "Copyright 2020 Nordix Foundation" license headers in some non RT-RIC code