Red Hat GLOBAL FILE SYSTEM 5.0 Manual do Utilizador descarregar pdf (Página 17)

Deploying a Failover Cluster

Configuring the Cluster

Once you create the cluster and set up Parallels Virtual Automation, configure the cluster as

follows:

1 Distribute the configuration file (/etc/cluster/cluster.conf) to all servers, and start the

clustering services on two cluster nodes:

# service cman start

# service rgmanager start

Try to start the clustering services simultaneously (or as fast as possible, one after another) on

both nodes.

2 Wait for the clustering services you started on two cluster nodes to restart all the other nodes in

the cluster.

3 Once the nodes are restarted, start the clustering services on these nodes:

# service cman start

# service rgmanager start

4 Configure the clustering service on each node in the cluster to start in the default runlevel. For

example, if your system default runlevel is set to 3, you can enable the service by executing the

following commands on each of the cluster nodes:

# chkconfig --level 3 cman on

# chkconfig --level 3 rgmanager on

5 Use the clustat utility (you can run it on any cluster node) to make sure that all the services

have been successfully started. If they have not, investigate the cluster logs stored in

/var/log/messages by default. Keep in mind that the information you are looking for may

be placed on different servers in the cluster.

6 If you plan to use Parallels Virtual Automation for managing your cluster, log in to the PVA

Management Node, and register all clustered services. To register a clustered service, use the

IP address you assigned to the service when creating the cluster.

Configuring Containers in Failover Clusters

When creating Containers on nodes participating in a failover cluster, make sure that the ONBOOT

parameter in their configuration files (/etc/vz/conf/CT_ID.conf) is set to yes. If this

parameter is set to yes for a Container, the Container is automatically started once it is failed over

from one cluster node to another; otherwise, the Container remains in the stopped state.

If the ONBOOT parameter is set to no, change it to yes using this command:

# pctl set CT_ID --onboot yes --save

1 2 ... 12 13 14 15 16 17 18 19 20 21 22 ... 27 28

Sem comentários

Red Hat GLOBAL FILE SYSTEM 5.0 Manual do Utilizador Página 17