-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
None
In order to support design of ETSI SOL v3.3.1 NSDs (see SDC-3339) and maintain support for v2.7.1 we need to allow the user to specify the version of csar to be created.
We can do this by adding a metadata key-value pair to be used for specifying the version to be used. However this metadata will only be relevant to services belonging to the "ETSI NFV Network Service" category. Rather than hardcoding in a new metadata that is only applicable to one service category, the proposal is to support a mechanism where metadata keys can be added for specific categories in the category definition. Each key can be defined by:
- name - the name of the metadata key
- mandatory - whether it is mandatory to provide a value
- valid values - where specified, the value must be selected from a given list of allowed values.
For example:
ETSI_NFV_Network_Service: name: "ETSI NFV Network Service" icons: ['network_l_1-3'] metadataKeys: EtsiVersion: name: "ETSI Version" validValues: ['3.3.1', '2.7.1', '2.5.1'] mandatory: true
This new feature will be implemented for categories and sub-categories
- blocks
-
SDC-3339 Support for designing an ETSI SOL001 v3.3.1 compliant Network Service that can be deployed with an ETSI compliant NFVO
- Closed