You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Given the complexity of build-and-replace and delete-and-build, we are planning to push it across multiple releases and thus focusing one important component (traffic migration).

Traffic migration is key to multiple end-to-end functions – control loop, change management. For traffic migration, we will scope to defining the common API across different VNF types/services.


1)      Flexible workflow designer and orchestrator

  1. Impacted components: SDC, SO, VID
  2. Contributors: AT&T, Amdocs, Huawei (?)
  3. Functionalities
    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)


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
    2. Use case across different VNF types – vGW/vCPE, vFW, vLB, vDNS, vVOLTE (will need to pick/prioritize)
    3. Assessment report on commonalities/differences across VNF types – e.g., IP based redirection, DNS based or load balancer
    4. Incorporate recipe for traffic migration as part of in-place software upgrade workflow – quiesece/resume traffic are part of the SO workflow
    5. Develop recipe (using Ansible, NETCONF or REST) for traffic migration depending on the protocol used to communicate with the VNF  


3)      5G RAN PNF Software upgrade

  1. Impacted components: APPC, SO, SDC, A&AI, Ansible/EM
  2. Contributors: AT&T, China Mobile, Huawei
  3. Functionalities
    1. Leverage in-place software upgrade Beijing use case to demonstrate application to 5G RAN PNFs
    2. Health check (pre/post)
    3. Software download, installation and activation
    4. Roll-back for unsuccessful execution
    5. Manual processing / intervention for failures/roll-back issues

Will update slides soon.


 


Details on Flexible Designer/Orchestrator


ONAP Run Time Support of SDC Workflow Designer Use Case for CasaBlanca (Proposal)

Allow users to schedule and execute user designed workflows (designed with ONAP/R2 SDC Workflow Designer) from the VID interface.  The support of this use case includes:

  • SO push of Activities to the SDC Activity Specification Catalog
  • Distribution and Deployment of SDC Workflow to SO
  • Ability for a user to select a SDC Workflow, enter WF parameter values and schedule execution from VID
  • Ability for SO to execute the user designed SDC Workflow


  • No labels