| Project: ONAP - Track w/Link | 1-2 Key Points | Challenges |
|---|
| 2022-01-11 - ONAP: CDS Error Handling in Production deployments | - Handling various error scenarios in real life production deployment of CDS.
- Real Demo
|
|
| 2022-01-11 - ONAP: Disaster management for ONAP | - To backup and restore Kubernetes cluster resources and persistent volumes.
- Real Demo
|
|
| 2022-01-11 - ONAP: 2022 TSC priorities and Action Plan | - Review 2022 ONAP priorities and collect feedback
- Next Steps:
- Kick Off Offline vote with the ONAP TSC
- Define an action plan on 1/20
|
|
| 2022-01-11 - ONAP TSC Task Force: ONAP For Enterprise Business | - Share the latest updates about ONAP For Enterprise Business Roadmap, accomplissments and current activities.
| Call for Enterprise Use Cases |
| 2022-01-11 - ONAP: Release Process Review and Istanbul Retrospective | - Reviewed changes to release process approved by TSC last spring and rolled out in Istanbul. General agreement that changes were useful.
- Reviewed Istanbul lessons learned and discussed actions for each item. Ran out of time for the last few items, so we will plan time during the PTL meeting to finish up.
| - Architecture Reviews - Increase # reviews prior M2?
- Last Minute Requirements prior M2 (Specification Freeze)
|
| 2022-01-11 - ONAP: CNF Orchestration Tutorial | - Overview of existing and new functionalities / Demo
|
|
| 2022-01-11 - ONAP: Code quality demo | - Integrate SonarCloud during review process instead of daily runs
|
|
| 2022-01-11 - ONAP Security: Jakarta Global Requirements and Best Practices | - ONAP Security Requirements (Initiatives, Best Practices and Global Requirements)
- Deep Dive: Logging architecture leveraging open-source logging framework
|
|
| 2022-01-11 - ONAP: CM notification handling in SDN-R demo and tutorial | - Presentation of new functionality available to receive and store CM notifications
- Demo
|
|
| 2022-01-11 - ONAP: TOSCA Defined Control Loop Lifecycle Management Demo | - Presentation and demo on TOSCA defined control loop Life Cycle Management
- WOrking demo of control loop commissioning/creation/instantiation/removal performed
|
|
| 2022-01-11 - ONAP: Joint SDO Modeling Workshop | - Presentation from Lukasz on the K8S resource model (A&AI runtime model) used in CNF orchestration use case
- Presentation from Joerg on the latest progress of ETSI NFV on container modeling (VNFD) and reference point (NFVO-VNFM)
- Presentation from Alex and Jack on topology model from O-RAN and MEF perspective
|
|
| Project: ODL - Track w/Link | 1-2 Key Points | Challenges |
| 2022-01-11 - ODL: Overview of TransportPCE feature | - General presentation of odl-transportpce feature
- Reviewed main functionalities available on Phosphorus release, and those planned for next releases.
- Live demo with an example of one connectivity service available: 10GE service over OTN/WDM optical Transport Network
|
|
| 2022-01-11 - ODL: open talk about the current release process | - Q&A session about the history of the release process, MRI/MSI + self-managed/managed projects. Relevancy of this project today. Limits of Autorelease process today.
- documentation generation issues with RTD and automation
- release rebranding roll-out
| - How to improve current release process automation and face the coming migration to pipelines / blue ocean?
|
|
|
|
| Project Anuket- Track w/ Link | 1-2 Key Points | Challenges |
| 2022-01-11 - Anuket: Hybrid Multi-Cloud Infrastructure | - Reviewed the essential problem statement of Telcos wanting to leverage cloud infrastructure and capabilities but needing the flexibility, choice to be able to support multiple cloud environments
- Support public, private and hybrid
- Consensus that many solution providers were seeking to create Single Pane of Glass management solutions but without some common requirements, specifications and perhaps APIs, this could lead to more chaos
- Consensus that it seem to be appropriate for ANuket to consider adding requirements in this area.
- Bob Monkman also suggested collaboration with EMCO, which is a multi cluster orchestration sister project in LFN, could be beneficial in conjunction with such specification work.
| Conversations needed with EMCO and ONAP communities on how to handle multi-cloud |
| 2022-01-11 - Anuket: Lakelse Retrospective | - Reviewed history of Lakelse release, including milestone tasks and work products
- Value of RA review is questionable, as done for Lakelse. Need input from telcos on testing needs to help drive requirements definition.
- Need to define release criteria for RI. Do all tests need to pass? Suggestion: let's use performance of RI in Lakelse as a baseline for future releases.
- May need additional information for software release page on website, particularly regarding RA dependency for RC and RI specifications.
| - Insufficient input from telcos on testing needs
- Need to integrate other test/performance projects into common CI chain
|
| 2022-01-11-Anuket: RA-1 What's next | - Status of Lakelse release Reference Architecture 1
- Acceleration: further work on Cyborg if we can identify use cases requirements
- Edge: discussion on deployments based on OpenStack
- Hybrid and multi-cloud: to be addressed in interaction with the Reference Model. It is an orchestration topic, cross-community topic
|
|
| Project EMCO- Track w/ Link | 1-2 Key Points | Challenges |
| 2022-01-11 - EMCO: Project overview and Architecture | - Went over EMCO architecture, deeper dive of EMCO features and Open APIs
- Went through a Demo and some slides on a vFW Use Case
- Noted that Anuket is now considering defining some requirements around Telco multi cloud support for customers, which would benefit potentially from EMCO capabilities and so this project can connect with Anuket representatives to discuss collaboration.
|
|
| 2022-01-11 - EMCO: Hands-on experience with demo application. | - Excellent real world test case with the Huawei team who used an earlier version of EMCO to deploy and manage an internal application
- Gave a good indication of how to apply EMCO, ease of use considerations for the team, and possible some contributions back to the project.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
