vim_resource_pool

SOAP ops on resource pools: move + share-level config.

REST /api/vcenter/resource-pool lacks both move and the share-level cpuAllocation/memoryAllocation config. These go through pyVmomi vim.ResourcePool.

saltext.vcf.clients.vim_resource_pool.move(opts, rp_id_or_name, target_parent, profile=None)[source]

Move rp_id_or_name under target_parent. Synchronous.

target_parent may be a resource-pool moId, name, or vim.ResourcePool.

saltext.vcf.clients.vim_resource_pool.get_shares(opts, rp_id_or_name, profile=None)[source]

Return {cpu, memory} allocation dicts (reservation, limit, shares).

saltext.vcf.clients.vim_resource_pool.set_shares(opts, rp_id_or_name, *, cpu=None, memory=None, profile=None)[source]

Set CPU and/or memory allocation. Each is a dict with any of: reservation, expandable_reservation, limit, shares_level (low|normal|high|custom), shares_value (int).

SOAP ResourceConfigSpec requires both cpuAllocation and memoryAllocation to be populated; any None argument is merged on top of the pool’s current allocation so partial updates work safely.