[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tosca] [OASIS Issue Tracker] (TOSCA-245) Need clear description of relationship priority/ordering during deployment
|
I think there are two different types of dependencies here:
1.
Dependencies between different node templates in a topology template. I believe that in general, the assumption is that the orchestrator needs to create node templates in dependency order (as specified between by the relationships between
the node templates)
2.
Dependencies between node templates and artifacts (i.e. should artifacts be available/staged before or after creation of a node template?) It sounds like your examples fall in this category. I don’t believe the spec makes any statements
about this and it should be up to the orchestrator to do the right thing depending on the types of the artifacts. Chris -----Original Message----- Luca Gioppo commented on TOSCA-245: ----------------------------------- It all depends on the strategy that the orchestrator chooses to use to do the deploy. If I decide that I use puppet I need to dynamically generate all the puppet manifests before creating the VM since the VM once activated will call the puppet master and get the catalogue that it will use to do the rest (same NodeTemplates
descriptions but different approach) If I opt for bash ans SSH I need to have the VM and than issue all the commands in the VM so generate the script and than execute it or something (just idea since I use puppet :D ) We definitely need a dependency tree (I generate a graph based on the relationships but I still have to find a way to decide precedence or ordering on same level nodes: that is I have to install apache modules node type do I need an
order since they are all son of the Apache Node?[in that case no and I'm lucky but could not always be like that]) > 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) --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]