Hey Adrian, You can achieve this via storage tags. So let’s say you have 2 storage pool i.e SSD and HDD, you can define the tags on storage pool and based on that you can create compute offering and disk offering where you can assign the same storage tag.
Vivek Kumar Manager - Cloud & DevOps IndiQus Technologies 24*7 O +91 11 4055 1411 | M +91 7503460090 www.indiqus.com <http://indiqus.com/> This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential and/or privileged. If you are not the intended recipient please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses. > On 21-Jan-2021, at 12:26 AM, Adrian Morris > <adr...@sdchostingandsupport.co.uk> wrote: > > Hi, > > I’m wondering if it is possible to define the storage pool a volume is > created on during both deployVirutalMachine and createVolume. If so could > someone please give me an example how they have achieved this? > > Ideally I want the user to decide whether they store their data on SSD or HDD. > > > Many Thanks > Adrian Morris CIIT > Director > > > > SDC Hosting and Support Ltd > 890 The Crescent, Colchester Business Park, Colchester, CO4 9YQ > > This e-mail (and any attachments) contains confidential information which may > be legally privileged and protected from disclosure. It is intended solely > for the individual or entity to whom it is addressed and others authorised to > receive it. If you are not the intended recipient of this e-mail or any parts > of it please telephone 07802 665733 immediately upon receipt. No other person > is authorized to copy, forward or disclose, distribute or retain this e-mail > in any form
