XenServer 7.6

Code name: "lima".

Released in September 2018.

Changes

ChangeElementDescription
Published class Cluster Cluster-wide Cluster metadata
Published class Cluster_host Cluster member metadata
Published class probe_result A set of properties that describe one result element of SR.probe. Result elements and properties can change dynamically based on changes to the the SR.probe input-parameters or the target.
Published class sr_stat A set of high-level properties associated with an SR.
Published field Cluster.cluster_config Contains read-only settings for the cluster, such as timeouts and other options. It can only be set at cluster create time
Published field Cluster.cluster_hosts A list of the cluster_host objects associated with the Cluster
Published field Cluster.cluster_stack Simply the string 'corosync'. No other cluster stacks are currently supported
Published field Cluster.cluster_stack_version Version of cluster stack, not writable via the API. Defaulting to 2 for backwards compatibility when upgrading from a cluster without this field, which means it is necessarily running version 2 of corosync, the only cluster stack supported so far.
Published field Cluster.cluster_token The secret key used by xapi-clusterd when it talks to itself on other hosts
Published field Cluster.other_config Additional configuration
Published field Cluster.pending_forget Internal field used by Host.destroy to store the IP of cluster members marked as permanently dead but not yet removed
Published field Cluster.pool_auto_join True if automatically joining new pool members to the cluster. This will be `true` in the first release
Published field Cluster.uuid Unique identifier/object reference
Published field Cluster_host.PIF Reference to the PIF object
Published field Cluster_host.cluster Reference to the Cluster object
Published field Cluster_host.enabled Whether the cluster host believes that clustering should be enabled on this host. This field can be altered by calling the enable/disable message on a cluster host. Only enabled members run the underlying cluster stack. Disabled members are still considered a member of the cluster (see joined), and can be re-enabled by the user.
Published field Cluster_host.host Reference to the Host object
Published field Cluster_host.joined Whether the cluster host has joined the cluster. Contrary to enabled, a host that is not joined is not considered a member of the cluster, and hence enable and disable operations cannot be performed on this host.
Published field Cluster_host.other_config Additional configuration
Published field Cluster_host.uuid Unique identifier/object reference
Published field probe_result.complete True if this configuration is complete and can be used to call SR.create. False if it requires further iterative calls to SR.probe, to potentially narrow down on a configuration that can be used.
Published field probe_result.configuration Plugin-specific configuration which describes where and how to locate the storage repository. This may include the physical block device name, a remote NFS server and path or an RBD storage pool.
Published field probe_result.extra_info Additional plugin-specific information about this configuration, that might be of use for an API user. This can for example include the LUN or the WWPN.
Published field probe_result.sr Existing SR found for this configuration
Published field sr_stat.clustered Indicates whether the SR uses clustered local storage.
Published field sr_stat.free_space Number of bytes free on the backing storage (in bytes)
Published field sr_stat.health The health status of the SR.
Published field sr_stat.name_description Longer, human-readable description of the SR. Descriptions are generally only displayed by clients when the user is examining SRs in detail.
Published field sr_stat.name_label Short, human-readable label for the SR.
Published field sr_stat.total_space Total physical size of the backing storage (in bytes)
Published field sr_stat.uuid Uuid that uniquely identifies this SR, if one is available.
Published message Cluster.create Creates a Cluster object and one Cluster_host object as its first member
Published message Cluster.destroy Destroys a Cluster object and the one remaining Cluster_host member
Published message Cluster.get_network Returns the network used by the cluster for inter-host communication, i.e. the network shared by all cluster host PIFs
Published message Cluster.pool_create Attempt to create a Cluster from the entire pool
Published message Cluster.pool_destroy Attempt to destroy the Cluster_host objects for all hosts in the pool and then destroy the Cluster.
Published message Cluster.pool_force_destroy Attempt to force destroy the Cluster_host objects, and then destroy the Cluster.
Published message Cluster.pool_resync Resynchronise the cluster_host objects across the pool. Creates them where they need creating and then plugs them
Published message Cluster_host.create Add a new host to an existing cluster.
Published message Cluster_host.destroy Remove the host from an existing cluster. This operation is allowed even if a cluster host is not enabled.
Published message Cluster_host.disable Disable cluster membership for an enabled cluster host.
Published message Cluster_host.enable Enable cluster membership for a disabled cluster host.
Published message Cluster_host.force_destroy Remove a host from an existing cluster forcefully.
Published message SR.probe_ext Perform a backend-specific scan, using the given device_config. If the device_config is complete, then this will return a list of the SRs present of this type on the device, if any. If the device_config is partial, then a backend-specific scan will be performed, returning results that will guide the user in improving the device_config.
Changed field Cluster.token_timeout the unit is now seconds
Changed field Cluster.token_timeout_coefficient the unit is now seconds