DemandFlow Support Centre

RESOURCEPOOL: Resource Pool

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A logical partition of CPU and memory resources within a hypervisor cluster, with reservations, limits, and shares for workload isolation.

RESOURCEPOOL: Resource Pool

The RESOURCEPOOL entity: A logical partition of CPU and memory resources within a hypervisor cluster, with reservations, limits, and shares for workload isolation.

Default definition. This article describes the default RESOURCEPOOL definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches RESOURCEPOOL.

Entity properties

PropertyValue
Entity codeRESOURCEPOOL
Display nameResource Pool
PluralResource Pools
Level330

Use cases

RESOURCEPOOL models the resource partitioning layer in hypervisor clusters. vSphere Resource Pools, Hyper-V resource metering groups, Proxmox resource pools, etc. It is a child of HYPCLUSTER via comboKey (SUB|HYPC).

Resource pools can nest via the parentPool self-referential lookup, supporting hierarchical resource allocation (e.g. Production > Tier1 > Database). CPU and memory each have three controls: reservation (guaranteed minimum), limit (hard cap), and shares (relative priority when resources are contended).

Fields

Pool Information

FieldTypeRequiredNotes
nametextYesPool Name
descriptiontext (multi-line)Description
clusterreference → HYPCLUSTERCluster
parentPoolreference → RESOURCEPOOLNest within a parent resource pool
statusenumYesStatus Valid ids: 1 (Active), 2 (Inactive).
expandableReservationbooleanAllow this pool to borrow from parent when its own reservation is exhausted

CPU Resources

FieldTypeRequiredNotes
cpuReservationMhznumberGuaranteed minimum CPU
cpuLimitMhznumberHard cap. -1 = unlimited
cpuSharesnumberRelative priority (Low=1000, Normal=2000, High=4000, or custom)
cpuShareLevelenumShare Level Valid ids: 1 (Low), 2 (Normal), 3 (High), 4 (Custom).
cpuUsedMhznumberRead-only. Current Usage (MHz)

Memory Resources

FieldTypeRequiredNotes
memReservationGBnumberGuaranteed minimum memory
memLimitGBnumberHard cap. -1 = unlimited
memSharesnumberShares
memShareLevelenumShare Level Valid ids: 1 (Low), 2 (Normal), 3 (High), 4 (Custom).
memUsedGBnumberRead-only. Current Usage (GB)

Summary

FieldTypeRequiredNotes
vmCountnumberRead-only. VMs in Pool
childPoolCountnumberRead-only. Child Pools

Additional panels

  • Activity timeline panel attached.

Relationships

  • Lookups: cluster points at a HYPCLUSTER record; parentPool points at a RESOURCEPOOL record.
  • Related lists: COMPINV (format link), RESOURCEPOOL (format link).

Creating a Resource Pool via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "RESOURCEPOOL",
  "level":    330,
  "comboKey": "SUB:|ENT:",
  "name":    "Example name",
  "status":    1,
  "description":    "Example Description",
  "cluster":    ""
}

Listing Resource Pools records

GET /v1/entities/RESOURCEPOOL/SUB

See also

resourcepoolresource poolresource poolsentitydefinitionreference

Was this article helpful?

← Back to Knowledge Base