Migration between OSM versions

Migration between OSM versions

Proposers

• Francisco Rodríguez (Indra)

Target MDG/TF

NBI, LCM, RO

Description

Currently, the internal NF records in the OSM database are not necessarily compatible between versions. This makes migrations of running OSM instances difficult, since a procedure to change the DB contents in a way that is not documented is needed.

The feature will consist on providing the means to ensure that running instances of VNF are unaffected, without needing re-deployment, when the OSM version is migrated, either by making the internal NF records compatible or by having a tool in charge of performing the necessary internal changes.

Implementation may rely, at least in part, on the features #10515 (closed) “Internal Information Model” and #10891 “Versioning of OSM descriptor formats”.

Demo or definition of done

The definition of done will consist on having a running instance of OSM with several VNF and CNF deployed, and executing an upgrade procedure, from version X to version X+1. This procedure will include the migration tool if that is the chosen implementation. The running instances should be operable (list, delete, heal, execute primitives) after the upgrade.

The migration procedure from version X to version X+1 should be part of the tests to be executed before launching a new release.