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
- VNF
- must be in Service
- with the VNF Orchestration Status = Active
- and PROV_Status = PROV
- The VNF must be onboarded via SDC
- The VNF must be orchestrated via SO
APPC
- Receive ConfigScaleOut(VNF_ID, VF_Module_ID)
- 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
- Add Controller_Type to VNF Model. This should be one of: APPC, SDNC, VF-C???
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)