[
https://issues.apache.org/jira/browse/ARIA-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942235#comment-15942235
]
ASF subversion and git services commented on ARIA-126:
------------------------------------------------------
Commit d74baa7895297bdcd190afdf823d3a70d2429e42 in incubator-ariatosca's branch
refs/heads/ARIA-126-update-node-statuses from [~avia]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-ariatosca.git;h=d74baa7 ]
ARIA-126 Add node states
1. The states are described in section 3.3.1 of the TOSCA spec.
2. The state is changed if a standard lifecycle operation runs of the
node, as described in sections 5.7.4.1, 5.7.4.4.1, and 5.7.4.4.2 of the TOSCA
spec.
3. We did not address the 'error' state yet.
This state is defined as part of the possible node states in the model, but
currently no execution path leads to setting a node's state to 'error'.
4. No validation of state transiontions.
For example, we do not validate if a node goes from 'created'
to 'started' without going through the 'configured' state in between.
> Update state of nodes during normative lifecycle execution
> ----------------------------------------------------------
>
> Key: ARIA-126
> URL: https://issues.apache.org/jira/browse/ARIA-126
> Project: AriaTosca
> Issue Type: Story
> Reporter: Avia Efrat
> Assignee: Avia Efrat
>
> Update a node's state while preforming tasks that reflect changes to its
> state.
> Currently, this will be hardcoded specifically for lifecycle operations, i.e.
> `created`, `configured`, `started` etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
