Installation guide

<ip address="127.143.131.100" monitor_link="yes"
sleeptime="10"/>
<apache config_file="conf/httpd.conf"
name="example_server" server_root="/etc/httpd" shutdown_wait="0"/>
</resources>
<service autostart="1" domain="example_pri" exclusive="0"
name="example_apache" recovery="relocate">
<fs ref="web_fs"/>
<ip ref="127.143.131.100"/>
<apache ref="example_server"/>
</service>
</rm>
For example, here is an Apache service that uses service-specific resources:
<rm>
<service autostart="0" domain="example_pri" exclusive="0"
name="example_apache2" recovery="relocate">
<fs name="web_fs2" device="/dev/sdd3"
mountpoint="/var/www2" fstype="ext3"/>
<ip address="127.143.131.101" monitor_link="yes"
sleeptime="10"/>
<apache config_file="conf/httpd.conf"
name="example_server2" server_root="/etc/httpd" shutdown_wait="0"/>
</service>
</rm>
Example 7.10, “ cl uster. co nf with Services Added: One Using Global Resources and One
Using Service-Specific Resources ” shows an example of a cl uster. co nf file with two
services:
exampl e_apache — This service uses global resources web_fs, 127. 14 3. 131. 10 0 ,
and example_server.
exampl e_apache2 — This service uses service-specific resources web_fs2,
127.14 3. 131. 10 1, and exampl e_server2.
5. Update the co nfi g _versi o n attribute by incrementing its value (for example, changing
from co nfi g _versi o n= "2" to co nfi g _versio n= "3">).
6. Save /etc/cl uster/cl uster.co nf.
7. (Opti o nal ) Validate the updated file against the cluster schema (cl uster.rng ) by
running the ccs_co nfi g _val i d ate command. For example:
[root@ example-01 ~]# ccs_co nfi g _val i d ate
Configuration validates
8. Run the cman_to o l versio n -r command to propagate the configuration to the rest of the
cluster nodes.
9. Verify that the updated configuration file has been propagated.
10. Proceed to Section 7.9, “ Verifying a Configuration” .
Red Hat Ent erprise Linux 6 Clust er Administ rat ion
122