Hi, The 'onehost update' functionality isn't limited to CLUSTER, you can have different attributes like LOCATION, ENVIRONMENT, what makes it much flexible than the clusters in 2.x versions.
Operators are allowed in the requirements attribute, see the syntax here [1]. Shell wildcards can be also used, so you can do things like REQUIREMENTS = "CLUSTER = A | CLUSTER = B" REQUIREMENTS = "CLUSTER = *" Regards. [1] http://opennebula.org/documentation:rel3.0:template#requirement_expression_syntax -- Carlos Martín, MSc Project Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | [email protected] On Thu, Aug 11, 2011 at 9:28 PM, Shi Jin <[email protected]> wrote: > Hi there, > It seems like the onecuster command has been removed from the 3.0 version > and my understanding is that we need to use "onehost update" to insert > cluster info, which has worked well in our testing environment. > My question is that after we divide the hosts into several distinct > clusters, is there any way to allow a VM to be deployed within more than one > or all of the clusters? For example, is there a "REQUIREMENTS=cluster=all" > or "clusterA and clusterB" type of functionality? > Thanks. > Shi > > -- > Shi Jin, Ph.D. > > > _______________________________________________ > 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
