Change Management Extensions

For Casablanca release, we propose the following functionalities.

1)  Flexible workflow designer and orchestrator  COMMITTED

1. Impacted components: SDC, SO, and VID (nice-to-have)
2. Contributors: AT&T, Amdocs, Huawei (?)
3. Functionalities

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

Run-time support of User Designed Workflows

2)      Traffic migration building block COMMITTED

1. Impacted components: SDNC, APPC
2. Contributors: AT&T, Orange, Intel
3. Functionalities
   1. Traffic to one or multiple (V)NFs is distributed by a Traffic Distribution/Balancing Entity
   2. For Casablanca, we will focus on the LCM action necessary for traffic migration. For Dublin and beyond, we will create a workflow within SO for traffic migration
   3. New LCM action to control traffic distribution (to achieve traffic migration) - will also have to update CDT Design tool
   4. DistributeTraffic LCM action (Alternative is ConfigModify LCM action if PTLs recommend to push DistributeTraffic LCM to Dublin)
      
      1. Anchor point ID (VNF ID in action identifier)
      2. Traffic distribution weights for all nodes covered by the anchor point that require changes - this will be in the payload section in the form of "ConfigFileName" The config file (json) would be stored in the Ansible docker.
      3. The playbook would read a Traffic Distribution Configuration file associated with the DistribConfigName value sent by the Controller
      4. If we want to test/try various traffic distributions (many tests), we could have many Traffic Distribution Configuration files, each with it own DistribConfigName.

      5. The Playbook could also include a step to take a backup of the Traffic Distribution/Balancing Entity current traffic distrib/configuration and save it locally at some dir path. If the new traffic distribution action is rejected/failed then the playbook can restore previous traffic distribution/config. The Playbook can offer lots of flexibility and it is up to the entity SME to decide what he/she wants to do upon a DistributeTraffic action request.

   5. Mechanisms for traffic migration - implemented by controller
      1. Assessment report on commonalities/differences across VNF types – e.g., IP based redirection, DNS based or load balancer
4. Integration/testing
   
   1. For Casablanca, we will demonstrate traffic migration across 2 vFWs using traffic source as the anchor point
   2. Ansible playbook for adjusting the traffic weight on the traffic source (anchor point)
   3. Traffic weight before migration: 100,0 and traffic weight after migration: to 0,100
   4. Second test case would be traffic migration (quiesece / drain) on vGW/vCPE

Execution flow:

User → DMAAP → SDNC/APPC → Ansible → VNF(s)

Design flow:

User uploads Ansible playbook into CCSDK

3)      5G RAN PNF Software upgrade

1. Impacted components: SDNC, Ansible (CCSDK)
2. Contributors: AT&T, China Mobile, Huawei
3. Functionalities

   1. Leverage in-place software upgrade Beijing use case (minor changes) to demonstrate application to 5G RAN PNFs

   2. Complete generic building blocks for flexible upgrade workflow design

   3. Enhance precheck and postcheck steps with vendor specific rules

   4. Integrate the external controller into ONAP controller, and the EC will handle temporary states retrieval/storage/analysis of PNFs

   5. PNF ID, Expected Software Version, Controller Type, EC type, Rule Name and corresponding parameters can be specified at run time 

   6. Update A&AI entry with new PNF software version, as ‘active version’

   7. Support Batch software upgrade operations (stretch goal)

4) Change Management Scheduler COMMITTED

1. Impacted components: OOF
2. Contributors: AT&T
3. Functionalities
   
   1. Discover schedule based on the change management constraints
   2. Constraints
      
      1. Time-based - e.g., execute the change activity during the maintenance window and weekdays
      2. Concurrency of how many NF instances to change at a time - this is concurrency within a single user request
      3. NF conflicts (if time permits) - avoid work scheduled at the same time on the same NF instance
   3. Input
      
      1. List of NF instances - request details as depicted in the Beijing script
      2. Start/end times
      3. Expected duration
      4. Constraint/policy
      5. Type of change (workflow name)
      6. Concurrency value
   4. Output
      
      1. Schedule - time and instance at which the workflow would be executed

4. Integration/Testing plan

   1. Use Beijing vGW in-place software upgrade to demo execution based on the schedule output by OOF