Scaling Use Case Proposal Scaling Use Cases Manual

Scaling Use Case Proposal

Scaling Use Cases Manual Scaling Automatic Scaling Scale Out Scale In Beijing Casablanca (In Progress) (Stretch Goal) 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)

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, SDC • 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. Impacts: SDC • 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.

Auto Scale Out Work Flow VNFC APPC SDNC DMaa. P VID SO Policy DCAE Telemetry Data Option A Scaling Data Scaling Event Scaling Request New VNFC Option B Existing VNF(C) Telemetry Data Scaling Event (Complex Request) Option C (Preferred) Telemetry Data Scaling Event (VNFInstance. Id, VF_Module) 4

Auto Scale Out Work Flow APPC SDNC VNFC SO DMaa. P VID Policy DCAE Option C (Preferred) Telemetry Data Scaling Event (VNFInstance. Id, VF_Module Type) Healthcheck New VNFC Existing VNF(C) Healthcheck Create new instance Homing, Licensing, Capacity checks Config. Scale. Out() Configure new instance Config. Scale. Out() Telemetry Data Healthcheck 5

What needs to be done? • What triggers a Scaling Event? • What component sends SO the Scaling Request? • The Scaling Request should use the same API as VID uses for manual Scaling? ? ? • What Data is in the Scaling Request? • See separate slide • What does a Scaling Policy look like? • “If [threshold] then scale [vf_module]”? • “If [threshold] then scale [VNFC/VM_TYPE]”? • …

VID -> SO Scaling Request { "request. Details": { "model. Info": { "model. Type": "vf. Module", "model. Invariant. Id": "ff 5256 d 2 -5 a 33 -55 df-13 ab-12 abad 84 e 7 ff", "model. Version. Id": "fe 6478 e 5 -ea 33 -3346 -ac 12 -ab 121484 a 3 fe", "model. Customization. Id": "856 f 9806 -b 01 a-11 e 6 -80 f 5 -76304 dec 7 eb 7", "model. Name": "v. SAMP 12. . base. . module-0", "model. Version": "1" }, "cloud. Configuration": { "lcp. Cloud. Region. Id": "xyz 1", "tenant. Id": "88 a 6 ca 3 ee 0394 ade 9403 f 075 db 23167 e" }, "request. Info": { "instance. Name": "MSOTEST 103 a-v. SAMP 12_base_module-0", "source": "VID", "suppress. Rollback": true, "requestor. Id": "az 2016" }, "related. Instance. List": [ { "related. Instance": { "instance. Id": "17 ef 4658 -bd 1 f-4 ef 0 -9 ca 0 -ea 76 e 2 bf 122 c", "instance. Name": "MSOTESTVOL 103 a-v. SAMP 12_base_module-0_vol", "model. Info": { "model. Type": "volume. Group" } }, { "related. Instance": { "instance. Id": "{service. Instance. Id}", "model. Info": { "model. Type": "service" "model. Invariant. Id": "ff 3514 e 3 -5 a 33 -55 df-13 ab-12 abad 84 e 7 ff", "model. Version. Id": "fe 6985 cd-ea 33 -3346 -ac 12 -ab 121484 a 3 fe", "model. Name": "{parent service model name}", "model. Version": "1. 0" } }, { "related. Instance": { "instance. Id": "{vnf. Instance. Id}", "model. Info": { "model. Type": "vnf", "model. Invariant. Id": "ff 5256 d 1 -5 a 33 -55 df-13 ab-12 abad 84 e 7 ff", "model. Version. Id": "fe 6478 e 4 -ea 33 -3346 -ac 12 -ab 121484 a 3 fe", "model. Name": "v. SAMP 12", "model. Version": "1. 0", "model. Customization. Name": "v. SAMP 12 1", "model. Customization. Id": "a 7 f 1 d 08 e-b 02 d-11 e 6 -80 f 5 -76304 dec 7 eb 7" } } ], "request. Parameters": { "controller. Type": "appc", "user. Params": [] } } }

Homing and License Flow Diagram