VMwareAPI driver can only use the 0th resource pool

[Sirisha Guduru]

Nova essex setup with ESXi hypervisor.

In our scenario, the instance has to be provisioned in a separate resource pool. But the code present now only supports the provisioning of instance in only one resource pool i.e., the main resource pool of the ESX.

[Shawn Hartsock (hartsock)]

Please give more detail.

[Shawn Hartsock (hartsock)]

Is anyone working on this?

[Sabari Murugesan (smurugesan)]

I can work on this issue. The root resource pool is the default on which instances are created. This is true in the context of a cluster as well.

[Thierry Carrez (ttx)]

This sounds like something that doesn't match the guidelines for a "critical" bug (which is usually a serious regression or data loss issue). Could even be seen as a missing feature ;)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/35374

[Sabari Murugesan (smurugesan)]

This is indeed a enhancement rather than a bug. Stumbled upon this blueprint.
https://blueprints.launchpad.net/nova/+spec/accurate-capacity-of-clusters-for-scheduler

I can attribute my patch towards this blueprint. But at this point, there is no milestone that is set. I can work on this, if this feature is critical. I will bring this up in the next IRC meeting. Bug Reporter can also participate :- https://wiki.openstack.org/wiki/Meetings/VMwareAPI

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/43908

[Gary Kotton (garyk)]

https://review.openstack.org/35374 has been abandoned and was resurrected and rebased - please see https://review.openstack.org/#/c/43908/

[Shawn Hartsock (hartsock)]

Several driver design issues around resource pools should be covered in this refactor:
* https://blueprints.launchpad.net/nova/+spec/vmware-resource-pool-refactor