[OASIS Issue Tracker] (TOSCA-245) Need clear description of relationship priority/ordering during deployment

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59812#comment-59812 ] 

Luca Gioppo commented on TOSCA-245:
-----------------------------------

I believe that we need two type of dependency description:
1) between nodes
2) between artifacts

Than between nodes we have two types of relationship:
1) operation relationship (the application wordpress will connect to the DB) where we do not imply any ordering (theoretically I can install wordpress node before MySQL node without having wordpress complaining if I know beforehand the naming of the DB and so on when wordpress comes up it will wait for the connection to be up)
2) installation relationship: I cannot install anything untill the Compute node is created in the cloud so orchestrator could not process the other nodes

To do this we need to have proper attributes in the specification and not rely on the node type otherwise we will have to change the orchestrator each time someone invent a new IT piece that needs a slightly different behaviour.
Probably something in the relation type could be useful also to express different graphs in the orchestrator

With the attributes we have more difficulty since we lost the "plan" tag from the XML standard and the whole BPMN thing.


> 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)