Ohh, I missed the storage tags in the compute offering. I only configured it in 
the disk offering. Got it working now correctly. Thanks Slavka.

Thanks,
Irvin

> On Mar 2, 2022, at 2:46 PM, Slavka Peleva <[email protected]> 
> wrote:
> 
> Hi Irvin,
> 
> You have to add the same storage tags of your primary storage to the
> compute offering that you're using while deploying a VM. If this does not
> work, can you share more information about the two primary storage
> (Zone-wide or Cluster-wide), their tags and the compute offering tags?
> 
> Best regards,
> Slavka
> 
> On Wed, Mar 2, 2022 at 8:17 AM jcapagcuan . <[email protected]> wrote:
> 
>> Hi Antoine,
>> 
>> Yes, I’m using tags whenever i add data disk and that works fine. My issue
>> is for the root disk when I launch from a template, that’s when it
>> randomizes where to put the root disk to the 2 primary storage.
>> 
>> Thanks,
>> Irvin
>> 
>>> On Mar 2, 2022, at 10:05 AM, Antoine Boucher <[email protected]>
>> wrote:
>>> 
>>> Use tags on storage and on templates, compute offering or instance
>> creation.
>>> 
>>> Antoine Boucher
>>> [email protected]
>>> 
>>> 
>>> Confidentiality Warning: This message and any attachments are intended
>> only for the use of the intended recipient(s), are confidential, and may be
>> privileged. If you are not the intended recipient, you are hereby notified
>> that any review, retransmission, conversion to hard copy, copying,
>> circulation or other use of this message and any attachments is strictly
>> prohibited. If you are not the intended recipient, please notify the sender
>> immediately by return e-mail, and delete this message and any attachments
>> from your system.
>>> 
>>> On Mar 1, 2022, at 19:02, jcapagcuan . <[email protected]> wrote:
>>> 
>>> Hi,
>>> 
>>> I have created 2 primary storage for my Cloudstack (4.16.0). Whenever I
>> launch an instance from a template, it randomizes from the 2 primary
>> storage on where it will put the root disk. Is there a way to restrict the
>> root disk to a specific storage?
>>> 
>>> Thanks,
>>> Irvin
>>> 
>> 
>> 

Reply via email to