| |
|
Project: ONAP - Track w/Link | 1-2 Key Points | Challenges |
---|
2022-01-12 - ONAP: Stability, Resiliency and Stress tests | - Overview of stability and resiliency tests since Guilin
|
|
2022-01-11 - ONAP: Database Upgrade and Rollback in Policy Framework | - Overview of new upgrade/rollback functionality / Demo
|
|
2022-01-12 - ONAP: Deutsche Telekom Portal presentation - LF Networking - LF Networking Confluence | - Presentation of DT's ONAP based "TNAP" portal architecture.
- Midterm plan to contribute the portal code to the community (not yet decided and scheduled)
- Real Demo!
|
|
2022-01-12 - ONAP: Unmaintained code handling and its impact on documentation | - Explanation of the documentation changes planned for "Jakarta" release, the reasons for them and current activities to fix the root cause of the problem (management of unmaintained code).
- Good discussion; request from Amy Zwarico to Kenny Paul to check how unmaintained code and dependencies are managed in the Linux Operating System
|
|
2022-01-12 - ONAP: How DT deploys ONAP with the help of Argo CD | - Argo CD helps us, doing GitOPs in the "TNAP" project and install ONAP and TNAP components.
- Real Demo!
|
|
|
|
|
Project: ODL - Track w/Link | 1-2 Key Points | Challenges |
2022-01-12 - ODL: T-API contribution to T-PCE | - Overview of Open and Disaggregated Transport Networks
- Introduction to ONF T-API YANG models
- Explanation on Nokia contribution to tapi NBI of ODL/TransportPCE:
- T-API topology service
- T-API connectivity service
- T-API notification service
- Demo showing the creation of an OTN 10GB service using T-API interface
|
|
2022-01-12 - ODL: Planned extension of T-API module and integration of OpenConfig device models in T-PCE | - Nokia's view in open multi-domain & multi-device YANG data model optical networks
- On going development to extend ODL/TransportPCE capabilities, and make it more agnostic to handle brownfield equipment:
- External PCE based on T-API topology aided by ML application to select the optimal configuration parameters of the devices across the computed path
- Introduction of OpenConfig device data models, to support multi-device data model networks
- Integration of OpenConfig Renderer to provision OpenConfig based optical devices
- Creation of an E2E network services across a multi device data model network
- Great discussion with Olivier Renaisabout the release of this contribution and some technical aspects about the implementation
| - Conversations needed in order to position the proposed extended optical SDN controller in the Transport Slice use case of ONAP
|
|
|
|
|
|
|
Project Anuket- Track w/ Link | 1-2 Key Points | Challenges |
2022-01-12 - Anuket: DevIntOps -- Agile Delivery of NFV | 1, Promoting more close collaboration between vendors and operator by continuous integration multiple vendor products, continuous testing, continuous optimizing. 2, Promoting Pre-integration and Pre-deployment before production deploy, will help improve the quality and save time. | 1, Openstack deploy could be very complex, hard to fully automate deploy and upgrade 2, Not easy to define which vendor should be responsible for the defect, suggesting apply RC testing. |
2022-01-12 - Anuket: Anuket Assured - How can we deliver on the Anuket Value Proposition for Cloud Infrastructure and Cloud Native Workloads? | Overview of AAP Discussions from Operators and vendors | 1) Develop a community Strategy
|
RC2 |
|
|
Project EMCO- Track w/ Link | 1-2 Key Points | Challenges |
|
|
|
|
|
|
|
|
|
Project Tungsten Fabric- Track w/ Link | 1-2 Key Points | Challenges |
|
|
|
Project 5G Super Blueprint w/ Link (Cross-community with EMCO) | 1-2 key Points | Challenges |
5G Super Blueprint: Realizing Multiple Network Slices & MEC Apps in each Slice with LFN/LFE/CNCF Projects | - Discussed evolution of Network slicing; current and future capabilities.
- Demo of EMCO orchestration of slices & MEC applications
| Planning for 2022 in regards to:- Automation needs.
- Performance isolation needs
- Security isolation needs
- Type of observability & closed loop actions needed to maintain SLAs even when there are noisy neighbors.
|