Re: updated workflow documents

(I thought I'd sent this, but it didnt apear on the list)



1. I note you can do the same today with Try deployments inside the Parallel


DeployVM extends Try {
   hostname TBD;
   action extends XenDeploy {
hostname PARENT:hostname;
   }
}


Parallel {
   vm1 extends DeployVM { hostname "host1";}
   vm2 extends DeployVM { hostname "host2";}
   vm3 extends DeployVM { hostname "host3";}
}

So its something you can already deal with with some form of 
composition. Still, there's no reason to hard code policy in a container 
when a single property can manage it.

Therefore we have a new todo item: 
http://jira.smartfrog.org/jira/browse/SFOS-83

One question, what should we do if a child fails to deploy? I dont like 
ignoring that as it can be a symptom of a deeper problem.

I think it may be best to have two attributes so both behaviours can be 
controlled:

  //terminate if a child terminates
  terminateOnAbnormalChildTermination true;
  //terminate if a child wont deploy
  terminateOnAbnormalChildDeploy true;

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV