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

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
   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)
   (extension from Casablanca)
3. Direct Service Modification - Implementation of 'Change service’ API. E.g., Inter-Carrier change bandwidth /elastic bandwidth  for E-LAN (Access E-line, Access E-LAN)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
4. 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
5. 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

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 Out.  If possible we may attempt to complete Scale In also.  Manual Scale Out was completed in Beijing.

CCVPN E-LAN Service Use Case Presentations

Use Case Subcommittee December 5th, 2018

CCVPN E-LAN Service Use Case Team Meetings

For Dublin we will be using the weekly CCVPN call to progress the CCVPN E-LAN Service Use Case.

Meeting Logistics

Weekly Scaling Meeting

Day: TBD

Meeting Minutes 

Impacts

The Auto Scale Out Use Case for Casablanca will have impacts on the following projects:  Policy, CLAMP, SO, OOF, APPC, SDNC, SDC, and VID

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

Project Commitments