We have the same restriction for storage tags in a compute and disk offering.
I had initially assumed it was due to the following: If we, say, deployed a VM to a host with the host tag X that we wanted to make sure that the VM could only be migrated to those hosts that are tagged as X. This doesn't appear to be the case, though. It seems that you can deploy a VM to a host tagged as X and then migrate it to a host not tagged as X. That being the case, it seems the host tags field should be mutable in a compute offering. On Tuesday, September 22, 2015, ilya <ilya.mailing.li...@gmail.com> wrote: > Is there any reason why we cant alter hosttags for service offering once > its created? i've done it many times from the backend and not seen any > issues, but i wonder if there any technical reason.. > > Thanks > ilya > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud <http://solidfire.com/solution/overview/?video=play>*™*
