Page History

...

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 controller
      1. Assessment report on commonalities/differences across VNF types – e.g., IP based redirection, DNS based or load balancer
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

...

1. Impacted components: SDNC/APPC, SO, SDC, DCAE, A&AI, Ansible /EC(CCSDK)
2. Contributors: AT&T, China Mobile, Huawei, Ericsson(?)
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)

...