1. ONAP Change Management
Beijing Use Case Proposal
December 1, 2017

2. Overview Background Goal Mechanism Support for S3P goals
Amsterdam use cases demonstrate VNF instantiation and simple performance management capability
Change management is a critical life cycle activity required in any operator environment
Goal
Extend ONAP platform to support NF change management (e.g., software upgrades, configuration changes) in a scalable and flexible manner
Mechanism
Provide capability for flexible workflow creation and execution using generic building blocks from catalog
Support for S3P goals
Ability to define, create and execute workflows from a catalog will facilitate new VNF and service creation and thereby support an increasing number of services and VNFs
Use of well-defined and well-understood building blocks (as opposed to single use monolithic flows) will result in a more stable platform that is easier to modify and has better understood interaction between building blocks

3. Change Management Platform requirements / dependencies
SDC – (i) catalog of building blocks, (ii) designer for creating CM workflows
SO – execution of CM workflows
A&AI – (i) inventory of instances, (ii) lock/unlock VNF instances
Controller – execution of upgrade mechanisms such as in-place software upgrade
Scheduler – scheduling the CM workflow for execution at specific instance(s)
Any dependencies on specific VNF capabilities – none
VNFs that we would like to test the use cases
vFW [extending Amsterdam use case to support vFW software upgrade]
Companies willing to contribute – AT&T, Ericsson, Orange

4. CM design phase ONAP user SDC SO VID Design CM workflow
Deploy CM workflow
Send workflow API & meta information

5. CM execution phase ONAP user VID SO A&AI Controller
Request CM for a workflow and VNF instance
Send CM request
Lock VNF instance
Software installation and reboot
Status of software upgrade
Unlock VNF instance
Status of CM execution
Status of CM execution