Upgrading VNF instances with new version of VNF package changing only charm and primitives
Proposers
- Gerardo García (Telefónica)
- Francisco Javier Ramón (Telefónica)
- Francisco Rodríguez (Indra)
- Alexis Romero (Indra)
- David García (Canonical)
- Guillermo Calvino (Canonical)
Description
Once we have a VNF running, there is no mechanism in OSM to upgrade the active charm for that VNF instance. The idea is to replace the active charm with a new charm passed by the end user. That charm could reside on a local repo or could be passed as part of the NB API call.
This feature will also enable the update of the primitives. This will be done through the update of VNF packages. OSM will store the latest version of the VNF packages as well as the older versions. If there are running instances of VNFs using an older version of the package, the OSM UI and OSM CLI should allow the upgrade of the instance.
This feature will not cover the upgrade of all the fields in a VNF descriptor, but only the upgrade of the primitives. Therefore, OSM should provide documentation about what fields can be edited between versions.
Demo or definition of done
A new test should be defined. The test will instantiate a VNF, then upgrade the charm via the API call, finally run a day2 action using one of the primitives that changed in the new charm with respect to the old one.
The robot test will do the following:
- Upload version 1.0 of a VNF package and a NS package using it
- Deploy a NS instance
- Execute actions
- Upgrade the VNF package to a different version (p.e 1.1)
- Upgrade the NS instance to use the new package
- Execute new actions included in the new version of the VNF package
- Execute an updated actions included in both the old and the new version of the VNF package
The feature is considered done when the previous robot test succeeds.