/ 4.11. Configuring a Clone Resource
	4.10. Configuring a Cluster Resource Group		4.12. Migrating a Cluster Resource

Configuring a Clone Resource

You may want certain resources to run simultaneously on multiple nodes in your cluster. To do this you must configure a resource as a clone. Examples of resources that might be configured as clones include STONITH and cluster file systems like OCFS2. You can clone any resource provided it is supported by the resource’s Resource Agent. Clone resources may even be configured differently depending on which nodes they are hosted.

There are three types of resource clones:

Anonymous Clones: These are the simplest type of clones. They behave identically anywhere they are running. Because of this, there can only be one instance of an anonymous clone active per machine.
Globally Unique Clones: These resources are distinct entities. An instance of the clone running on one node is not equivalent to another instance on another node; nor would any two instances on the same node be equivalent.
Stateful Clones: Active instances of these resources are divided into two states, active and passive. These are also sometimes referred to as primary and secondary, or master and slave. Stateful clones can be either anonymous or globally unique.

Procedure 4.11. Adding or Modifying Clones

Start the Linux HA Management Client and log in to the cluster as described in Section 4.1, “Linux HA Management Client”.
In the left pane, select Resources and click Add+Clone.
Enter a unique ID for the clone.
Below Options, set the Initial state of resource.
Activate the respective options you want to set for your clone and click Forward.
In the next step, you can either add a Primitive or a Group as sub-resources for the clone. These are created similar as described in Adding Primitive Resources or Adding a Resource Group.
If all parameters in the clone configuration dialog are set according to your wishes, click Apply to finish the configuration of the clone.