/usr/share/doc/drbd-doc/users-guide/s-rhcs-failover-clusters.html is in drbd-doc 8.4~20151102-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 | <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3. Using DRBD in Red Hat Cluster fail-over clusters</title><link rel="stylesheet" type="text/css" href="default.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="home" href="drbd-users-guide.html" title="The DRBD User’s Guide" /><link rel="up" href="ch-rhcs.html" title="Chapter 9. Integrating DRBD with Red Hat Cluster" /><link rel="prev" href="s-rhcs-config.html" title="9.2. Red Hat Cluster configuration" /><link rel="next" href="ch-lvm.html" title="Chapter 10. Using LVM with DRBD" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">9.3. Using DRBD in Red Hat Cluster fail-over clusters</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="s-rhcs-config.html">Prev</a> </td><th width="60%" align="center">Chapter 9. Integrating DRBD with Red Hat Cluster</th><td width="20%" align="right"> <a accesskey="n" href="ch-lvm.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="s-rhcs-failover-clusters"></a>9.3. Using DRBD in Red Hat Cluster fail-over clusters</h2></div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png" /></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p>This section deals exclusively with setting up DRBD for Red Hat
Cluster fail over clusters not involving GFS. For GFS (and GFS2)
configurations, please see <a class="xref" href="ch-gfs.html" title="Chapter 11. Using GFS2 with DRBD">Chapter 11, <em>Using GFS2 with DRBD</em></a>.</p></td></tr></table></div><p>This section, like <a class="xref" href="ch-pacemaker.html" title="Chapter 8. Integrating DRBD with Pacemaker clusters">Chapter 8, <em>Integrating DRBD with Pacemaker clusters</em></a>, assumes you are about to
configure a highly available MySQL database with the following
configuration parameters:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
The DRBD resources to be used as your database storage area is named
<code class="literal">mysql</code>, and it manages the device <code class="literal">/dev/drbd0</code>.
</li><li class="listitem">
The DRBD device holds an ext3 filesystem which is to be mounted to
<code class="literal">/var/lib/mysql</code> (the default MySQL data directory).
</li><li class="listitem">
The MySQL database is to utilize that filesystem, and listen on a
dedicated cluster IP address, 192.168.42.1.
</li></ul></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="s-rhcs-example-cluster-conf"></a>9.3.1. Setting up your cluster configuration</h3></div></div></div><p>To configure your highly available MySQL database, create or modify
your <code class="literal">/etc/cluster/cluster.conf</code> file to contain the following
configuration items.</p><p>To do that, open <code class="literal">/etc/cluster/cluster.conf</code> with your preferred text
editing application. Then, include the following items in your
resource configuration:</p><pre class="programlisting"><rm>
<resources />
<service autostart="1" name="mysql">
<drbd name="drbd-mysql" resource="mysql">
<fs device="/dev/drbd/by-res/mysql/0"
mountpoint="/var/lib/mysql"
fstype="ext3"
name="mysql"
options="noatime"/>
</drbd>
<ip address="10.9.9.180" monitor_link="1"/>
<mysql config_file="/etc/my.cnf"
listen_address="10.9.9.180"
name="mysqld"/>
</service>
</rm></pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png" /></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p>This example assumes a single-volume resource.</p></td></tr></table></div><p>Nesting resource references inside one another in <code class="literal"><service/></code> is the
Red Hat Cluster way of expressing resource dependencies.</p><p>Be sure to increment the <code class="literal">config_version</code> attribute, found on the root
<code class="literal"><cluster></code> element, after you have completed your
configuration. Then, issue the following commands to commit your
changes to the running cluster configuration:</p><pre class="screen">ccs_tool update /etc/cluster/cluster.conf
cman_tool version -r <version></pre><p>In the second command, be sure to replace <span class="emphasis"><em><version></em></span> with the new
cluster configuration version number.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png" /></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p>Both the <code class="literal">system-config-cluster</code> GUI configuration utility and
the Conga web based cluster management infrastructure will complain
about your cluster configuration after including the <code class="literal">drbd</code> resource
agent in your <code class="literal">cluster.conf</code> file. This is due to the design of the
Python cluster management wrappers provided by these two applications
which does not expect third party extensions to the cluster
infrastructure.</p></td></tr></table></div><p>Thus, when you utilize the <code class="literal">drbd</code> resource agent in cluster
configurations, it is not recommended to utilize
<code class="literal">system-config-cluster</code> nor Conga for cluster configuration
purposes. Using either of these tools to only monitor the cluster’s
status, however, is expected to work fine.</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="s-rhcs-config.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch-rhcs.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch-lvm.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">9.2. Red Hat Cluster configuration </td><td width="20%" align="center"><a accesskey="h" href="drbd-users-guide.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 10. Using LVM with DRBD</td></tr></table></div></body></html>
|