Versions Compared

Key

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

Overview

CCVPN in Casablanca release included the creation of Point-to-Point connectivity services (e.g., E-Line). The CCVPN Use Case extension for Dublin should include MultiPoint-to-MultiPoint connectivity Service Creation and Modification. This sub-use case extension makes use of the concepts of Unified and Composite Services as depicted in the attached presentation.

From an Operator perspective, it is important to introduce the capability to manage the performance of the CCVPN End-to-End E-LAN service in order to guarantee the adherence to the agreed SLS.

Dublin Goals

Auto Scale Out - Provide a Closed Loop Response to high demand within a VNF.   StatuscolourGreentitleCommitted
  1. Primary impacts will be: Policy, CLAMP, SDC, SO
Enhancements to Manual Scale Out (from Beijing Release)   StatuscolourGreentitleCommitted
  1. Healthcheck fix - ()
  2.  ConfigScaleOut() - Controller should attain configuration information from AAI instead of SO (APPC, SDNC, SO)
  3. SDNC Resource Assignment - IP Address of new instance needs to be added to AAI (SDNC)
  4. SDNC needs to import all Beijing capability (SDNC)
  • Controller Type - In Beijing, the operator had to manually select the controller type (SDNC or APPC) within VID.  The controller type should be part of the VNF model and not a run time option.  ONAP components should be able to look within the VNF model to determine which controller to use for a particular VNF. Primary impacts: SDC, Modeling, VID
  • Homing and Capacity- When new instances are requested ONAP should do a check to determine placement and license availability.  This feature was descoped in Beijing.  Primary impacts will be: SO, OOF, SDNC and SDC
  • Future Release
    1. Scale In (Auto and Manual) - This feature will complete the scaling capabilities for VNFs and will requirem a command to drain and move traffic from an existing instanceso that it can be removed from the pool of active instances.  Primary impacts should be: AOOC, SDNC, SO, Policy, CLAMP, VID, SDC
    2. TOSCA Capabilities - Manual Scale Out in Beijing only allowed scaling of HEAT based VNFs.  As the TOSCA model becomes more mature within ONAP we will need to enable scaling for TOSCA based VNFs
    1. Enhancements to Information & Data Model - Extend CCVPN IM &DM for Composite Services
    2. Service Order & Activation/Configuration -  NorthBound API extension to include Composite Services (extension from Casablanca)
    3. Direct Service Modification - Implementation of Change service API following what proposed in Introduction an API at ‘service’ level.pptx. E.g., Inter-Carrier change bandwidth /elastic bandwidth  for E-LAN (Access E-line, Access E-LAN)
    4. Service Catalog Notification - Notify to partner SP that the Service has been created in the Service Catalog
    5. Performance Monitoring modelling in Service Catalog - Model SOAM in Service Catalog for   E-LAN (Access E-line, Access E-LAN)

    6. Future Releases (El Alto and beyond)
      1. Managed Access E-LINE Services (as per MEF 62)
      2. Automatic import/export of TOSCA csar in other provider’s Service Catalog (SDC)

      3. Service characteristics visibility in Service Inventory (A&AI)

    Business Requirement

    E-LAN Services are used by Operators to connect different Customers (especially Enterprise Customers). For example, multiple Cloud Consumers can be connected to one or more CSP Technology Centers. This service could also be used to deliver Public Cloud services or enable secure (encrypted) connectivity to Private Clouds

    Business Requirement

    Dynamic scaling gives an operator the tools it needs to maximize efficiency of the resources dedicated to the cloud. ONAP's control environment allows it to assign resources where they are most needed and reallocate them when they are needed by different VNF.  This allows the cloud environment to achieve a much higher resource utilization level than the old data centers it is replacing

    Participating Companies

    Vodafone

    Scope

    Dublin release will focus on Auto Scale OutMP2MP Service Creation and Modification.  If possible we may attempt to complete Scale In also.  Manual Scale Out was completed in Beijing.Performance Monitoring modeling as well. 

    CCVPN E-LAN Service (sub-)Use Case Presentations

    Use Case Subcommittee December 5th, 2018

    External API Subcommittee February 13th, 2019

    CCVPN E-LAN Service Use Case Team Meetings

    For Dublin we will be using the weekly CCVPN call Use Case Extension calls to progress the CCVPN E-LAN Service (sub-)Use Case.

    Meeting Logistics

    Weekly Scaling Meeting

    Day: TBD

    Meeting Minutes 


    Impacts

    The Auto Scale Out Use Case for Casablanca It is envisioned that the CCVPN E-LAN Service (sub-)Use Case for Dublin will have impacts on the following projects:  Policy  External API, CLAMPSDC,  SOSO,  OOF, APPC, SDNC, SDC, and VIDA&AI, DCAE.

    The modeling sub-committee will be engaged for the definition of the IM & DM.

    Please see the Impacts page for page for a more detailed list of requirements in each project. 

    Project Commitments


    ProjectPTLCommitmentNotes
    AAI
    A&AI

    Status
    colour

    Green

    Grey
    title

    Committed

    NA
     

    APPCRanda Maher

    Support Composite Service Instances (multi-operator)

    SDC

    Status
    colour

    Green

    Grey
    title

    Committed No commitment for Controller_Type since the requirements are still unknownCLAMPGervais-Martial Ngueko

    NA

    1. Support Composite Services creation
    2. Must be able to model LCM operations/Interfaces and expose the modification capabilities through the Service Catalog
    DCAE

    Status
    colour

    Green Modeling 

    Yellow
    title

    Committed

     Risks:

    1. "VF_Module_ID" to be confirmed as input for operational Policy
    2. API and content for new policy interaction to create new top of Operational Policy (Guard Policy) might end up more costly than anticipated 

    r5

    Performance management - Stretched GOAL (postponed to El Alto)

    Modeling

     

    Status
    titleNA

     No Requirements at this time OOF Sarat Puthenpura

    Need to support Composite Services

    External APIMatthieu Geerebaert

     

    Status
    colour

    Yellow

    Grey
    title

    Partial Can only support R2 functionality Policy Pamela Dragosh

    NA

    1. Implement TMF 641 for external BSS Portal (parameters passed as one composite/single orerItem)
    2. implement East-West cross-operator  External API-External API ("patch service" for service modification)
    SO

     

    Status
    colour

    Green

    Grey
    title

    Committed Add Risks from Pam

    NA

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

    Status
    colourGrey
    titleNA

    TBR
    SDN-CDan Timoney

     SDC

     

    Status
    titleNA

    No Requirements at this time SDNC  StatuscolourGreentitleCommitted SO 

    Status
    colour

    Green

    Grey
    title

    Committed VID

    NA

    TBR
      StatuscolourGreentitleCommitted