Hi Rafael, there is a bug, that only one host-tag can be used within service offerings. But there is an open PR https://github.com/apache/cloudstack/pull/4399 to address this ;)
Regards, Michael Michael Brußk Administration - Network Services GMS Cloud Infrastructure Services We Transform. Trust into Value itelligence Global Managed Services GmbH ▪ Breitscheidstrasse 48 ▪ 01237 Dresden phone: +49 3591 2952 2555 e-mail: michael.bru...@itelligence.de www.itelligencegroup.com Wir halten Sie immer auf dem Laufenden! Folgen Sie uns auf unseren Social Media Kanälen: Xing LinkedIn Facebook Twitter Profitieren Sie vom Know-how unserer Experten – mit dem itelligence Infoservice! Jetzt kostenlos registrieren! itelligence Global Managed Services GmbH ▪ Sitz: Bautzen ▪ Handelsregister: Amtsgericht Dresden, HRB 21356 Geschäftsführer: Mirko Kruse ▪ André Walter -----Ursprüngliche Nachricht----- Von: rva...@privaz.io.INVALID <rva...@privaz.io.INVALID> Gesendet: Donnerstag, 12. November 2020 13:04 An: users@cloudstack.apache.org Betreff: Service Offerings and Host Tags EXTERNAL MAIL: Hi! I am trying to create service offerings targetting particular clusters, for example those of hosts with a low power CPU, or SSD local storage, things like that. I am using host tags both in the host and in the service offering. I am assuming that if a service offering is tagged a host with those tags will be selected to schedule newly created VMs. Is this functionality working? Is anybody using it than can share her/his experience? Does it work for single or multiple tags? I don't get it to work, and I wonder if I am missing something. Rafael
