Description

PNF Software upgrade includes:

1. Support in-place software upgrade for PNF.
2. Define generic building blocks, which can be used for workflow design in the design time.
3. Support External Controller (e.g., EMS) as the main entity responsible for carrying out the detailed vendor-specific software upgrade steps.
4. Enhance precheck and postcheck steps in the upgrade process by vendor-specific rules. There are two approaches to provide these rules. One is artifacts in the PNF packages, and the other is preprovisioning in the EC. Anyhow, during the design time, operator could specify the used rules as need.
5.  Expected software version is modeled in PNF Modeling phase (same as 5G PNF PnP), and given corresponding value during the upgrade process.
6. Apply in-place software upgrade in Casablanca.
7. Define procedures involved in the design time and run time for specifying these rules. 
8. Enhance PNF modeling needed for PNF software upgrades (e.g., expected software version) and define processes in ONAP components (e.g., SO, A&AI, DCAE, and ONAP Controllers) for successful/unsuccessful software upgrades. 
9. Demonstrate single PNF upgrade and batch upgradeBasically, complete single PNF upgrade first, and the batch upgrade is considered as a stretch goal. 

Presentations:

1. 5Guc-RAN Operations (SW upgrade)-Casablanca-Huawei&CMCC 05112018v1.pptx
2. Change Management for life-cycle support from hybrid PNF and VNF management perspective_201806BeijingForum