Sophie

Sophie

distrib > Fedora > 13 > i386 > by-pkgid > fd1445e4ec50ea0254985a386bb83a07 > files > 185

pacemaker-doc-1.1.1-1.fc13.i686.rpm

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 9. Advanced Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican 1.6" /><meta name="package" content="Pacemaker-Pacemaker_Explained-1.1-en-US-1-0" /><link rel="home" href="index.html" title="Configuration Explained" /><link rel="up" href="index.html" title="Configuration Explained" /><link rel="prev" href="s-rules-recheck.html" title="8.6. Ensuring Time Based Rules Take Effect" /><link rel="next" href="s-recurring-start.html" title="9.2. Specifying When Recurring Actions are Performed" /></head><body class=""><p id="title"><a class="left" href="https://fedorahosted.org/publican"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="https://fedorahosted.org/publican"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s-rules-recheck.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s-recurring-start.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 9. Advanced Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="ch-advanced-options">Chapter 9. Advanced Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-advanced-options.html#s-remote-connection">9.1. Connecting to the Cluster Configuration from a Remote Machine</a></span></dt><dt><span class="section"><a href="s-recurring-start.html">9.2. Specifying When Recurring Actions are Performed</a></span></dt><dt><span class="section"><a href="s-moving-resource.html">9.3. Moving Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s-moving-resource.html#id2813190">9.3.1. Manual Intervention</a></span></dt><dt><span class="section"><a href="s-failure-migration.html">9.3.2. Moving Resources Due to Failure</a></span></dt><dt><span class="section"><a href="ch09s03s03.html">9.3.3. Moving Resources Due to Connectivity Changes</a></span></dt><dt><span class="section"><a href="ch09s03s04.html">9.3.4. Resource Migration</a></span></dt></dl></dd><dt><span class="section"><a href="s-reusing-config-elements.html">9.4. Reusing Rules, Options and Sets of Operations</a></span></dt></dl></div><div class="section" title="9.1. Connecting to the Cluster Configuration from a Remote Machine"><div class="titlepage"><div><div><h2 class="title" id="s-remote-connection">9.1. Connecting to the Cluster Configuration from a Remote Machine</h2></div></div></div><div class="para">
			Provided Pacemaker is installed on a machine, it is possible to connect to the cluster even if the machine itself is not a part of it. To do this, one simply sets up a number of environment variables and runs the same commands as you would when working on a cluster node.
		</div><div class="table" id="id2722184"><div class="table-contents"><table summary="Environment Variables Used to Connect to Remote Instances of the CIB " border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
							Environment Variable
						</th><th>
							Description
						</th></tr></thead><tbody><tr><td>
							CIB_user
						</td><td>
							The user to connect as. Needs to be part of the hacluster group on the target host. Defaults to <span class="emphasis"><em>$USER</em></span>
						</td></tr><tr><td>
							CIB_passwd
						</td><td>
							The user's password. Read from the command line if unset
						</td></tr><tr><td>
							CIB_server
						</td><td>
							The host to contact. Defaults to <span class="emphasis"><em>localhost</em></span>.
						</td></tr><tr><td>
							CIB_port
						</td><td>
							The port on which to contact the server. Required.
						</td></tr><tr><td>
							CIB_encrypted
						</td><td>
							Encrypt network traffic. Defaults to <span class="emphasis"><em>true</em></span>.
						</td></tr></tbody></table></div><h6>Table 9.1. Environment Variables Used to Connect to Remote Instances of the CIB </h6></div><br class="table-break" /><div class="para">
			So if c001n01 is an active cluster node and is listening on 1234 for connections, and someguy is a member of the hacluster group. Then the following would prompt for someguy's password and return the cluster's current configuration:
		</div><pre class="programlisting">
	<strong class="userinput"><code> export CIB_port=1234; export CIB_server=c001n01; export CIB_user=someguy; cibadmin -Q </code></strong>
</pre><div class="para">
			For security reasons, the cluster does not listen remote connections by default. If you wish to allow remote access, you need to set the <code class="literal">remote-tls-port</code> (encrypted) or <code class="literal">remote-clear-port</code> (unencrypted) top-level options (ie. those kept in the cib tag , like <code class="literal">num_updates</code> and <code class="literal">epoch</code>).
		</div><div class="table" id="id2819367"><div class="table-contents"><table summary="Extra top-level CIB options for remote access " border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
							Field
						</th><th>
							Description
						</th></tr></thead><tbody><tr><td>
							remote-tls-port
						</td><td>
							Listen for encrypted remote connections on this port. Default: <span class="emphasis"><em>none</em></span>
						</td></tr><tr><td>
							remote-clear-port
						</td><td>
							Listen for plaintext remote connections on this port. Default: <span class="emphasis"><em>none</em></span>
						</td></tr></tbody></table></div><h6>Table 9.2. Extra top-level CIB options for remote access </h6></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s-rules-recheck.html"><strong>Prev</strong>8.6. Ensuring Time Based Rules Take Effect</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s-recurring-start.html"><strong>Next</strong>9.2. Specifying When Recurring Actions are Perfor...</a></li></ul></body></html>