ariatosca-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ARIA-126) Update state of nodes during normative lifecycle execution
Date Mon, 27 Mar 2017 13:39:41 GMT


ASF subversion and git services commented on ARIA-126:

Commit 0e107933e68ec8a6fbc690a02d59e2fca900a540 in incubator-ariatosca's branch refs/heads/ARIA-126-update-node-statuses
from [~avia]
[;h=0e10793 ]

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,, and 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:
>             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

View raw message