[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-245) Need clear description of relationship priority/ordering during deployment
[ https://issues.oasis-open.org/browse/TOSCA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Rutkowski updated TOSCA-245: ------------------------------------- Due Date: 30/Jun/15 Component/s: Profile-YAML > Need clear description of relationship priority/ordering during deployment > -------------------------------------------------------------------------- > > Key: TOSCA-245 > URL: https://issues.oasis-open.org/browse/TOSCA-245 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Task > Components: Profile-YAML > Reporter: Sahdev Zala > Fix For: CSD04 > > > Per discussion on 05/07/15 TOSCA TC Special 4 Hour Meeting: > What is the "strategy"? Related to JIRA issue TOSCA-219: > Need clear priority/ordering of relationships as it affects deployment > Relevant comment in Chapter 10. > (Luc) > Can we be more explicit what that means in terms of lifecycle: are we saying that the Service /Node that is “depended on” must always be deployed before the dependent Node is deployed? There has to be a general semantics defined, if we consider that such a generic requirement makes sense. -- 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]