Overview
When users use CCVPN services, they usually want service providers to provide secure, fast and stable network services. In order to implement the above capabilities, the service provider usually connects the traffic to a service node such as a firewall or a load balancer. The traditional implementation is to manually adjust the policy of the device in the entire forwarding path, so the deployment is very complicated. The SFC service capability based on the CCVPN can reduce the coupling between the service and the device, so that the user does not need to perceive the underlying physical device. When the underlying physical network topology changes, the deployment and activation of the service node are not affected.
Dublin Goals
- Enhancements to Information & Data Model - Extend CCVPN IM &DM for SFC services
- SFC Activation/Configuration - enable SFC 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
Wind River, Huawei,ZTE
Scope
The Dublin version will focus on the enabling of basic features. If possible, we can also try to complete the intelligent modeling of SFC at SDC.
CCVPN DR Service (sub-)Use Case Presentations
SFC design for CCVPN
Impacts
It is envisioned that the CCVPN SFC feature for Dublin will have impacts on the following projects: UUI, SO, A&AI, VFC and MCloud.
Project Commitments
Project | PTL | Commitment | Notes |
---|---|---|---|
UUI | NA | Support DR Service properties | |
SO | NA | Need to support DR priorities | |
A&AI | NA | Support DR Service properties | |
VFC | NA | Implement parameters passed for SFC enabling and disabling | |
MCloud | NA | AZ capability collection DR capability discovery and enablement |