DemandFlow Support Centre

VIRTSWVER: Virtualisation Software Version

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A software version or release of a virtualisation platform running on a hypervisor cluster, with lifecycle dates tracking general availability through end-of-life and end-of-support.

VIRTSWVER: Virtualisation Software Version

A software version or release of a virtualisation platform running on a hypervisor cluster, with lifecycle dates tracking general availability through end-of-life and end-of-support.

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

Entity properties

PropertyValue
Entity codeVIRTSWVER
Display nameVirtualisation Software Version
PluralVirtualisation Software Versions
Level305

Use cases

A software version or release of a virtualisation platform running on a hypervisor cluster, with lifecycle dates tracking general availability through end-of-life and end-of-support.

VIRTSWVER tracks software versions for HYPCLUSTER. e.g. ESXi 8.0 Update 3, Proxmox VE 8.2, Hyper-V Server 2025 CU4. Structurally mirrors NWPLATSW (telecom platform software) and DPLATSW (IT platform software) but is a child of HYPCLUSTER via comboKey (SUB|HYPC). The four lifecycle dates (GA, EOL, EOS, EOSupport) are the critical fields for managing virtualisation currency and support expiry. The prereqs multi-objectLookup enables dependency chains (e.g. 'vCenter 8.0 U3 requires ESXi 8.0 U2+'). The Release panel captures change impact, testing, compliance, deployment, and post-deployment details for each version upgrade. important because hypervisor upgrades are high-risk operations affecting all hosted VMs.

Fields

Version Details

FieldTypeRequiredNotes
nametextYesRelease Name.
versiontextVersion.
typeenumValid ids: major (Major), minor (Minor), patch (Patch / Update), hotfix (Hotfix), emergency (Emergency Fix).
statusenumYesValid ids: planned (Planned), testing (Testing), active (Active), deprecated (Deprecated), eol (End of Life), retired (Retired).
clusterreference → HYPCLUSTERYesHypervisor Cluster.
componentenumWhich part of the virtualisation stack this version applies to Valid ids: hypervisor (Hypervisor (ESXi, Hyper-V, PVE)), management (Management (vCenter, SCVMM)), vsan (Storage (vSAN, Ceph)), nsx (Networking (NSX, ACI)), backup (Backup (Veeam, Zerto)), monitoring (Monitoring (vROps, Aria)), other (Other).
descriptiontext (multi-line)Description.

Lifecycle Dates

FieldTypeRequiredNotes
dategadateGeneral Availability.
dateeoldateEnd of Life.
dateeosdateEnd of Sale.
dateeosupdateEnd of Support.

Prerequisites & Dependencies

FieldTypeRequiredNotes
prereqsarray of references → VIRTSWVEROther virtualisation software versions required before this one can be deployed
minHwVersiontexte.g. VM hardware version 20, Gen2
compatibilityNotestext (multi-line)Known incompatibilities, required driver versions, etc.

Planning

FieldTypeRequiredNotes
dateplandatePlanned Date.
dateactualdateActual Date.
rbackavailbooleanRollback Available.
rbackplantext (multi-line)Rollback Plan.

Change & Impact

FieldTypeRequiredNotes
changeFeaturestext (multi-line)New Features.
changeFixestext (multi-line)Bug Fixes.
changeSecurityFixestext (multi-line)Security Fixes.
riskenumValid ids: low (Low), medium (Medium), high (High), critical (Critical).
approvalstatusenumValid ids: pending (Pending), approved (Approved), rejected (Rejected), deferred (Deferred).

Testing

FieldTypeRequiredNotes
teststatusenumValid ids: notstarted (Not Started), inprogress (In Progress), passed (Passed), failed (Failed), blocked (Blocked).
testcasesnumberTest Coverage (%).
testuatenumValid ids: pending (Pending), passed (Passed), failed (Failed).
testLabValidatedbooleanLab Validated.
testVmCompatibilitybooleanVM Compatibility Verified.
testsignoffreference → userSign-off By.
testNotestext (multi-line)Test Notes.

Deployment

FieldTypeRequiredNotes
depMaintenanceWindowtextMaintenance Window.
depMethodenumValid ids: rolling (Rolling (host by host)), parallel (Parallel), lifecycle (Lifecycle Manager / VUM), manual (Manual), ansible (Ansible / Automation).
depVmsMigratedbooleanVMs Migrated Pre-upgrade.
depDowntimeMinutesnumberDowntime (mins).
depNotestext (multi-line)Deployment Notes.

Post-Deployment

FieldTypeRequiredNotes
poststatusenumValid ids: ok (OK), issues (Issues Found), rolledback (Rolled Back).
postissuestext (multi-line)Issues.

Attachments and additional panels

  • Activity timeline panel attached.

Relationships

  • Lookups: cluster points at a HYPCLUSTER record; prereqs points at multiple VIRTSWVER record.

Creating a Virtualisation Software Version via the API

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

{
  "entity":   "VIRTSWVER",
  "level":    305,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example name",
  "status": "planned",
  "cluster": ""
}

Listing Virtualisation Software Versions

GET /v1/entities/VIRTSWVER/SUB

See also

virtswvervirtualisationsoftwareversionversions

Was this article helpful?

← Back to Knowledge Base