I believe (if not mistaken) that CloudStack will match first available
storage based on storage tags and availability, and will always choose
first storage pool, even though you have 3 of them available for particular
cluster.
In this sense, you can not really balance load across multiple Primary
Hi, all:
At my site, our currently practice is to have only one primary storage device
for each CloudStack cluster, serving up to 500 disk volumes with total of 10 –
20TB disk space. Now, we are replacing old NetApp clusters with new ones and
moving to SSD disks, so I need to recreate all my
+1 Deployed local environment and tested VM/host/storage lifecycles.
Hosts: KVM running on Ubuntu 16.04
Management server and database: running on Ubuntu 16.04
- create/use/delete system and user VMs
- register new template
- register service offering
- work with hosts (add, maintenance, remove)
