Implicit pass of an OSM dictionary to Execution Environments

Proposers

• Gerardo García (Telefónica)

Description

Today the pass of information to the Execution Environment (EE) related to a NS, NF or DU has to be done explicitly through config steps typically at the day-1 (initial-config-primitive). This is not ideal since it forces the NF vendor to make them explicit without an actual need.

Instead, OSM could pass a well known dictionary with the relevant information for the EE. The EE could have structures and methods to eaily read them, thus facilitating its use. The information to be passed to the EE might not be restricted to the current information (mainly mgmt IP address), but also other relevant information might be added, like:

• Structure of the NF or NS
• Names of DU
• IP addresses of the different DU
• Etc.

The specific information to be passed is to be decided and could be potentially different for NS EE, NF EE and DU EE.

This mechanism has been successfully used for KDU proxy charms where an OSM config dictionary is passed to the KDU proxy charm with the list of KDU services, and for each service the IP address, port protocol, port number and service type. A call to an implicit action config is done during initial-config-primitive, passing the previous OSM dictionary to the EE with the relevant information for the KDU EE.

This feature will generalize this method to make it available to any EE.

Demo or definition of done

A new OSM package will be created with an EE being able to consume the OSM config dictionary. The descriptor won't make any reference to the OSM config dictionary (since it is implicit). A new test using this package will be created, and the test should contain a primitive to be executed that will confirm the use of the OSM config dictionary. The feature will be considered done when the test is passed.