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.




 

 

 

 

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. How should Policy be involved? (Long term: Policy should query an OOF microservice)
    2. Last In First Out as a temporary solution? (Dublin: will need to query for all instances and then choose)
  3. 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

  4. 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
  5. How do we use Distribute_Traffic? 
    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
  6. Need to build a ConfigScaleIn action and API for APPC and SDNC
  7. Will we be able to use CDS for AutoConfiguration?
  8. How do we determine which controller to use?
  9. STOP VM before Termination
  10. Scale In will release all resources.  It is not guaranteed that the same resources will be reassigned on the next scale out.