Impacts (Scale In Use Case)

Owned by Scott Blandford
Last updated: Jan 29, 2019
3 min read

This page will document the impacts for each goal within the Scale In Use Case

Bold items have been approved for Dublin

Italicized items have been pushed to a future release

Goal: Improvement of Control Loop

This is the primary focus of the Scaling Use Case in Dublin.  The Control Loop Requirements can be found on the Dublin Control Loop Impacts wiki page. 

Goal: Further Automation of Scaling Use Case

CLAMP (Stretch Goals)

  • Dummy VF Module elimination (Tech Mahindra) 

  • Operational Policy GUI simplification (Tech Mahindra)

Policy (Stretch Goals)

  • Dummy VF_Module elimination (Tech Mahindra) 

  • Naming Policy changes



Goal: Manual and Automatic Scale In

APPC

  • ConfigScaleIn (Priority: 1)

    • APPC will support a new LCM action ConfigScaleIn

    • APPC will need to support accepting a new ConfigScaleIn request from MSO

    • APPC will accept the payload sent from MSO. Included in the request will be the VF Module ID to be removed.

    • APPC will send the ConfigScaleOut request to the VNF via REST API

  • Pre Action Phase (Priority: 3) 

    • Need to decide what tasks we will execute in this phase so that we can write the requirements "How"

  • Post Action Phase (Priority: 3)

    • Need to decide what tasks we will execute in this phase so that we can write the requirements "How"

  • Distribute_Traffic (Priority: 1)

    • APPC will accept and process a DistributeTraffic request from MSO via DMaaP

    • DistributeTraffic action will be enhanced to specify a VM as the target

  • Quiesce_traffic for VNFCs (Priority: 1)

  •  

    • APPC will accept and process a QuiesceTraffic request from MSO via DMaaP

  •  

    • QuiesceTraffic action will be enhanced to specify a VM as the target

CLAMP

  • Scale In Closed Loop (Priority: 2)

  • Guard Policies (Priority: 2)

DCAE

  • Scale In Trigger (Priority: 2)

    • Support creating a Threshold Alert (TA) when capacity needs to be reduced

    • Send the TA to Policy 

OOF

  • Scale In Target (Priority: 2) Policy

  • Scale In Policy (Priority: 2)

    • Support sending Operational Policy request via DMaaP to SO

    • Create Operational Policy for a Scale In Request

  • Guard Policies (Priority: 2)

    • Accept Guard Policy from CLAMP for Scale In operations.  

SDC

  • Import Scaling Building Blocks to Catalog  (Priority: 3)

    • Add Scale In Building Block to SDC Catalog

    • Add any new BB (TBD based on finalized Scale In flow) to the Catalog

  • ability to build scaling workflows (Priority: 3)



SDNC



  • ConfigScaleIn (Priority: 1)

    • SDNC will support a new LCM action ConfigScaleIn

    • SDNC will need to support accepting a new ConfigScaleIn request from MSO

    • SDNC will accept the payload sent from MSO. Included in the request will be the VF Module ID to be removed.

    • APPC will send the ConfigScaleOut request to the VNF via REST API

  • Pre Action Phase (Priority: 3)

    • Need to decide what tasks we will execute in this phase so that we can write the requirements "How"

  • Post Action Phase (Priority: 3)

    • Need to decide what tasks we will execute in this phase so that we can write the requirements "How"

  • Distribute_Traffic (Priority: 1)

    • SDNC will accept and process a DistributeTraffic request from MSO via DMaaP

    • DistributeTraffic action will be enhanced to specify a VM as the target

  • Quiesce_traffic for VNFCs (Priority: 1)

    • SDNC will accept and process a QuiesceTraffic request from MSO via DMaaP

    • QuiesceTraffic action will be enhanced to specify a VM as the target



SO

  • Scale In Workflow (Priority: 1)

    • Support a new Scale In Building Block.

    • Support a sending and receiving messages from Policy and VID via DMaaP

    • Accept a Closed Loop (Policy) or Open Loop(VID) request to Scale In a module

    • Support sending a Scale In Request to the Controller. This request will include the VF-Modules/VM(s) that will be deleted

  • Support Pre Action Phase (Priority: 3)

  • Support Post Action Phase (Priority: 3)

  • Call ConfigScaleIn API on controller (Priority: 1)

  • Call DistributeTraffic Action.   (Priority: 1)

    • Enhance the DistributeTraffic action at a VM level and send to the Controller. This assumes that the action has been implemented and tested in Casablanca release. The necessary config parameters will be passed with the request to the Controller

  • Call QuiesceTraffic  (Priority: 1)

VID

  • UI enhancements (Priority: 1)

    • Support new field to specify which VM(s) to remove in the Scale In Request to SO

    •  Is VID going to call policy to determine which VM to remove or will a user enter the information on the GUI

    • Support Common DMaaP interface to send request to SO

Goal: Auto VNF Configuration

APPC

  • Adopt CDS for use in Auto Configuration (Priority: 2)

  • Change ConfigScaleOut to support Auto Configuration  (Priority: 2)

SDNC

  • Adopt CDS for use in Auto Configuration (Priority: 2)

  • Change ConfigScaleOut to support Auto Configuration  (Priority: 2)



SO

  • Change APPC/SDNC API usage to adopt Auto Configuration  (Priority: 2)

Goal: Updates to Manual and Auto Scale Out

APPC

  • Pre Action phase for Scale Out  (Priority: 3)

  • Post Action Phase for Scale Out (Priority: 3)

SDNC

  • Pre Action phase for Scale Out  (Priority: 3)

  • Post Action Phase for Scale Out (Priority: 3)

SO

  • Add pre action phase to Scale Out Workflow (Priority: 3)

  • Add Post action phase to Scale Out Workflow  (Priority: 3)



Goal: Homing and Capacity Check

OOF

  • Support a Homing and Capacity Check  Function (Priority: 4)

SO

  • Call Homing and Capacity API on OOF  (Priority: 4)



Goal: Controller_Type Lookup

SO

  • Utilize new Controller_Lookup Function  (Priority: 4)





Goal: Support for TOSCA Orchestration Model

CLAMP

SO

VID