DemandFlow Support Centre

HYPCLUSTER: Hypervisor Cluster

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A hypervisor cluster grouping physical hosts under a single management domain with shared storage, networking, and HA/DRS capabilities.

HYPCLUSTER: Hypervisor Cluster

A hypervisor cluster grouping physical hosts under a single management domain with shared storage, networking, and HA/DRS capabilities.

Default definition. This article describes the default HYPCLUSTER 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 HYPCLUSTER.

Entity properties

PropertyValue
Entity codeHYPCLUSTER
Display nameHypervisor Cluster
PluralHypervisor Clusters
Level300

Use cases

HYPCLUSTER sits between physical servers (COMPINV) and virtual machines (COMPINV with assetType=Virtual Machine). It represents the management-plane cluster (vCenter cluster, SCVMM host group, Proxmox cluster, oVirt cluster) that orchestrates VM placement, live migration, HA failover, and resource balancing across member hosts. The General panel captures platform, version, and management endpoints.

Fields

Cluster Information

FieldTypeRequiredNotes
nametextYesCluster Name.
descriptiontext (multi-line)Description.
platformenumYesValid ids: 1 (VMware vSphere), 2 (Microsoft Hyper-V), 3 (Proxmox VE), 4 (KVM / libvirt), 5 (Citrix Hypervisor (XenServer)), 6 (Nutanix AHV), 7 (Oracle VM), 8 (oVirt / RHV), 9 (Other).
versiontextPlatform Version.
statusenumYesValid ids: 1 (Active), 2 (Maintenance), 3 (Degraded), 4 (Failed), 5 (Provisioning), 6 (Decommissioned).
environmentenumValid ids: 1 (Production), 2 (Staging), 3 (Development), 4 (Test), 5 (DR).
sitereference → SITEData centre site where this cluster resides
nwplatinstreference → NWPLATINSTTelecom platform instance this cluster supports
dplatreference → DPLATIT platform instance this cluster supports
currentSwVersionreference → VIRTSWVERActive virtualisation software version

Management

FieldTypeRequiredNotes
managementUrltext (URL)vCenter, Proxmox UI, oVirt Engine, etc.
apiEndpointtext (URL)API Endpoint.
managementServerreference → COMPINVvCenter appliance, SCVMM server, etc.
licenseModelenumValid ids: 1 (Per Socket), 2 (Per Core), 3 (Per VM), 4 (Subscription), 5 (Open Source), 6 (Included (OEM)).
licenseKeytextLicense Key / Ref.

Capacity Summary

FieldTypeRequiredNotes
hostCountnumberHosts.
vmCountnumberVirtual Machines.
totalCpuCoresnumberTotal CPU Cores.
usedCpuCoresnumberAllocated vCPUs.
totalMemoryGBnumberTotal Memory (GB).
usedMemoryGBnumberAllocated Memory (GB).
totalStorageGBnumberTotal Storage (GB).
usedStorageGBnumberUsed Storage (GB).

High Availability

FieldTypeRequiredNotes
haEnabledbooleanHA Enabled.
admissionControlbooleanPrevent VM power-on if HA capacity insufficient
failoverCapacitynumberNumber of host failures the cluster can tolerate
hostMonitoringbooleanHost Monitoring.
vmMonitoringbooleanVM Monitoring.
heartbeatDatastorestextDatastores used for HA heartbeat

Distributed Resource Scheduling

FieldTypeRequiredNotes
drsEnabledbooleanDRS Enabled.
drsAutomationLevelenumValid ids: 1 (Manual), 2 (Partially Automated), 3 (Fully Automated).
drsMigrationThresholdnumber1 = conservative, 5 = aggressive
dpmEnabledbooleanDistributed Power Management - power off idle hosts
storagesDrsEnabledbooleanStorage DRS Enabled.

License Position

FieldTypeRequiredNotes
totalSocketsnumberSum of physicalSockets across all hosts in this cluster
totalCoresnumberSum of physicalCores across all hosts
totalLicensedSocketsnumberSum of purchased per-socket licenses
totalLicensedCoresnumberSum of purchased per-core licenses
clusterComplianceStatusenumValid ids: compliant (Compliant), overdeployed (Over-deployed), nearLimit (Near Limit), unknown (Unknown).
vmReclaimCandidatesnumberVMs flagged as Idle or Underutilised

Additional panels

  • Activity timeline panel attached.

Relationships

  • Lookups: site points at a SITE record; nwplatinst points at a NWPLATINST record; dplat points at a DPLAT record; currentSwVersion points at a VIRTSWVER record; managementServer points at a COMPINV record.
  • Related lists: COMPINV, COMPINV, DATASTORE (format SUB|HYPCLUSTER), VSWITCH (format SUB|HYPCLUSTER), RESOURCEPOOL (format SUB|HYPCLUSTER), HYPLICENSE (format SUB|HYPCLUSTER), VIRTSWVER (format SUB|HYPCLUSTER).

Creating a Hypervisor Cluster via the API

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

{
  "entity":   "HYPCLUSTER",
  "level":    300,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "platform": "1",
  "status": "1",
  "description": "..."
}

Listing Hypervisor Clusters

# All records in your tenant
GET /v1/entities/HYPCLUSTER/SUB:<your-sub-id>

See also

hypclusterhypervisorclusterclusters

Was this article helpful?

← Back to Knowledge Base