Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
This diagram supersedes the workflow described in the Casablanca Use Case
Gliffy Diagram | ||||
---|---|---|---|---|
|
Resolved
- 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
- In Dublin we will use a Last In First Out (LIFO) method for targeting the instance to be removed
- 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
- We will use Distribute_Traffic to move new traffic away from the target instance
- We will Use Quiesce_Traffic to return a signal when all existing traffic has been drained from the target instance
- We will need to issue a Stop_VM before we issue the Terminate_VM
- 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
- Need to Lock VNF so that other operations will not conflict with Scaling Actions
- Need to further define "Pre Action - Scale In" and "Post Action - Scale In"
- Need to work with APPC team to make "Distribute_Traffic" and "Quiesce_Traffic" operate at the VNFC/VF_Module level
- Need to "WorkFlow Designer" enable this work flow
- Does SO need to request Configuration Parameter Values from SDNC in the Configuration phase?
- Can ConfigScaleIn and ConfigScaleOut be collapsed into "ConfigScaling" or even just ModifyConfig
...