Implement mapping to SoftwareComponent
The current mapping of TOSCA nodes to HOT uses Heat resource SoftwareConfig which supports storing single configuration script. There are new Heat resources made available sometime back like SoftwareComponent and SoftwareDeployments which now allows for storing multiple configurations to address handling of lifecycle operations like create, update, delete etc. for a software component in one place.
We will be using these new resources for TOSCA node templates with multiple operations, this will provide a concise output HOT template compared to creating a SoftwareConfig resource to process individual configuration operation.
Ideally we want to use SoftwareComponent when multiple lifecycle operations involved.
Blueprint information
- Status:
- Started
- Approver:
- Sahdev Zala
- Priority:
- High
- Drafter:
- Sahdev Zala
- Direction:
- Needs approval
- Assignee:
- Julio Ruano
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- Sahdev Zala
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
WIP: Implement mapping of TOSCA nodes to HOT SoftwareComponents
