vccluster_resource_pool

Client for named child resource pools under a vCenter cluster (SOAP/pyVmomi).

Every cluster has an implicit root ResourcePool (ClusterComputeResource.resourcePool) – but vCenter rejects any field (reservation, limit, or shares) being set on that root pool with com.vmware.vim.resourcePool.error.rootSettingDisallowed, since shares are only meaningful relative to sibling pools and the root has none.

The real capability this wraps (matching the Ansible role’s own community.vmware.vmware_resource_pool) is a named child pool created directly under the cluster’s root – which is a completely ordinary, fully-configurable vim.ResourcePool once it exists.

saltext.vcf.clients.vccluster_resource_pool.get_or_none(opts, cluster, name, profile=None)[source]

Return the moId of resource pool name under cluster, or None.

saltext.vcf.clients.vccluster_resource_pool.create(opts, cluster, name, profile=None)[source]

Create resource pool name directly under cluster’s root pool.

Returns the new pool’s moId. CreateResourcePool requires a full ResourceConfigSpec up front (unlike UpdateConfig, there’s no existing config to leave fields unset against) – created with vSphere’s own defaults (normal shares, no reservation, no limit).

saltext.vcf.clients.vccluster_resource_pool.delete(opts, cluster, name, profile=None)[source]

Delete resource pool name under cluster.

saltext.vcf.clients.vccluster_resource_pool.get_shares(opts, cluster, name, profile=None)[source]

Return {cpu, memory} allocation for resource pool name under cluster.

saltext.vcf.clients.vccluster_resource_pool.set_shares(opts, cluster, name, *, cpu=None, memory=None, profile=None)[source]

Set CPU and/or memory allocation on resource pool name under cluster.