OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (TOSCA-219) Workflow/Plan generation and components state dependency

Luc Boutier created TOSCA-219:

             Summary: Workflow/Plan generation and components state dependency
                 Key: TOSCA-219
                 URL: https://issues.oasis-open.org/browse/TOSCA-219
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Bug
          Components: Profile-YAML
            Reporter: Luc Boutier

Currently we have a quite good workflow for node management and relationships scripts injection. However one notion that is really important is a bit missing, what is the state of my target (or what I expect as target state) before some of my workflow is invoked.
Right now the only operation that is triggered with a known state is add_target where both nodes are already started an this may not be enough.

Basically in order to process most of HostedOn scenario (install a software on a compute, install a database on a RDBMS) I expect the target node to be started before the source node workflow is triggered.
In some HostedOn scenarios I may want to launch create operation when the target node is created or configured (copy a war in the tomcat directory before it starts).
There is the same problems related to connectsto relationship: for some components we may need to make sure that the target node is started before we call the pre_configure_source or post_configure_source (for example to configure a database in a configuration file before the application is started).

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]