Show Table of Contents
10.4. XML Representation of a Cluster
Example 10.1. An XML representation of a cluster
<cluster id="00000000-0000-0000-0000-000000000000"
href="/ovirt-engine/api/clusters/00000000-0000-0000-0000-000000000000">
<name>Default</name>
<description>The default server cluster</description>
<link rel="networks"
href="/ovirt-engine/api/clusters/00000000-0000-0000-0000-000000000000/networks"/>
<link rel="permissions"
href="/ovirt-engine/api/clusters/00000000-0000-0000-0000-000000000000/permissions"/>
<link rel="glustervolumes"
href="/ovirt-engine/api/clusters/00000000-0000-0000-0000-000000000000/glustervolumes"/>
<link rel="glusterhooks"
href="/ovirt-engine/api/clusters/00000000-0000-0000-0000-000000000000/glusterhooks"/>
<link rel="affinitygroups"
href="/ovirt-engine/api/clusters/00000000-0000-0000-0000-000000000000/affinitygroups"/>
<cpu id="Intel Penryn Family"/>
<architecture>X86_64<architecture/>
<data_center id="00000000-0000-0000-0000-000000000000"
href="/ovirt-engine/api/datacenters/00000000-0000-0000-0000-000000000000"/>
<memory_policy>
<overcommit percent="100"/>
<transparent_hugepages>
<enabled>false</enabled>
</transparent_hugepages>
</memory_policy>
<scheduling_policies>
<policy>evenly_distributed</policy>
<thresholds low="10" high="75" duration="120"/>
</scheduling_policies>
<version major="4" minor="0"/>
<supported_versions>
<version major="4" minor="0"/>
</supported_versions>
<error_handling>
<on_error>migrate</on_error>
</error_handling>
<virt_service>true</virt_service>
<gluster_service>false</gluster_service>
<threads_as_cores>false</threads_as_cores>
<tunnel_migration>false</tunnel_migration>
<trusted_service>false</trusted_service>
<ha_reservation>false</ha_reservation>
<ballooning_enabled>false</ballooning_enabled>
<ksm>
<enabled>true</enabled>
</ksm>
</cluster>

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.