-
-<b>cluster</b> attributes :
-\li <b>id (mandatory)</b>: the identifier of the cluster to be used
- when referring to it.
-\li <b>prefix (mandatory)</b>: each node of the cluster has to have a
- name. This is its prefix.
-\li <b>suffix (mandatory)</b>: node suffix name.
-\li <b>radical (mandatory)</b>: regexp used to generate cluster nodes
- name. Syntax is quite common, "10-20" will give you 11 machines
- numbered from 10 to 20, "10-20;2" will give you 12 machines, one
- with the number 2, others numbered as before. The produced number
- is concatenated between prefix and suffix to form machine names.
-\li <b>power (mandatory)</b>: same as <b>host</b> power.
-\li <b>core</b>: same as <b>host</b> core.
-\li <b>bw (mandatory)</b>: bandwidth for the links between nodes and
- backbone (if any). See <b>link</b> section for syntax/details.
-\li <b>lat (mandatory)</b>: latency for the links between nodes and
- backbone (if any). See <b>link</b> section for syntax/details.
-\li <b>sharing_policy</b>: sharing policy for the links between nodes
- and backbone (if any). See <b>link</b> section for syntax/details.
-\li <b>bb_bw </b>: bandwidth for backbone (if any). See <b>link</b>
- section for syntax/details. If both bb_* attributes are omitted,
- no backbone is created (alternative cluster architecture described
- before).
-\li <b>bb_lat </b>: latency for backbone (if any). See <b>link</b>
- section for syntax/details. If both bb_* attributes are omitted,
- no backbone is created (alternative cluster architecture described
- before).
-\li <b>bb_sharing_policy</b>: sharing policy for the backbone (if
- any). See <b>link</b> section for syntax/details.
-\li <b>availability_file</b>: Allow you to use a file as input for
- availability. Similar to <b>hosts</b> attribute.
-\li <b>state_file</b>: Allow you to use a file as input for states.
- Similar to <b>hosts</b> attribute.
-\li <b>loopback_bw </b>: bandwidth for loopback (if any). See <b>link</b>
- section for syntax/details. If both loopback_* attributes are omitted,
- no loopback link is created and all intra-node communication will
- use the main network link of the node. Loopback link is a <b>FATPIPE</b>.
-\li <b>loopback_lat </b>: latency for loopback (if any). See <b>link</b>
- section for syntax/details. See loopback_bw for more info.
-\li <b>topology </b>: network topology to use. For now SimGrid supports FLAT
- (default, with or without backbone, as described before),
- <a href="http://en.wikipedia.org/wiki/Torus_interconnect">TORUS
- </a> and FAT_TREE attributes for this tag.
-\li <b>topo_parameters </b>: specific parameters to pass for the topology
- defined in the topology tag. For torus networks, comma-separated list of
- the number of nodes in each dimension of the torus. For fat trees, refer to
- \ref AsClusterFatTree "AsClusterFatTree documentation".
-
+Attribute name | Mandatory | Values | Description
+--------------- | --------- | ------ | -----------
+id | yes | string | The identifier of the cluster. Facilitates referring to this cluster.
+prefix | yes | string | Each node of the cluster has to have a name. This name will be prefixed with this prefix.
+suffix | yes | string | Each node of the cluster will be suffixed with this suffix
+radical | yes | string | Regexp used to generate cluster nodes name. Syntax: "10-20" will give you 11 machines numbered from 10 to 20, "10-20;2" will give you 12 machines, one with the number 2, others numbered as before. The produced number is concatenated between prefix and suffix to form machine names.
+power | yes | int | Same as the ``power`` attribute of the ``<host>`` tag.
+core | no | int (default: 1) | Same as the ``core`` attribute of the ``<host>`` tag.
+bw | yes | int | Bandwidth for the links between nodes and backbone (if any). <b>See <b>link</b> section for syntax/details.</b>
+lat | yes | int | Latency for the links between nodes and backbone (if any). See <b>link</b> section for syntax/details.
+sharing_policy | no | string | Sharing policy for the links between nodes and backbone (if any). See <b>link</b> section for syntax/details.
+bb_bw | no | int | Bandwidth for backbone (if any). See <b>link</b> section for syntax/details. If bb_bw and bb_lat (see below) attributes are omitted, no backbone is created (alternative cluster architecture <b>described before</b>).
+bb_lat | no | int | Latency for backbone (if any). See <b>link</b> section for syntax/details. If bb_lat and bb_bw (see above) attributes are omitted, no backbone is created (alternative cluster architecture <b>described before</b>).
+bb_sharing_policy | no | string | Sharing policy for the backbone (if any). See <b>link</b> section for syntax/details.
+availability_file | no | string | Allows you to use a file as input for availability. Similar to <b>hosts</b> attribute.
+state_file | no | string | Allows you to use a file as input for states. Similar to <b>hosts</b> attribute.
+loopback_bw | no | int | Bandwidth for loopback (if any). See <b>link</b> section for syntax/details. If loopback_bw and loopback_lat (see below) attributes are omitted, no loopback link is created and all intra-node communication will use the main network link of the node. Loopback link is a <b>FATPIPE</b>.
+loopback_lat | no | int | Latency for loopback (if any). See <b>link</b> section for syntax/details. See loopback_bw for more info.
+topology | no | FLAT\|TORUS\|FAT_TREE (default: FLAT) | Network topology to use. SimGrid currently supports FLAT (with or without backbone, as described before), <a href="http://en.wikipedia.org/wiki/Torus_interconnect">TORUS </a> and FAT_TREE attributes for this tag.
+topo_parameters | no | string | Specific parameters to pass for the topology defined in the topology tag. For torus networks, comma-separated list of the number of nodes in each dimension of the torus. For fat trees, refer to \ref AsClusterFatTree "AsClusterFatTree documentation".
+
+TODO