ETSI's Bug Tracker |
Anonymous | Login | Signup for local Mantis account | 21-05-2024 16:29 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 | ||||||||
0008209 | SOL001 - TOSCA-based NFV descriptors spec | [NFV Specifications] Feature Gap | public | 24-05-2023 05:45 | 25-04-2024 10:47 | ||||||||
Reporter | Sujeet Banerjee | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | ||||||||||||
Status | confirmed | Resolution | open | ||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0008209: [R4.4.1] [Clause 6.8.14] tosca.nodes.nfv.Mciop does not declare "properties" or "attributes", in discordance with SOL018 | ||||||||||||
Description | With reference to Clauses in SOL018 R4.3.1: "6.2.1.3 Conveying parameters" and "4.2.2.3.1 Helm TM chart file structure" [verbatim from SOL018] In case of using HelmTM for the OS container workload management service interface by the CISM, there are two ways to convey input parameters to the CISM APIs. Run-time information is conveyed by overriding the default values of the "values.yaml" configuration of the Helm™ chart and design-time information is conveyed by configuration files included in the HelmTM charts (see clause 4.2.2.3.1). [/verbatim] Feature Gap: The TOSCA node "tosca.nodes.nfv.Mciop" does not declare "properties" or "attributes" to convey the Design-time configurations and information of an MCIOP (or a Helm™ chart as per the SOL018 clause 6.2.1.3 stated above) | ||||||||||||
Additional Information | The Helm™ chart CLI allows multiple arguments as --set-string, --set-file, --set-json, --set, with Ordering of the --set-** arguments being important. External link: https://helm.sh/docs/helm/helm_install [^] Additionally, the question is, can we define a relative ordering of VDUs (OSContainerDeployableUnit) associated to an MCIOP? I believe, NOT. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
Notes | |
(0016623) lishi (developer) 25-04-2024 10:47 |
This is related to the work in ENH02.06, please see the progress in https://nfvprivatewiki.etsi.org/index.php?title=Feature_Tracking_Release_4#ENH02:_Special_technical_enhancements. [^] It adds support for artifacts in the VNF package tha perform the mapping between NFV parameters obtained from the API and input parameters to the cloud native templates (e.g. Helm charts). |
Issue History | |||
Date Modified | Username | Field | Change |
24-05-2023 05:45 | Sujeet Banerjee | New Issue | |
25-04-2024 10:47 | lishi | Note Added: 0016623 | |
25-04-2024 10:47 | lishi | Status | new => confirmed |
MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |