1. Scaling Use Case
Proposal

2. Scaling Use Cases Beijing Casablanca Scale Out Scale In Manual Scaling
(In Progress)
Casablanca
(Stretch Goal)
Manual Scaling
Scale In Complexities
Must not impact service
Drain/Migrate existing traffic
Transfer state of old instance
May need to create VNF state machine and state transitions (Idle/Active)
Automatic Scaling

3. Casablanca Scaling Features
Auto Scale Out – This is the highlight feature for Casablanca and will provide a closed loop response to high demand within a VNF. The primary impacts will be Policy, CLAMP, and APPC
Homing and Licensing – When new instances are requested we should do a check to determine placement and license availability. This feature was descoped from Beijing. The primary impacts will be SO, OOF, SDNC, and SDC
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.
Stretch Goals
Scale In (Auto and Manual) – This feature will complete the scaling capabilities for VNFs, and will require a command to drain and move traffic from an existing instance so that it can be removed from the pool of active instances. More work needs to be done to define the requirements for this feature. Primary impacts should be APPC, SDNC, SO, Policy CLAMP, VID, SDC.
TOSCA capabilities – Manual Scale Out in Beijing only allowed scaling of HEAT based VNFs. As the TOSCA model becomes more developed we will need to enable scaling for TOSCA based VNFs.

4. Auto Scale Out Work Flow
VNFC
VNFC
VNFC
APPC
SDNC
DMaaP SO
VID
Policy
DCAE
Telemetry Data
Scaling Data
Scaling Event
Scaling Request
Healthcheck
Healthcheck
Homing, Licensing, Capacity checks
Healthcheck
Create new instance
Existing VNF(C)
New VNFC
ConfigScaleOut()
ConfigScaleOut()
Configure new instance
Telemetry Data
Healthcheck
Healthcheck
Healthcheck

5. Homing and License Flow Diagram