Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

CCVPN includes across-domain network service provisions and operations. Where, across-domain disaster recovery is one of the important feature to provide with rising up of multiple connection and Cloud computing technologies.  DR feature will cooperate private and public Cloud to provide fine granularity recovery management for network services. 

Dublin Goals

  1. Enhancements to Information & Data Model - Extend CCVPN IM &DM for DR services
  2. Enhancements to DR compliant validation when on-boarding - Extend the existing validation for lifetime compliance validation
  3. DR Activation/Configuration -  enable DR awareness when provisioning and operations a NS
  4. Direct Service Recovering - Implementation of DR service across domains to provide fine granularity management during the elapse time
  5. Recovering Status Notification - Notify to service administrators that the Service has been recovering or progress in the service bus
  6. Smart workload balancing - smart optimization and selection when recovering for connection reliability and efficiency

  7. Future Releases (El Alto and beyond)
    1. Intent programming
    2. Predicability based optimization

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 Meetings

For 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 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. 

Project Commitments


ProjectPTLCommitmentNotes
A&AI

Status
colourGrey
titleNA
 

Support Composite Service Instances (multi-operator)

SDC
Status
colourGrey
titleNA
  • Support Composite Services creation
  • Must be able to model LCM operations/Interfaces and expose the modification capabilities through the Service Catalog

    DR Service properties

    DCAE

    Status
    colourGrey
    titleNA

    Performance management - Stretched GOALStatus and progress collection and analysis

    Modeling

     

    Status
    titleNA

    Need to support Composite Services

    External APIMatthieu Geerebaert

    DR priorities

    VFC

     

    Status
    colourGrey
    titleNA

    Implement

    TMF 641 for external BSS Portal (

    parameters passed

    as one composite/single orerItem)
  • implement East-West cross-operator  External API-External API ("patch service" for service modification)
  • SOSeshu Kumar Mudiganti

    for DR enabling and disabling

    MCloud

     

    Status
    colourGrey
    titleNA

  • Implement ability to "decompose" the End-to-End service (in collaboration with SDC). The same applies for the Service Change. 
  • Implement Service Modification API and associated workflows to interact with other projects (SDN-C, A&AI & ExtAPI)

    AZ capability collection

    DR capability discovery

    OOF/SDN-C

    Status
    colourGrey
    titleNA

    AZ aware placement for reliability consideration