Skip to content

OSM NG-UI to support input and file upload of primitiveParams used with config primitives defined for Helm-based KDUs

Proposers

  • Patrik Rokyta (NetNumber)

Target MDG/TF

NG-UI

Description

The requirement is for the OSM NG-UI to support the input (web form) and file upload for the primitiveParams used with config primitives defined for Helm-based KDUs in the NF package (upgrade, status, rollback). Otherwise, Helm-based KDUs cannot be upgraded using the OSM NG-UI resulting in a significant degradation of the user experience (the user must fallback to CLI or NBI).

OSM r10 only supports key-value-pairs as primitiveParams while the Helm-based KDUs need a structured YAML object referred to as the "values.yaml file". Note, the support of the structured YAML object is already implemented in OSM r10 for the NS instantiate operation (refer to the additionalParams that provide for structured objects and file upload via the OSM NG-UI). The same level of support is also required during the execution of the day2 config primitives via the OSM NG-UI.

Demo or definition of done

When applying a primitive (upgrade, status, rollback) to a Helm-based KDU using the NG.UI, the NG-UI provides for to possibility to define or upload the Helm release specific YAML content, AKA "values.yaml". The YAML content is then used as primitive params in the primitive operation that triggers helm upgrade, status, rollback.
Note, the CLI/NBI already supports this use case. Example NBI:

---
member_vnf_index: nti-nf
kdu_name: nti-nf
primitive: upgrade
primitive_params:
  global: <-- the "values.yaml" content starts here
  ...
Edited by garciadeblas