Flexible designer and orchestrator
Traffic migration
https://docs.onap.org/en/casablanca/submodules/integration.git/docs/docs_vFWDT.html
5G RAN PNF In-place software upgrade
https://git.onap.org/integration/tree/docs/docs_5G_PNF_Software_Upgrade.rst?h=casablanca
5G - PNF Software Update
5G - PNF Software Update Test Status
Change schedule optimizer
https://docs.onap.org/en/casablanca/submodules/optf/cmso.git/docs/index.html
M4 is GREEN for all Change Management Functionalities.
For Casablanca release, we propose the following functionalities.
SDC | SO | SDNC | APPC | CCSDK [Ansible playbooks] | OOF | A&AI | Policy | DCAE | Test Case | Status | |
Flexible designer/orchestrator | Amdocs | vGW in-place software upgrade | |||||||||
Traffic management | Orange, Intel Lead: Lukasz Rajewski Lead: Eric Multanen | vFW migrate traffic and vGW quiesce/resume traffic | |||||||||
5G PNF in-place software upgrade | 5G PNF in-place software upgrade (emulator) | ||||||||||
Change schedule optimization | trigger vGW in-place software upgrade at scheduled time |
API Freeze | M3 | 23-Aug-18 |
Code Freeze | M4 | 20-Sep-18 |
Integration | RC0 | 11-Oct-18 |
RC1 | 25-Oct-18 |
1) Flexible workflow designer and orchestrator
Flow Designer Orchestration High Level Diagram
Run-time support of User Designed Workflows
2) Traffic migration building block
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.
Execution flow:
User → DMAAP → SDNC/APPC → Ansible → VNF(s)
Design flow:
User uploads Ansible playbook into CCSDK
For the LCM action :
If the payload contains pnf-flag and it is set to true then that indicates request for PNF.
If it is set to false, then the request is for VNF, and we will use vnf-id in input and nf-naming-code in payload.
nf-naming-code = vgw for example.
SDNC will look up nf-naming-code in AAI if not passed in payload.
For PNF, we will use the following in payload: pnf-name and ipaddress-v4-oam
3) 5G RAN PNF Software upgrade
Leverage in-place software upgrade Beijing use case (minor changes) to demonstrate application to 5G RAN PNFs
Complete generic building blocks for flexible upgrade workflow design
Enhance precheck and postcheck steps with vendor specific rules
External controller would receive instructions from Ansible SDNC
PNF ID, Expected Software Version, Controller Type, EC type, Rule Name and corresponding parameters can be specified at run time
Update A&AI entry with new PNF software version, as ‘active version’
Support Batch software upgrade operations (stretch goal)
4) Change Management Scheduler
Integration/Testing plan
Use Beijing vGW in-place software upgrade to demo execution based on the schedule output by OOF