The Cluster.NodeRuntimeInfo structure describes a node's runtime information in a VCHA Cluster.

JSON Example
    "state": "string",
    "role": "string",
    "placement": {
        "management_vcenter_name": "string",
        "management_vcenter_server_guid": "string",
        "vm_name": "string",
        "datacenter": "string",
        "datacenter_name": "string",
        "host": "string",
        "host_name": "string",
        "cluster": "string",
        "cluster_name": "string",
        "ha_network": "string",
        "ha_network_name": "string",
        "ha_network_type": "string",
        "management_network": "string",
        "management_network_name": "string",
        "management_network_type": "string",
        "storage": {
            "datastore": "string",
            "datastore_name": "string"
        "bios_uuid": "string"

The Cluster.NodeState enumerated type defines possible state a node can be in a VCHA Cluster.
UP : Node is up and has joined the VCHA Cluster.
DOWN : Node is down and has left the VCHA Cluster.


The Cluster.NodeRole enumerated type defines the role node can be in a VCHA Cluster.
ACTIVE : Node is having a role of Active. In this role, node runs a vCenter Server that serves client requests.
PASSIVE : Node is having a role of Passive. In this role node, runs as a standby for the Active vCenter Server and receives state updates. This node takes over the role of Active vCenter Server upon failover.
WITNESS : Node is having a role of Witness. In this role, node acts as a quorum node for avoiding the classic split-brain problem.


The PlacementInfo structure contains information to describe the inventory placement of a single node of a VCHA cluster. The active node's management vCenter server credentials are required to populate all fields except biosUuid.