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.
Leftovers from Beijing
- Homing and Licensing Request to OOF
- HealthCheck needs to be fixed
- How to get configuration information to APPC/SDNC
- SDNC needs to add IP Address information to AAI
Scaling Impacts
Pre-requisites for Auto scaling
- VNF must be in Service with the VNF Orchestration Status = Active and PROV_Status = PROV
- The VNF must be onboarded via SDC
- TOSCA model should have been distributed
- The VNF must be orchestrated via SO
AAI
- (This requirement is no longer needed) Implement and develop a new custom query to get the IP Addresses that will be used to communicate to the VF-Module Instance being scaled. The custom query should be generic so it can be used for different configuration actions
APPC
- (Provided in Beijing) For L4-L7 VNFs, process a HealthCheck action from SO via DMaaP
- (Provided in Beijing) For L4-L7 VNFs, process a ConfigScaleOut action from SO via DMaaP.
- Receive ConfigScaleOut(VNF_ID, VF_Module_ID)
- (This requirement is no longer needed) Retrieve the IP addresses from A&AI for the ConfigScaleOut action
- Obtain Configuration information for new instance from A&AI
APPC
CLAMP
- Ensure CLAMP has access to VF_Module_Type at Name at design time
- Create policies Create Threshold Crossing Alert (TCA) policies for Scaling of vDNS
- Create Guard policies for Auto Scale Out
DCAE
Test Support Only
OOF (Not Pursing in R3)
- OOF will process Homing and license capacity 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 (Not Required)
- 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
- Add Controller_Type to VNF Model. This should be one of: APPC, SDNC, VF-C???
- ** CURRENTLY, NO REQUIREMENTS
SDNC
- For L1-3 VNFs, process a HealthCheck action from SO via DMaaP
- Import Scaling changes from APPC so that all configuration changes may be done on VNFs controlled by SDNC
- Retrieve the IP addresses from A&AI for the ConfigScaleOut action
- Obtain Configuration information for new instance from A&AI
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 checksCreate Workflows using Workflow Designer capacity checks (Moved to Dublin)
VID
- Change Manual Scaling Use Case to use the same SO API that Policy is using in Auto Scaling Use Case (Common Actor API)