While googling the subject, I came across the following slide deck: 
http://www.slideshare.net/srivastavasaksham/explicit-dedication-in-cloudstack, 
and on slide #7 it explained all.

Once I assign this new ExplicitDedicate affinity group to my instances,  they 
all get created on the intended cluster.

Yiping




On 10/19/15, 11:41 AM, "Yiping Zhang" <[email protected]> wrote:

>Hi, all:
>
>I am trying to work out  the best way of deploying VM’s onto a dedicated 
>cluster.  Here is what my CloudStack setup looks like:
>
>Domains:   d1, d2, d3, d4
>Clusters:    c1 (dedicated to d1),  c2 (not dedicated)
>Currently,  I am not using tags for hosts, storages, service offerings at all.
>
>When I login to domains d2/d3/d4, and create new VM’s,  they will go to 
>cluster c2.  That’s great as it is the intended results.
>However,  when I login to domain d1 and create new VM’s,  they can go to 
>either cluster c1 or c2, but I would like VM’s only go to c1.
>
>Is using host/storage tags and matching tags in service offering the only way 
>to achieve this goal ?
>
>The reason I am reluctant to use tags is that leads to proliferation of 
>service offerings, as the resulting number of SO  could grow exponentially 
>with the number of host/storage tags introduced.
>
>Thanks,
>
>Yiping

Reply via email to