Table of Contents
Scope
Support PNF software upgrade with schema update including service level LCM operations
- PNF software upgrade with updated service template
- PNF schema update with updated service template
- Service template update with multiple resource instances
- Including:
- Updating the design time service template using vendor provided onboarding package
- Upgrading a run time service instance based on the updated service template
- Updating the run time catalog at software upgrade completion
Schema Update
- Vendor delivers
- PNF box with pre-installed software, and
- PNF package which describes the functions supported by the PNF box
- At PNF software upgrade, a new software version is running in the PNF box which may introduce new functions. Without schema updates, the ONAP is not aware of any of the new functions, e.g. new PM counters, new CM Yang model, new Alarms, etc.
- In order to update the ONAP with the new functions introduced by the upgraded PNF software,
- a vendor shall provide a new PNF package with updated artifacts and the new PNF software image to the operator.
- the operator shall update the resource / service template based on the received PNF onboarding package, and upgrade the PNF software and update the run time catalog
Key Issues
Enable software version (Modelling/SDC/AAI):
- Onboarding the software version information using vendor provided onboarding package
- Supporting software version in internal model
- Store the upgrade path info at design time (SDC/SO/VID):
- Resource upgrade path
- Service upgrade options
- Run the upgrade at service level (SO): Executing the workflow at service level
- Update the run time catalog (AAI):
- Support updating resource model ID/version
- Support updating service model ID/version
Progress
- Solution for onboarding PNF software version is proposed in Resource Data Model team: ONAP R6+ Onboarding VNF/PNF package format, non-MANO artifacts set definition
- Architectural issue has been raised in architectural team