Overview
CCVPN includes across-domain network service provisions provisioning and operationsoperation. Where, across-domain disaster recovery is one of the important feature to provide with rising up of multiple connection access and Cloud computing technologies. DR feature will cooperate private and public Cloud to provide fine granularity recovery management for network services.
Dublin Goals
- Enhancements to Information & Data Model - Extend CCVPN IM &DM for DR services
- Enhancements to DR compliant validation when on-boarding - Extend the existing validation for lifetime compliance validation
- DR Activation/Configuration - enable DR awareness when provisioning and operations a NS
- Direct Service Recovering - Implementation of DR service across domains to provide fine granularity management during the elapse time
- Recovering Status Notification - Notify to service administrators that the Service has been recovering or progress in the service bus
Smart workload balancing - smart optimization and selection when recovering for connection reliability and efficiency
- Future Releases (El Alto and beyond)
- Intent programming based trigger and receiver
- Predicability based optimization
- VPN as a service
Business Requirement
DR Services are used by Operators to connect different Cloud for DR usage. For example, multiple Cloud Consumers can connect with different Clouds for replication/recovery between different domains/sites.
Participating Companies
VMware
Scope
Dublin release will focus on enabling of basic functions. If possible we may attempt to complete smart optimzaition modeling as well.
CCVPN DR Service (sub-)Use Case Presentations
DR design for CCVPN CCVPN
E-LAN Service Use Case Team MeetingsFor Dublin we will be using the weekly CCVPN Use Case Extension calls to progress the CCVPN DR Service (sub-)Use Case.Meeting Logistics
Weekly Scrum Meeting
Day: TBD
Meeting Minutes
Impacts
It is envisioned that the CCVPN E-LAN Service (sub-)Use Case DR feature for Dublin will have impacts on the following projects: External API, SDC, SO, A&AI, DCAE.
The modeling sub-committee will be engaged for the definition of the IM & DM.
Please see the Impacts page for a more detailed list of requirements in each project. , Modeling, MCloud, OOF and VNFSDK
Project Commitments
| Project | PTL | Commitment | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| A&AI |
colour | Grey | title | NA | | Support Composite Service Instances (multi-operator) | SDC | ||||
| Status | |||||||||||
| colour | Grey | ||||||||||
| title | NA | DR Service properties | |||||||||
| DCAE | Performance management - Stretched GOAL | yes | Long-run task status and progress collection and analysis | ||||||||
| Modeling |
| next release | Need to support Composite Services | External API | Matthieu Geerebaert | ||||||
| Status | |||||||||||
| colour | Grey | ||||||||||
| title | NA |
| SO | ||||||||
| Status | |||||||||||
| colour | Grey | ||||||||||
| title | NA |
| OOF/SDN-C | | Status | | ||||||
| colour | Grey | ||||||||||
| title | NA | ||||||||||
| VFC | yes | Implement parameters passed for DR enabling and disabling | |||||||||
| VNFSDK | victor gao | yes | Enable DR compliance detection during lifecycle validation | ||||||||
| MCloud | yes | AZ capability collection DR capability discovery and enablement | |||||||||