ETSI's Bug Tracker - 3GPP SA5 Bug Tracking
View Issue Details
00081603GPP SA5 Bug Tracking[NFV Specifications] Feature Gappublic15-12-2022 05:4315-12-2022 09:18
Sujeet Banerjee 
 
normalminorhave not tried
newopen 
 
 
0008160: [SOL001] [4.3.1] The node tosca.nodes.nfv.Mciop does not support OCI compliant helm charts
Context: The future HELM versions would support OCI, and would be hosted/deployed from OCI-compliant registries.

References:
1. https://helm.sh/docs/topics/registries/ [^]
2. OCI ==> Open Containers Initiative (https://opencontainers.org/ [^])

The ETSI SOL001 4.3.1 specification does not have a provision (within tosca.nodes.nfv.Mciop) to allow specifying an OCI URI for the helm-charts, in the VNFD.

The referred TOSCA node, however, allows a packaged helm-chart as a ZIP-ed artifact. But, that's the only provision.
Need to Allow MCIOPs that may not be packaged as an artifact, or may be hosted on an OCI repository/registery remotely, with a URI.

Kubernetes, Helm-clients are already supporting OCI compliant helm-charts and docker-images.

This gap needs to be filled-in for SOL001 as well.
No tags attached.
Issue History
15-12-2022 09:18Sujeet BanerjeeNew Issue
15-12-2022 09:18Sujeet BanerjeeIssue generated from: 0008157

Notes
(0016391)
Sujeet Banerjee   
15-12-2022 06:58   
"Packaged Helm/docker as artifacts" also makes the management and versioning of the VNF Packages an overhead for the vendors. A small update in Helm-chart or a minor fix would require not only an update in the repository but as well in the VNF package (update the MCIOP artifact - which would be of 10 to 15GB order in size).

With allowing OCI URI for the helm-charts and docker-images, there is a choice to update the URI in the VNF package (and only if required, in the worst case).