Hi, That is exactly what the AppFlow component does. Take a look at the documentation for 4.0 here [1]. It will be merged into the main distribution before 4.2, with a bunch of new features, including elasticity. The documentation for 4.2 can be found here [2], but it still needs to be completed.
Was that what you had in mind? Do you miss any key feature? Regards [1] http://opennebula.org/documentation:rel4.0:appflow [2] http://opennebula.org/documentation:rel4.2:appflow_use_cli -- Join us at OpenNebulaConf2013 <http://opennebulaconf.com> in Berlin, 24-26 September, 2013 -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | [email protected] | @OpenNebula<http://twitter.com/opennebula><[email protected]> On Sun, Jun 23, 2013 at 9:43 PM, Alberto Picón Couselo <[email protected]>wrote: > Hi all. > > I would like to know if Opennebula 3.8 or 4.0 (using Sunstone or CLI) is > capable to deploy a group of VMs (with persistent disk images) in a > concrete order and wait until a specific VM is deployed to proceed launching > the others. > > I think it could be a very interesting feature that would reduce redeployment > time when an infrastructure maintenance takes place. > > What do you think? > > Best Regards > Alberto Picón > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
