Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated Issues


Gliffy
nameScaling Seq Diagram Copy
pagePin10

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. Possible items to be checked in a preparation phase:
    2. Upgrade and rollback for both VNF and RAP
    3. Snapshot Saving
    4. Another ongoing scaling operation
    5. Syncronization problems between VNFM and VNF database
    6. DB Service StatusUse 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?
    1. Do we need additional configuration changes after VM removal? Use a generic Post phase call that has a scaling flag to trigger a Post scaling playbook
    2. In onboarding package vendor needs to say whether or not they support a Pre and Post action
  5. How do we use Redistribute_Traffic?
    1. How do we know when Redistibute is finished? 
      1. talk with Ops and use a MOPS type action to monitor the VNF to determine when Redistribute has finished. 
  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?