Juju vSphere cloud provider does not support resource pools or folders with vsphere 6.5/6.7

Bug #1807961 reported by Calvin Hartwell
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Christian Muirhead

Bug Description

Hi all,

Juju does not seem to handle the correct placement of machines into a Resource Pool or Folder on vSphere 6.5/6.7.

The cluster selection works, I.E if I have a data-center with multiple clusters in vSphere, I can choose which cluster to use, but placement within the cluster, I.E in a Folder or Resource Pool does not work.

Also, some of these constraints appear to be ignored as part of the bundle, an example is found here: https://gist.githubusercontent.com/CalvinHartwell/fb36f64531fb5d640d8c590e867b07ad/raw/07644cf334db45851d20acc5113c407459eb496d/vmware-cdk-constraints-ignored.yaml

My manual work around is to manually add the machines first, before deploying units and relationships, I.E:

juju add-machine zone=$ZONE --constraints root-disk=50G --constraints cores=4 --constraints mem=16G

This may have been partially fixed by this: https://github.com/juju/juju/pull/9481

Instead, Juju places all of the VM(s) onto the same, single esx hypervisor within a cluster which means there is no HA placement of services.

vSphere versions tested: 6.5 and 6.7. I have an internal (Canonical) video showing the issue and a work around for a current customer.


- Calvin

summary: Juju vSphere cloud provider does not support resource pools or folders
- in vsphere 6.5/6.7
+ with vsphere 6.5/6.7
description: updated
Revision history for this message
Christian Muirhead (2-xtian) wrote :

Hi Calvin - I think supporting resource pools should be straightforward. Folders are a bit trickier because at the moment we use them to track controller/model hierarchy at the provider level (in other providers we use tags for this).

It depends how much control you want/need over this - if it's a matter of specifying a parent folder for the controller folder (and then the model folders still go inside that folder) then it's not a big change. Would that do what you want?

Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.5.1
Changed in juju:
status: Triaged → Incomplete
Ian Booth (wallyworld)
Changed in juju:
milestone: 2.5.1 → 2.5.2
Revision history for this message
Christian Muirhead (2-xtian) wrote :

Support for resource pools: https://github.com/juju/juju/pull/9744

Changed in juju:
status: Incomplete → In Progress
Changed in juju:
assignee: nobody → Christian Muirhead (2-xtian)
Revision history for this message
John A Meinel (jameinel) wrote :
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: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
Changed in juju:
milestone: 2.5.6 → 2.5.7
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.