Juju vSphere cloud provider needs a constraint for datastore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Christian Muirhead |
Bug Description
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.
You will end up hitting out-of-space errors like this one: https:/
Machine State DNS Inst id Series AZ Message
0 pending juju-fcc43f-0 bionic poweredOn
1 pending juju-fcc43f-1 bionic poweredOn
2 pending juju-fcc43f-2 bionic poweredOn
3 pending juju-fcc43f-3 bionic poweredOn
3/lxd/0 pending pending bionic
4 down pending bionic Insufficient disk space on datastore ''.
5 down pending bionic Insufficient disk space on datastore ''.
6 down pending bionic Insufficient disk space on datastore ''.
7 down pending bionic Insufficient disk space on datastore ''.
8 down pending bionic Insufficient disk space on datastore ''.
9 pending juju-fcc43f-9 bionic poweredOn
10 down pending bionic Insufficient disk space on datastore ''.
11 down pending bionic Insufficient disk space on datastore ''.
vSphere versions used were: 6.5 and 6.7.
Cheers,
- Calvin
Related issue with the vSphere provider: https:/
Related issue with lack of thin provisioning: https:/
description: | updated |
description: | updated |
description: | updated |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5.1 |
Changed in juju: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.7 |
Hi Calvin -
There's a model configuration setting "datastore" which will determine which datastore new VMs will use - I've just tested it out and it works. It's not the ideal way of doing this, since you'd need to change the setting between deploying applications or adding units if you want them to be allocated on different stores, but from the bug description it sounds like it would solve your problem?