[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-206) lifecycle.Simple interface and plan/workflow management...
[ https://issues.oasis-open.org/browse/TOSCA-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luc Boutier updated TOSCA-206: ------------------------------ Component/s: Profile-YAML > lifecycle.Simple interface and plan/workflow management... > ---------------------------------------------------------- > > Key: TOSCA-206 > URL: https://issues.oasis-open.org/browse/TOSCA-206 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Bug > Components: Profile-YAML > Reporter: Luc Boutier > > I think that the Simple normative interface cause an issue with the lifecycle workflow generation and especially when relationships are used. > As a user I want indeed to have the pre-configure/post-configure source/target operations to be called before the configure operation of the node. > If a node uses simple rather than the default lifecycle operation the issue is that we don't have access to configure anymore (as a single operation is doing all in one). > So we should not state that the deploy is equivalent to create + configure but only to create and that configure is just dropped in case of Simple. > Anyway it is important to make clear the impact on the workflow (yes anyway all the workflow generation and management has to be clarified). -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]