ACC can only route provisioning based on the tags ( compute and storage)
assigned to a service offering so if you are looking at mandatory automatic
assignment based on guest OS provisioning it is not possible without
segregating your environment. If you are OK with soft segregation then you can
create 2 sets of service offerings.
http://docs.cloudstack.apache.org/en/4.11.1.0/adminguide/service_offerings.html
Thanks,
Sergey
On 9/15/20, 7:36 AM, "Rakesh Venkatesh" <www.rakeshv....@gmail.com> wrote:
Hello All
I want your opinion on how you organize deploying different types of
VM's(Linux, windows) on a specific set of hypervisors.
In our setup, we have added a tag "Linux,Unix" on few hypervisors and also
on templates so that when we create a vm using these templates then it will
be deployed on HV's matching that tag only. If there is no tag on the
template then it can be deployed on any hypervisor.
We have some windows templates which do not have a tag as they are uploaded
by customers and when VM is created from that template, it will be deployed
in any suitable hypervisor but we want it to be deployed on a hypervisor
having "Windows" tag. Is there any way to achieve this apart from using
template tag?
Another way is to use the OS type and match with hypervisor tags but that
may not be a suitable solution. So if anyone has managed to deploy windows
vm's on windows tagged hypervisor and linux vm's on linux/unix tagged
hypervisor then please let me know
--
Thanks and regards
Rakesh
