Page History

...

1. 1. Catalog in SDC for meta-data about the building blocks – completed by Amdocs
   2. Designer/editor in SDC for creating workflow – committed to develop by Amdocs
   3. Convert already existing building blocks/activities to be workflow designer ready
   4. Move workflow out of service model to independent artifact – priority nice to have
   5. Distribution of workflow to SO – preferably with workflow as independent artifact
   6. Deployment of workflow in SO
   7. User interface (VID) to select workflow and input parameters for execution
   8. Execute workflow in SO
   9. Rainy day handling for unsuccessful workflow steps
   10. Visualize the execution results on VID dashboard
   11. Ability to cancel workflow execution (VID)

Flow Designer Orchestration High Level Diagram

Image Added

Run-time support of User Designed Workflows

Image Added

2)      Traffic migration building block

1. Impacted components: SDNC, APPC, VFC, SO
2. Contributors: AT&T, Orange, Intel
3. Functionalities
   1. Common API definition for traffic migration
      1. Source, destination nodes - pool
      2. Flow distribution policy - equal distribution for e.g.
      3. Anchor points - e.g., DNS for layer-4+ VNFs
      4. Fine-grained flow filter
      5. Failure handler
   2. Mechanisms for traffic migration - implemented by controllerUse case across different VNF types – vGW/vCPE, vFW, vLB, vDNS, vVOLTE (will need to pick/prioritize)
      1. Assessment report on commonalities/differences across VNF types – e.g., IP based redirection, DNS based or load balancer
      Incorporate recipe for traffic migration as part of in-place software upgrade workflow – quiesece/resume traffic are part of the SO workflow
4. Integration/testing
   
   1. Use case across different VNF types – vGW/vCPE, vFW, vLB, vDNS
   2. Develop recipe (using Ansible, NETCONF or REST) for traffic migration depending on the protocol used to communicate with the VNF API details:

3)      5G RAN PNF Software upgrade

...