Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

  1. The Auto Scale Out Use Case will impact each of the Projects listed on this page. We also list the requirements for each project to support the Casablanca Scaling Use Case.

Pre-requisites for Auto scaling

  1. VNF must be in Service with the VNF Orchestration Status = Active  and PROV_Status = PROV
  2. The VNF must be onboarded via SDC
    1. TOSCA model should have been distributed
  3. The VNF must be orchestrated via SO

AAI

  1. Implement and develop a new named query to get the IP Addresses that will be used to communicate to the VF-Module Instance being scaled. The named query should be generic so that it can be used for different Configuration actions
  2. Add Topic ID for VNF Controller to VNF instance information

APPC

  1. For L4-L7 VNFs, process a HealthCheck action from SO via DMaaP
  2. For L4-L7 VNFs, process a ConfigScaleOut action from SO via DMaaP.  
    1. Receive ConfigScaleOut(VNF_ID, VF_Module_ID)
  3. Retrieve the IP addresses from A&AI for the ConfigScaleOut action  
    1. Obtain Configuration information for new instance from A&AI

CLAMP

  • Ensure CLAMP has access to VF_Module_Type at design time
  • Create policies for Scaling of vDNS  
  • Create Guard policies for Auto Scale Out

DCAE

  • PAM (Are there any impacts to DCAE to get it to send Scaling data to Policy?) 

OOF

  • OOF will process Homing and license placement request from MSO.

OOF will support additional Policies for Scale Out to check the following:

  • If there is enough capacity in the region or close to the region
  • For the VNF Instance, is the license sufficient to satisfy the configuration requested

Modeling

  • Need to add Controller type to the VNF Model in SDC 

Policy 

  • Create API call to SO with VNFInstanceID and VF_Module_Type as arguments
  • Set up proper Guard Policies
  • Compare number of instances to both Min and Max values
  • Check Prov_Status = PROV


 

SDC

  1. Support a Common Controller communication i.e. common Controller architecture to process LCM actions 
    1. Model new parameters, Controller Cluster and Topic (Channel), in the TOSCA Service Model.  The Controller Cluster and Topic can be defined by geography. Note: Controller Type will Not be used in Casablanca release and going forward. The Controller Cluster  should be one of: APPC, SDNC, VF-C
    2. The Topic (Channel) will be a two (2) way communication


SDNC

  • Import Scaling changes from APPC so that all configuration changes may be done on VNFs controlled by SDNC
  • After Resource Assignment for new instance, IP Addresses need to be added to AAI 

SO

  • Create API for VID and Policy to call that will allow SO to scale a VNFC
  • Create work flow to get all needed information to Scale a VNFC
  • Call API for Homing and Licensing checks
  • Create Workflows using Workflow Designer 

VID

  • Change Manual Scaling Use Case to use the same SO API that Policy is using in Auto Scaling Use Case (Common Actor API)
  • No labels