...
- Description: Let's close the gaps from design to runtime for supporting current and future control loops.
- Topic Leader: Pam Dragosh
- Volunteer Note Taker: First Last email
- Estimated Duration: 2h
Link to data Source (if applicable)
Workshop Title: ONAP Multi Cloud Architectural vision for R2 and beyond
Goal: Advance Multi Cloud beyond the current proxy implementation to address ONAP platform level issues across all use cases
Moderator: VMware
Primary Contact: Ramki Krishnan, VMware, ramkik@vmware.com
Topic 1: Standardized Infrastructure and Application class statistics Model
Description: This session will focus on a hierarchical cloud-platform-aware architectural framework with separation of collection, storage, processing functions and real-time vs historical analytics components. In this framework, Multi Cloud will deliver a standardized infrastructure and application class statistics model for driving ONAP component/VNF placement/change management across distributed DC multi cloud instances through ONAP-OF, DCAE and other components. The benefit to ONAP platform, across all use cases, will be delivering the best performance and security while minimizing cost.
Desired Audience: ONAP-OF, DCAE, A&AI, Policy, OOM, SDN-C, DMaaP, OOM
Estimated Duration: 2 hrs.
Desired Scheduling: Before Topic 4, Architecture and TSC meetings.
Discussion Lead(s): VMware, Wind River, AT&T (to confirm)
Topic 2: Towards a performance-aware and portable cloud-agnostic infrastructure
Description: Multi-vendor cloud portability and interoperability while delivering performance is a mandatory feature of distributed DC deployments. The practical challenge in achieving this goal is the lack of standardization of Platform-aware and QoS features, for example extra specs in OpenStack, which results in a vertically integrated solution. This session will focus on how Multi Cloud can offer policy standardization and translation as a microservice for platform-aware and QoS features (hard-guarantee, min-guarantee, best effort etc.) for addressing this challenge and how NFV application classes such as IMS/EPC Control/Data Plane can benefit from this framework.
Audience: VNF Requirements/Modelling, A&AI, Policy, SO, VF-C, APP-C, SDC
Estimated Duration: 2 hrs.
Desired Scheduling: Before Topic 4, Architecture and TSC meetings.
Discussion Leads(s): Wind River, ?
Topic 3: Architectural options for Multi-vendor SDN Controller and Multi Cloud Deployments in a DC
Description: Multi-vendor components in a DC including underlay, overlay, gateway and SDN Controllers for the same pose various architectural challenges in terms interoperability, security etc. This session will focus on an in depth analysis of the architectural options including related efforts such as OpenStack Gluon, in-band OAM features for latency sensitive applications such as VoLTE and suggest deployment options for various releases. This proposal also addresses communication latency-bound multi-side physical DCs which can be treated as a single virtual DC for management purposes.
Desired Audience: SDN-C, SO, VF-C, APP-C, SDC
Estimated Duration: 2 hrs.
Desired Scheduling: Before Topic 4, Architecture and TSC meetings.
Discussion Leads(s): Huawei, AT&T (to confirm)
Topic 4: Multi-Cloud Architectural vision Summary and Next Steps
Description: This session will focus on summarizing the discussion on the aforementioned three topics and define concrete next steps towards making progress for R2 and beyond for Multi Cloud and other relevant ONAP component capabilities. For convenience, the aforementioned three topics are listed below
- Standardized Infrastructure and Application class statistics Model
- Towards a performance-aware and portable cloud-native infrastructure
- Architectural options for Multi-vendor SDN Controller and Multi Cloud Deployments in a DC
Audience: All PTLs
Estimated Duration: 2 hrs.
Scheduling: After topics 1, 2 and 3 and before Architecture and TSC meetings.
Discussion Leads: VMware, Wind River, AT&T