Heat Translator

Represent TOSCA node states

Registered by Sahdev Zala

As part of ongoing working draft 2 for TOSCA specs, states are introduced for node. As components (i.e., nodes) of TOSCA applications are deployed, instantiated and orchestrated over their lifecycle using normative lifecycle operations (see tosca.interfaces.node.lifecycle in the specs) it is important define normative values for communicating the states of these components normatively between orchestration and workflow engines and any managers of these applications.

Interfaces are now Standard with no states and Lifecycle with states.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
Sahdev Zala
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Sahdev Zala

Related branches

Sprints

Whiteboard

(spzala) I think it's a good idea that we discuss it via emails as you designed it. I think it may be a good idea to use Heat APIs to track states otherwise from just heat-translator it sounds not quite clear how states can be tracked once Heat deploy the stack.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.
Edit subscription

Subscribers

No subscribers.