-
Bug
-
Resolution: Done
-
Medium
-
Honolulu Release
-
None
-
None
-
Following issues are present in the requirement handling of the NSD:
- In the requirement mappings in the substitution mapping of the NSD:
- The requirement name does not match to a requirement defined in the node type definition of the NSD node type (i.e. the requirement is missing from the NSD node type definition)
- The node template requirement name does not match the name in the relevant VNFD node type definition
- In the topology template for the VNFs:
- The requirement name does not match the name in the relevant VNFD node type definition
Also, capabilities removed from the substitution mapping in the NSD as functionality not yet implemented to support properly. Full support for capabilities to be introduced in a new story
Following issues are present in the requirement handling of the NSD: In the requirement mappings in the substitution mapping of the NSD: The requirement name does not match to a requirement defined in the node type definition of the NSD node type (i.e. the requirement is missing from the NSD node type definition) The node template requirement name does not match the name in the relevant VNFD node type definition In the topology template for the VNFs: The requirement name does not match the name in the relevant VNFD node type definition Also, capabilities removed from the substitution mapping in the NSD as functionality not yet implemented to support properly. Full support for capabilities to be introduced in a new story - In the requirement mappings in the substitution mapping of the NSD:
Following issues are present in the requirement handling of the NSD:
- In the requirement mappings in the substitution mapping of the NSD:
- The requirement name does not match to a requirement defined in the node type definition of the NSD node type (i.e. the requirement is missing from the NSD node type definition)
- The node template requirement name does not match the name in the relevant VNFD node type definition
- In the topology template for the VNFs:
- The requirement name does not match the name in the relevant VNFD node type definition