In the clusternodes section, specify the node name and the node ID of each node using the clusternode attributes: name and nodeid. The node name can be up to bytes in length. Validate the file against the cluster schema cluster.
For example:. For example, you could propagate the file to other cluster nodes using the scp command. Propagating the cluster configuration file this way is necessary the first time a cluster is created. It is possible to use the scp command to propagate an updated configuration file; however, the cluster software must be stopped on all nodes while using the scp command. While there are other elements and attributes present in the sample configuration file for example, fence and fencedevices , there is no need to populate them now.
Subsequent procedures in this chapter provide information about specifying other elements and attributes. If the cluster is running, proceed to Section 8. Basic Configuration Examples. Subsequent procedures in this chapter provide information about configuring fencing and HA services. The consensus Value for totem in a Two-Node Cluster. When you create a two-node cluster and you do not intend to add additional nodes to the cluster at a later time, then you should omit the consensus value in the totem tag in the cluster.
Kit Gerrits. Post by Kit Gerrits Isn't that what ccsd was for? Post by Fabio M. Post by carlopmart Thanks Fabio, but do I need to run ricci on both nodes?? If i need run ricci on both nodes, what about certificates generated by ricci init script?? Do i need to copy on both nodes?? Chris Feist. Di Nitto Post by Fabio M. Di Nitto Yes you need to run ricci on every single cluster node.
I am not entirely sure about ricci's internal, but I added Ryan and Chris in CC and they should be able to answer specifically your question.
0コメント