Update TOSCA requirements for type and template
The final to be draft of TOSCA spec has drastically changed how TOSCA types should declare requirements and how requirements can be assigned in the node template.
The TOSCA type definition must declare requirement with following keywords as shown in example below for a requirement for Compute node type. The 'capability' is required one where as other keywords are optional and can be used in any combination. However, it is preferred that, all keywords (capability, relationship and node) are mentioned in the type definition.
requirements:
- local_storage:
capability: tosca.capabilit
node: tosca.nodes.
The current logic to create relationship between TOSCA types are based on the requirements and needs to be updated accordingly to above changes. The TOSCA definition for base type is defined in the TOSCA_definitio
On the TOSCA template side, the node template can specify requirement using 'capability, relationship and node' keywords or just by a capability name (as provided in most of the existing tests templates under the tests directory in toscalib)
There is a notion of target_filter or node_filter but that doesn't need to be implemented in this blueprint.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Sahdev Zala
- Direction:
- Needs approval
- Assignee:
- srinivas_tadepalli
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Sahdev Zala
- Completed by
- Sahdev Zala
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Update TOSCA requirements for template and type
Addressed by: https:/
Added occurrences of requirements validation
(spzala) one of the above changes were abandoned, as heat-translator project was split into two projects i.e. new one tosca-parser. Changes were implemented under tosca-parser
