/
2021 Q4 (Oct, Nov, Dec)

2021 Q4 (Oct, Nov, Dec)

Apr 07, 2022

2021 12 15

Recording: toc recording

Agenda

  1. Call for Scribe (minutes owner): @Former user (Deleted)

  2. Roll Call & Quorum Check 

    *Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

  3. Review and Agree to Minutes of Previous Meeting

    1. Decision: Minutes for TOC meeting approval: proposed by David seconded by James The motion is approved

  4. Review of Today's Agenda

  5. Release Votes and Approval

  6. AAL project

    1. Action point: Trishan to check if your have to sign a new agreement for the repo if TOC decides on BSD license use. Refer to minutes of previous meeting(s) for details.

      1. Update on 11/17/21 : @Trishan de Lanerolle we can put an exception clause for introduce a new license (BSD), this will be done in coordination with WG6.

    2. Action point: Jack to present the write up about the AAL project  to have a vote.

      1. This was put on the table on 2021-07-07 meeting

      2. Jack: There is discussion ongoing in WG6 and we're still waiting for some aspects that discussion to be resolved. Some clarifications were made but until we get more information we leave this table for now

      3. No update on  12/01/21.

      4. No update on  12/08/21.

      5. No update on 12/15/21.

  7. Copyright update

    1. 12/01/21:

      1. Jinri: What is the status of defining the  process for moving eg. YANG files under SCCL license. There was also question if OSC charter needs update to reflect SCCL.

      2. Jack: I am working on writing the process description but it needs further work on streamlining of the process and automation. Only O-RAN SCP charter controlled by O-RAN will need update and there is ongoing discussion with legal team.

    2. 12/08/21:

      1. Jack: Progress on CLA was made. Ongoing work on the processes.

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

    1. 12/01/21:

      1. Jirni: There will be no physical O-RAN F2F meeting in Feb 21. If it happens as virtual meeting is not decided yet. 

      2. Jirni: Most of the new specs targeting November train are under review of O-RAN TSC.

      3. Jirni: There is to be confirmed plan to have 2 PRs. First one will be about plug-fest. Second one that will include OSC release E and other 2021 achievements is now planned for Jan 22.

      4. Jack: Last TOC meeting of 2021 will happen on 15th Dec and then we will resume on 5th Jan.

    2. 12/08/21: 

      1. PR for release E:

        1. Action point:  Jinri asks PTLs to provide quote and highlight of 2-3 new features or improvements in their project.

        2. Tracy: This year's joined O-RAN/TIP Plugfest used release E software. PR message should be aligned. Link to release D PR message.

        3. Please contact Jinri if your company is interested in providing quote. There is process to balance the quotes and include quotes from one company in every other PR instead of consecutively.

    3. 12/15/21

      1. Rittwik and David Kinsey will sync with Jinri about release overview

      2. Our PR is likely to be published together in O-RAN Alliance 2021 summary and possibly other pieces. 

  9. Old business and Status of Open Action 

    1. "E" Release timeline.

      1. 12/08/21:

        1. James: No blockers for release. Working with PTL to follow on their progress and what can be worked for integration. Also working on release wiki page.

        2. Trishan: License scan was executed and PTLs received email with the results. There were only few medium level issues.

        3. James will follow up with PTL to resolve all the issues.

        4. Jack: Basic required steps for release:

          1. Resolve the license scan issues and update documentation.

          2. Branch e-release before TOC call on Dec 15th

          3. TOC release vote will happen on Dec 15th.

          4. Approx. week after vote release is publishes after process of packaging.

      2.  12/15/21:

        1. James: No outstanding issues from scan, monitoring the release processes from projects. 

        2. Agreement that James will not create single tarball file for the release E as it was not created for D release. There will be reference to container image list same as it was provided for D release.

        3. Jinri makes a motion to approve of release of O-RAN SC Release E. Seconded by David. The motion is approved.

    2. OSC lab in Taiwan (Prof Ray's lab):

      1. 11/24/21 : @Former user (Deleted) initial configurations (TDD specs) is ongoing. 

    3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.

      1. 11/10/21: @Tracy Van Brakle 5G super blueprint is already taking advantage of the OSC initiated developments in ONAP (but not just ONAP). Jack: There are new functionalities that are needed that we need to make sure that gets into the roadmap.

    4. "F" Release time:

      1. 10/27/21: Rittwik: will focus on O-Cloud usecase in F release, as well as the continuation of network slicing use case. Will reach out to PTLs to check if any more use cases. And might divide use cases between Taiwan lab and New Jersey lab.

      2. 11/03/21: Jack: please reach Rittwik and David to get early information into the planning process of F release.

      3. 12/15/21: Planning discusion

        1. There are multiple smaller contributions planned for F release.

        2. NTT Docomo proposes to leverage Tacker OpenStack as upstream project for O2 implementation in SMO project but there is also WindRiver contribution on O2 so alignment will be needed in F release planning.

        3. Testing of Slicing E2E should be one of the goals of OSC Lab in release F to validate work done in E.

    5. Access to the lab, raised by @Mahesh Jethanandani

      1. Mahesh: SMO and ODU high have different access levels to the lab and VMs.

      2. @Jack Murray : Please send me the e-mail with details and I will help with the access to the lab. Access to the VMs is more dependent on each project but we can work on that.

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

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

    2. Requirements Software Architecture Committee 

    3. OSC lab

      1. Update on 11/24/21 @Former user (Deleted) :

        1. Lab is now running, all equipements are there, cables have been delivered last week. Next week, if we can get all PTP running, then the work can continue.

        2. For the Slicing UCs we need some of this preliminary work, but december seems to be short. 

        3. O2 pre-spec implementation is available (@James Li), tests could be scheduled on december - E release. @Bin Yang wanted a server that he can stand up in the OC lab to do this O2 validation. @Jackie Huang An email was send with hardware requirements.

        4. @James Liis documented on the wiki that's going on with the New Jersey lab, the Taiwan lab and also I think CMCC want to send that set up a lab in the West Coast.

      2. Update on 12/01/21:

        1. E2E slicing use-case cannot be executed fully but we are progressing. Should be functional in F release.

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

      1. @James Li Integration and Testing (INT)

      2. @Mahesh Jethanandani Service Management and Orchestration (SMO)

        1. One repo is branched. Second one waits for permition modification from LF. Code is ready for release otherwise.

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

        1. Repos are branched. Release images are ready. Small improvements of docs is ongoing.

      4. @Sunil Kumar RIC Applications (RICAPP)

        1. Branching should be done by end of the week. The release page will note which apps have been updated in E release a which are obsolete.

      5. @Thoralf Czichy RIC Platform (RIC)

        1. Ready to branch after aproval. Everything should be ready for release.

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. @Former user (Deleted)  O-RAN Distributed Unit High (ODUHIGH)

        1. Code and docs are reade. Yet to update docker image page, will do after this meeting.

        2. Action Point: @Former user (Deleted) to check that ODULOW binary is compatible with E release.

          1. ODULOW binary will be ready with maintenance release. It should be fine as we plan to do the integration in that timeframe.

      8. @Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)

      9. @Martin Skorupski Operations and Maintenance (OAM)

        1. Everything is ready.

      10. @Alex Stancu Simulations (SIM)

        1. Everything is ready. Docker images are available and code is branched.

      11. @Jackie Huang Infrastructure (INF)

        1. Code is ready but we found issue in in generated ISO image. Fixed version will be available EoW.

      12. @Weichen Ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)

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

    1. TOC vote on O-RAN SC software release E. → see point 9.a for details

  12. Planning for Next Meeting

  13. Any Other Business (AOB)

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

2021 12 08

Recording: toc recording

Agenda

  1. Call for Scribe (minutes owner): @Former user (Deleted)

  2. Roll Call & Quorum Check 

    *Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

  3. Review and Agree to Minutes of Previous Meeting

    1. Decision: Minutes for TOC meeting approval: proposed by David Streibl seconded by John-Paul Lane. The motion is approved

  4. Review of Today's Agenda

  5. Release Votes and Approval

  6. AAL project

    1. Action point: Trishan to check if your have to sign a new agreement for the repo if TOC decides on BSD license use. Refer to minutes of previous meeting(s) for details.

      1. Update on 11/17/21 : @Trishan de Lanerolle we can put an exception clause for introduce a new license (BSD), this will be done in coordination with WG6.

    2. Action point: Jack to present the write up about the AAL project  to have a vote.

      1. This was put on the table on 2021-07-07 meeting

      2. Jack: There is discussion ongoing in WG6 and we're still waiting for some aspects that discussion to be resolved. Some clarifications were made but until we get more information we leave this table for now

      3. No update on  12/01/21.

      4. No update on  12/08/21.

  7. Copyright update

    1. 11/24/21:

      1. Jack: Meeting last week for agreed on the CLA structure (not closed yet). 

    2. 12/01/21:

      1. Jinri: What is the status of defining the  process for moving eg. YANG files under SCCL license. There was also question if OSC charter needs update to reflect SCCL.

      2. Jack: I am working on writing the process description but it needs further work on streamlining of the process and automation. Only O-RAN SCP charter controlled by O-RAN will need update and there is ongoing discussion with legal team.

    3. 12/08/21:

      1. Jack: Progress on CLA was made. Ongoing work on the processes.

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

    1. 11/24/21:

      1. @Thoralf Czichynext O-RAN meeting will be virtual and probably July 2022 meeting will be face to face.

      2. Jack, Jinri and others should meet to prioritise topics for next release, time slots will be proposed for those discussions.

    2. 12/01/21:

      1. Jirni: There will be no physical O-RAN F2F meeting in Feb 21. If it happens as virtual meeting is not decided yet. 

      2. Jirni: Most of the new specs targeting November train are under review of O-RAN TSC.

      3. Jirni: There is to be confirmed plan to have 2 PRs. First one will be about plug-fest. Second one that will include OSC release E and other 2021 achievements is now planned for Jan 22.

      4. Jack: Last TOC meeting of 2021 will happen on 15th Dec and then we will resume on 5th Jan.

    3. 12/08/21: 

      1. PR pro release E:

        1. Action point:  Jinri asks PTLs to provide quote and highlight of 2-3 new features or improvements in their project.

        2. Tracy: This year's joined O-RAN/TIP Plugfest used release E software. PR message should be aligned. Link to release D PR message.

        3. Please contact Jinri if your company is interested in providing quote. There is process to balance the quotes and include quotes from one company in every other release PR instead of consecutively.

  9. Old business and Status of Open Action 

    1. "E" Release timeline.

      1. 11/03/21: PR of E release is expected for the first days of the next year. 

      2. 11/17/21 - Jack: At this window of time the code should be principally freezing with the exception of bug fixes and functionality.

      3. 12/01/21:

        1. First security scan will be executed tomorrow 2nd Dec. Branching need to ocure after sec. scan is passed by repository but before vote that is planned for 15th Dec. Additional security scan can be executed if needed.

        2. Vote on E release will happen on 15th Dec. We need to be ready by then with branches.

      4. 12/08/21:

        1. James: No blockers for release. Working with PTL to follow on their progress and what can be worked for integration. Also working on release wiki page.

        2. Trishan: License scan was executed and PTLs received email with the results. There were only few medium level issues.

        3. James will follow up with PTL to resolve all the issues.

        4. Jack: Basic required steps for release:

          1. Resolve the license scan issues and update documentation.

          2. Branch e-release before TOC call on Dec 15th

          3. TOC release vote will happen on Dec 15th.

          4. Approx. week after vote release is publishes after process of packaging.

    2. OSC lab in Taiwan (Prof Ray's lab):

      1. 11/24/21 : @Former user (Deleted) initial configurations (TDD specs) is ongoing. 

    3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.

      1. 11/10/21: @Tracy Van Brakle 5G super blueprint is already taking advantage of the OSC initiated developments in ONAP (but not just ONAP). Jack: There are new functionalitiesthat are needed that we need to make sure that gets into the roadmap.

    4. "F" Release time:

      1. 10/27/21: Rittwik: will focus on O-Cloud usecase in F release, as well as the continuation of network slicing use case. Will reach out to PTLs to check if any more use cases. And might divide use cases between Taiwan lab and New Jersey lab.

      2. 11/03/21: Jack: please reach Rittwik and David to get early information into the planning process of F release.

    5. Access to the lab, raised by @Mahesh Jethanandani

      1. Mahesh: SMO and ODU high have different access levels to the lab and VMs.

      2. @Jack Murray : Please send me the e-mail with details and I will help with the access to the lab. Access to the VMs is more dependent on each project but we can work on that.

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

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

      1. 10/27/21: no update, just wait for final CLA approval to setup repos

    2. Requirements Software Architecture Committee 

      1. Update on 11/24/21: 

        1.  @Former user (Deleted) use case for F release - (1) APP package CRD descriptor (link with WG10), implement a pre-spec of this. (2) Slice use case will also continue for F release. The complition of O2 will be for F release.

    3. OSC lab

      1. Update on 11/24/21 @Former user (Deleted) :

        1. Lab is now running, all equipements are there, cables have been delivered last week. Next week, if we can get all PTP running, then the work can continue.

        2. For the Slicing UCs we need some of this preliminary work, but december seems to be short. 

        3. O2 pre-spec implementation is available (@James Li), tests could be scheduled on december - E release. @Bin Yang wanted a server that he can stand up in the OC lab to do this O2 validation. @Jackie Huang An email was send with hardware requirements.

        4. @James Liis documented on the wiki that's going on with the New Jersey lab, the Taiwan lab and also I think CMCC want to send that set up a lab in the West Coast.

      2. Update on 12/01/21:

        1. E2E slicing use-case cannot be executed fully but we are progressing. Should be functional in F release.

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

      1. @James Li Integration and Testing (INT)

      2. @Mahesh Jethanandani Service Management and Orchestration (SMO)

        1. Feature commits are complete. Working on documentation. We should be ready.

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

        1. Finishing documentation. Branching will happen in couple of days. Will check license scan results. 

      4. @Sunil Kumar RIC Applications (RICAPP)

        1. Matti: All code is committed. Documentation should be ready by next Wednesday.

      5. @Thoralf Czichy RIC Platform (RIC)

        1. All the container images were created, tested the basic things. We plena demo on Dec 21st that also partially documents the release.

      6. (TBD) O-RAN Centralized Unit (OCU) 

      7. @Former user (Deleted)  O-RAN Distributed Unit High (ODUHIGH)

        1. Started documentation. Waiting for feedback on O1 integration and then we can branch.

        2. Action Point: @Former user (Deleted) to check that ODULOW binary is compatible with E release.

      8. @Zhimin Yuan (Deactivated) O-RAN Distributed Unit Low (ODULOW)

      9. @Martin Skorupski Operations and Maintenance (OAM)

        1. Need t check scan results and then we will be ready for branching.

      10. @Alex Stancu Simulations (SIM)

        1. We are ready. Just finishing SIM usage wiki page and documentation.

      11. @Jackie Huang Infrastructure (INF)

        1. Checked license scan report and confirmed with Trishan and Jeff that no further actions are required. All the code is merged including in StarlingX. Started updating released notes and dev. guide. 

      12. @Weichen Ni Documentation (DOC)

      13. (TBD) O-RAN Radio Unit (ORU)

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

  12. Planning for Next Meeting

  13. Any Other Business (AOB)

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

2021 12 01 

Recording: zoom recording

Agenda

  1. Call for Scribe (minutes owner): @Former user (Deleted)

  2. Roll Call & Quorum Check 

    *Quorum: 50% or more of total TOC voting members unless excluded due to attendance.   

  3. Review and Agree to Minutes of Previous Meeting

    1. Decision: Minutes for November 24th TOC meeting approval: proposed by David Streibl seconded by Jinri Huang. The motion is approved

  4. Review of Today's Agenda

  5. Release Votes and Approval

  6. AAL project

    1. Action point: Trishan to check if your have to sign a new agreement for the repo if TOC decides on BSD license use. Refer to minutes of previous meeting(s) for details.

      1. Update on 11/17/21 : @Trishan de Lanerolle we can put an exception clause for introduce a new license (BSD), this will be done in coordination with WG6.

    2. Action point: Jack to present the write up about the AAL project  to have a vote.

      1. This was put on the table on 2021-07-07 meeting

      2. Jack: There is discussion ongoing in WG6 and we're still waiting for some aspects that discussion to be resolved. Some clarifications were made but until we get more information we leave this table for now

      3. No update on  12/01/21.

  7. Copyright update

    1. 11/24/21:

      1. Jack: Meeting last week for agreed on the CLA structure (not closed yet). 

    2. 12/01/21:

      1. Jinri: What is the status of defining the  process for moving eg. YANG files under SCCL license. There was also question if OSC charter needs update to reflect SCCL.

      2. Jack: I am working on writing the process description but it needs further work on streamlining of the process and automation. Only O-RAN SCP charter controlled by O-RAN will need update and there is ongoing discussion with legal team.

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

    1. 11/24/21:

      1. @Thoralf Czichynext O-RAN meeting will be virtual and probably July 2022 meeting will be face to face.

      2. Jack, Jinri and others should meet to prioritise topics for next release, time slots will be proposed for those discussions.

    2. 12/01/21:

      1. Jirni: There will be no physical O-RAN F2F meeting in Feb 21. If it happens as virtual meeting is not decided yet. 

      2. Jirni: Most of the new specs targeting November train are under review of O-RAN TSC.

      3. Jirni: There is to be confirmed plan to have 2 PRs. First one will be about plug-fest. Second one that will include OSC release E and other 2021 achievements is now planned for Jan 22.

      4. Jack: Last TOC meeting will happen on 15th Dec and then we will resume on 5th Jan.

  9. Old business and Status of Open Action 

    1. "E" Release timeline.

      1. 11/03/21: PR of E release is expected for the first days of the next year. 

      2. 11/17/21 - Jack: At this window of time the code should be principally freezing with the exception of bug fixes and functionality.

      3. 12/01/21:

        1. First security scan will be executed tomorrow 2nd Dec. Branching need to ocure after sec. scan is passed by repository but before vote that is planned for 15th Dec. Additional security scan can be executed if needed.

        2. Vote on E release will happen on 15th Dec. We need to be ready by then with branches.

    2. OSC lab in Taiwan (Prof Ray's lab):

      1. 11/24/21 : @Former user (Deleted) initial configurations (TDD specs) is ongoing. 

    3. 5G Super Blueprint status - tabled for D and E, will be re-evaluated for F release.

      1. 11/10/21: @Tracy Van Brakle 5G super blueprint is already taking advantage of the OSC initiated developments in ONAP (but not just ONAP). Jack: There are new functionalitiesthat are needed that we need to make sure that gets into the roadmap.

    4. "F" Release time:

      1. 10/27/21: Rittwik: will focus on O-Cloud usecase in F release, as well as the continuation of network slicing use case. Will reach out to PTLs to check if any more use cases. And might divide use cases between Taiwan lab and New Jersey lab.

      2. 11/03/21: Jack: please reach Rittwik and David to get early information into the planning process of F release.

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