Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page was used for initial draft solutions for Scale In.  It has now been deprecated and is no longer up to date.  The latest version can be found on the Dublin Scaling Use Case wiki section.



Gliffy
nameScaling Seq Diagram Copy
pagePin2327

Gliffy
nameScale In Diagram
pagePin15


 

 

 

 

Issues to be resolved

  1. When should scaling be done?
    1. In Dublin our primary reason for scaling will be focused on adjusting resources to the load.  As load increases or decreases, the VNF will scale Out or In as appropriate. This can be done either manually or automatically.
    2. Other reasons for scaling may include:
      1. Upgrades
      2. VM Moves
      3. Meet with Operations to determine other reasons
  2. Which instance should be removed?
    1. Is this an Optimization decision?
    2. How should Policy be involved? (Long term: Policy should query an OOF microservice)
    3. Last In First Out as a temporary solution? (Use in Dublin: will need to query for all instances and then choose)
  3. Do we need to a preparation phase?
    1. Use a generic Prep phase call that has a scaling flag that will trigger a pre scaling playbook
  4. Do we need a post scaling phase?Use a generic Post phase call that has a scaling flag to trigger a Post scaling playbookWe need a generic Pre-Action API with a scale in flag to trigger a scale in playbook.  This will allow the VNF to do any VNF specific actions prior to a scale in action
  5. We need a generic Pre-Action API with a scale in flag to trigger a scale in playbook.  This will allow the VNF to do any VNF specific actions prior to a scale in action

    1. In onboarding package vendor needs to say whether or not they support a Pre and Post action
  6. How do we use RedistributeDistribute_Traffic?How do we know when Redistibute is finished? talk with Ops and use a MOPS type action to monitor the VNF to determine when Redistribute has finished.  
    1. Distribute_Traffic will move all new traffic
      1. Will need to make Distribute_Traffic work at the VM/VNFC level
    2. Quiesce_traffic can be used for returning a response once all traffic is drained from the target instance
      1. will need to make Quiesce_Traffic work on the VM/VNFC level
  7. Need to build a ConfigScaleIn action and API for APPC and SDNC
  8. Will we be able to use CDS for AutoConfiguration?
  9. How do we determine which controller to use?
  10. STOP VM before Termination
  11. Scale In will release all resources.  It is not guaranteed that the same resources will be reassigned on the next scale out.