Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

This diagram supersedes the workflow described in the Casablanca Use Case

 

 

Resolved

  1. For Dublin Scaling will be done to respond to load issues.  Either manually or automatically.  Auto Scale In will be done based on the VNF crossing a low threshold trigger
  2. In Dublin we will use a Last In First Out (LIFO) method for targeting the instance to be removed
  3. We will add a Pre and Post Action Signal to notify the VNF when a scaling action is about to occur and when it has finished
  4. We will use Distribute_Traffic to move new traffic away from the target instance
  5. We will Use Quiesce_Traffic to return a signal when all existing traffic has been drained from the target instance
  6.  We will need to issue a Stop_VM before we issue the Terminate_VM
  7. NOTE: Scale In releases all resources (e.g. IP Addresses) for use by other VNFs.  The next scale out option will not re-use the resources released by Scale In. 

To Do

  1. Need to Lock VNF so that other operations will not conflict with Scaling Actions
  2. Need to further define "Pre Action - Scale In" and "Post Action - Scale In"
  3. Need to work with APPC team to make "Distribute_Traffic" and "Quiesce_Traffic" operate at the VNFC/VF_Module level
  4. Need to "WorkFlow Designer" enable this work flow
  5. Does SO need to request Configuration Parameter Values from SDNC in the Configuration phase?
  6. Can ConfigScaleIn and ConfigScaleOut be collapsed into "ConfigScaling" or even just ModifyConfig
  • No labels