| |
ETSI's Bug Tracker |
| Anonymous | Login | Signup for local Mantis account | 30-04-2024 10:47 IST |  |
| Main | My View | View Issues | Change Log | Roadmap | Stop monitoring project |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0008157 | SOL001 - TOSCA-based NFV descriptors spec | [NFV Specifications] Feature Gap | public | 15-12-2022 05:43 | 22-02-2024 09:48 | ||||||||
| Reporter | Sujeet Banerjee | ||||||||||||
| Assigned To | |||||||||||||
| Priority | normal | ||||||||||||
| Status | confirmed | Resolution | open | ||||||||||
| Product Version | 4.3.1 | ||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0008157: [SOL001] [4.3.1] The node tosca.nodes.nfv.Mciop does not support OCI compliant helm charts | ||||||||||||
| Description | 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. | ||||||||||||
| Additional Information | 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. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Attached Files | |||||||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0016390) Sujeet Banerjee (reporter) 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). |
|
(0016619) lishi (developer) 22-02-2024 09:48 |
this would be a new requirement. It needs to be analyzed whether the existing procedure for upload VNF package with external artifacts supports providing the necessary access information to allow the NFVO to fetch the Helm chart from the OCI registry. In addition, if the service provider places the Helm chart in an OCI registry, the impacts on the VNFD would need to be analyzed. It may be considered in the next version. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 15-12-2022 05:43 | Sujeet Banerjee | New Issue | |
| 15-12-2022 06:58 | Sujeet Banerjee | Note Added: 0016390 | |
| 15-12-2022 09:18 | Sujeet Banerjee | Issue cloned: 0008160 | |
| 30-03-2023 01:47 | lishi | Status | new => confirmed |
| 22-02-2024 09:48 | lishi | Note Added: 0016619 | |
|
Issue History |
| MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |
 |