© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
Hey all,
When Juju deploys virtual machines on vSphere, it does not provide any way to select the datastore which should be used to provide storage for the virtual machines. By default, it attempts to use the datastore which is available on the ESX hypervisor it is using to run the VM(s).
There are two problems with this approach:
1) Customers generally don't want the VM disks to sit on the local datastore, as this is usually a small disk used for snapshots, ISO images and other misc files.
2) If the VM disks being provisioned are too large, I.E bigger than those provided by the local datastore, it will not work because thin provisioning is not used by default (https:/
So, we need a way of specifying which datastore should be used when provisioning new VM(s) on vSphere. Usually each hypervisor is exposed or has connectivity to several different datastores.
Cheers,
- Calvin
Related issue with the vSphere provider: https:/
Related issue with lack of thin provisioning: https:/