Modeling instantiation parameters in OSM

Proposers

• Gerardo García (Telefónica)
• Francisco Javier Ramón Salguero (Telefónica)

Description

This is a long term feature, intended to change the way instantiation parameters are modeled and managed in OSM. Right now, instantiation parameters are modeled in file "osm_nbi/validation.py", e.g. in structures like ns_instantiate and additional_params_for_vnf. There is a mix of OSM-defined parameters and user-defined parameters, and the structure is totally different from the descriptor.

The feature will model instantiation parameters as part of OSM IM, so that they are under control of the TSC. In addition, the feature will allow the incorporation of user-defined parameters (key:value pairs) that could be conveyed as part of the instantiation e.g. to day-0 params in cloud-init files, day-1 params used by initial config primitives, etc.

It should follow the principles of usability, maintainability and alignment with standards.

Instantiation parameters should arrive to the NBI in the way foreseen in ETSI NFV SOL005 API. Ideally, they should follow a similar structure to the NSD, VNFD and NST, so that they should be easy to fill by an end user. It should be possible to do an easy merge of both structures (descriptor and instantiation parameters) in order to build the final target to be deployed. That target should be stored in the corresponding record.

Instantiation parameters will be backwards compatible. Osmclient and NG-UI might help in that transition, translating the received instantiation parameters from the old format to the new format.

Demo or definition of done

All robot tests will be updated so that all instantiation parameters follow the new format. Feature will be considered done when all robot tests pass.