diff --git a/doc/sphinx/Pacemaker_Remote/baremetal-tutorial.rst b/doc/sphinx/Pacemaker_Remote/baremetal-tutorial.rst index 02a86b816d..df0e9c2bc4 100644 --- a/doc/sphinx/Pacemaker_Remote/baremetal-tutorial.rst +++ b/doc/sphinx/Pacemaker_Remote/baremetal-tutorial.rst @@ -1,341 +1,238 @@ .. index:: single: remote node; walk-through Remote Node Walk-through ------------------------ **What this tutorial is:** An in-depth walk-through of how to get Pacemaker to integrate a remote node into the cluster as a node capable of running cluster resources. **What this tutorial is not:** A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of remote nodes as quickly as possible. -This tutorial requires three machines: two to act as cluster nodes, and -a third to act as the remote node. +Configure Cluster Nodes +####################### + +This walk-through assumes you already have a Pacemaker cluster configured. For examples, we will use a cluster with two cluster nodes named pcmk-1 and pcmk-2. You can substitute whatever your node names are, for however many nodes you have. If you are not familiar with setting up basic Pacemaker clusters, follow the walk-through in the Clusters From Scratch document before attempting this one. + +You will need to add the remote node's hostname (we're using **remote1** in +this tutorial) to the cluster nodes' ``/etc/hosts`` files if you haven't already. +This is required unless you have DNS set up in a way where remote1's address can be +discovered. + +Execute the following on each cluster node, replacing the IP address with the +actual IP address of the remote node. + +.. code-block:: none + + # cat << END >> /etc/hosts + 192.168.122.10 remote1 + END Configure Remote Node ##################### .. index:: single: remote node; firewall Configure Firewall on Remote Node _________________________________ Allow cluster-related services through the local firewall: .. code-block:: none # firewall-cmd --permanent --add-service=high-availability success # firewall-cmd --reload success .. NOTE:: - If you are using iptables directly, or some other firewall solution besides - firewalld, simply open the following ports, which can be used by various + If you are using some other firewall solution besides firewalld, + simply open the following ports, which can be used by various clustering components: TCP ports 2224, 3121, and 21064, and UDP port 5405. If you run into any problems during testing, you might want to disable the firewall and SELinux entirely until you have everything working. This may create significant security issues and should not be performed on machines that will be exposed to the outside world, but may be appropriate during development and testing on a protected host. To disable security measures: .. code-block:: none # setenforce 0 # sed -i.bak "s/SELINUX=enforcing/SELINUX=permissive/g" /etc/selinux/config # systemctl mask firewalld.service # systemctl stop firewalld.service - # iptables --flush Configure pacemaker_remote on Remote Node _________________________________________ Install the pacemaker_remote daemon on the remote node. .. code-block:: none # yum install -y pacemaker-remote resource-agents pcs -Create a location for the shared authentication key: - -.. code-block:: none - - # mkdir -p --mode=0750 /etc/pacemaker - # chgrp haclient /etc/pacemaker - -All nodes (both cluster nodes and remote nodes) must have the same -authentication key installed for the communication to work correctly. -If you already have a key on an existing node, copy it to the new -remote node. Otherwise, create a new key, for example: - -.. code-block:: none - - # dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1 - -Now start and enable the pacemaker_remote daemon on the remote node. - -.. code-block:: none - - # systemctl enable pacemaker_remote.service - # systemctl start pacemaker_remote.service - -Verify the start is successful. - -.. code-block:: none - - # systemctl status pacemaker_remote - pacemaker_remote.service - Pacemaker Remote Service - Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled) - Active: active (running) since Fri 2018-01-12 15:21:20 CDT; 20s ago - Main PID: 21273 (pacemaker_remot) - CGroup: /system.slice/pacemaker_remote.service - └─21273 /usr/sbin/pacemaker-remoted - - Jan 12 15:21:20 remote1 systemd[1]: Starting Pacemaker Remote Service... - Jan 12 15:21:20 remote1 systemd[1]: Started Pacemaker Remote Service. - Jan 12 15:21:20 remote1 pacemaker-remoted[21273]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log - Jan 12 15:21:20 remote1 pacemaker-remoted[21273]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121. - Jan 12 15:21:20 remote1 pacemaker-remoted[21273]: notice: bind_and_listen: Listening on address :: - -Verify Connection to Remote Node -################################ - -Before moving forward, it's worth verifying that the cluster nodes -can contact the remote node on port 3121. Here's a trick you can use. -Connect using ssh from each of the cluster nodes. The connection will get -destroyed, but how it is destroyed tells you whether it worked or not. - -First, add the remote node's hostname (we're using **remote1** in this tutorial) -to the cluster nodes' ``/etc/hosts`` files if you haven't already. This -is required unless you have DNS set up in a way where remote1's address can be -discovered. - -Execute the following on each cluster node, replacing the IP address with the -actual IP address of the remote node. - -.. code-block:: none - - # cat << END >> /etc/hosts - 192.168.122.10 remote1 - END - -If running the ssh command on one of the cluster nodes results in this -output before disconnecting, the connection works: - -.. code-block:: none - - # ssh -p 3121 remote1 - ssh_exchange_identification: read: Connection reset by peer - -If you see one of these, the connection is not working: - -.. code-block:: none - - # ssh -p 3121 remote1 - ssh: connect to host remote1 port 3121: No route to host - -.. code-block:: none - - # ssh -p 3121 remote1 - ssh: connect to host remote1 port 3121: Connection refused - -Once you can successfully connect to the remote node from the both -cluster nodes, move on to setting up Pacemaker on the cluster nodes. - -Configure Cluster Nodes -####################### - -Configure Firewall on Cluster Nodes -___________________________________ - -On each cluster node, allow cluster-related services through the local -firewall, following the same procedure as in `Configure Firewall on Remote Node`_. - -Install Pacemaker on Cluster Nodes +Integrate Remote Node into Cluster __________________________________ -On the two cluster nodes, install the following packages. - -.. code-block:: none - - # yum install -y pacemaker corosync pcs resource-agents - -Copy Authentication Key to Cluster Nodes -________________________________________ - -Create a location for the shared authentication key, -and copy it from any existing node: - -.. code-block:: none - - # mkdir -p --mode=0750 /etc/pacemaker - # chgrp haclient /etc/pacemaker - # scp remote1:/etc/pacemaker/authkey /etc/pacemaker/authkey - -Configure Corosync on Cluster Nodes -___________________________________ - -Corosync handles Pacemaker's cluster membership and messaging. The corosync -config file is located in ``/etc/corosync/corosync.conf``. That config file must be -initialized with information about the two cluster nodes before pacemaker can -start. - -To initialize the corosync config file, execute the following pcs command on -both nodes, filling in the information in <> with your nodes' information. - -.. code-block:: none - - # pcs cluster setup --force --local --name mycluster - -Start Pacemaker on Cluster Nodes -________________________________ - -Start the cluster stack on both cluster nodes using the following command. - -.. code-block:: none - - # pcs cluster start +Integrating a remote node into the cluster is achieved through the +creation of a remote node connection resource. The remote node connection +resource both establishes the connection to the remote node and defines that +the remote node exists. Note that this resource is actually internal to +Pacemaker's controller. A metadata file for this resource can be found in +the ``/usr/lib/ocf/resource.d/pacemaker/remote`` file that describes what options +are available, but there is no actual **ocf:pacemaker:remote** resource agent +script that performs any work. -Verify corosync membership +Before we integrate the remote node, we'll need to authorize it. .. code-block:: none - # pcs status corosync - Membership information - ---------------------- - Nodeid Votes Name - 1 1 node1 (local) + # pcs host auth remote1 -Verify Pacemaker status. At first, the ``pcs cluster status`` output will look -like this. +Now, define the remote node connection resource to our remote node, +**remote1**, using the following command on any cluster node. This +command creates the ocf:pacemaker:remote resource, creates and copies +the key, and enables pacemaker_remote. .. code-block:: none - # pcs status - Cluster name: mycluster - Stack: corosync - Current DC: NONE - Last updated: Fri Jan 12 16:14:05 2018 - Last change: Fri Jan 12 14:02:14 2018 - - 1 node configured - 0 resources configured + # pcs cluster node add-remote remote1 -After about a minute, you should see your two cluster nodes come online. +That's it. After a moment you should see the remote node come online. The final ``pcs status`` output should look something like this, and you can see that it +created the ocf:pacemaker:remote resource: .. code-block:: none # pcs status Cluster name: mycluster - Stack: corosync - Current DC: node1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum - Last updated: Fri Jan 12 16:16:32 2018 - Last change: Fri Jan 12 14:02:14 2018 - - 2 nodes configured - 0 resources configured + Cluster Summary: + * Stack: corosync + * Current DC: pcmk-1 (version 2.0.5-8.el8-ba59be7122) - partition with quorum + * Last updated: Wed Mar 3 11:02:03 2021 + * Last change: Wed Mar 3 11:01:57 2021 by root via cibadmin on pcmk-1 + * 3 nodes configured + * 1 resource instance configured + + Node List: + * Online: [ pcmk-1 pcmk-2 ] + * RemoteOnline: [ remote1 ] + + Full List of Resources: + * remote1 (ocf::pacemaker:remote): Started pcmk-1 - Online: [ node1 node2 ] +How pcs Configures the Remote +############################# -For the sake of this tutorial, we are going to disable stonith to avoid having -to cover fencing device configuration. +To see that it created the key and copied it to all cluster nodes and the +guest, run: .. code-block:: none - # pcs property set stonith-enabled=false - -Integrate Remote Node into Cluster -################################## - -Integrating a remote node into the cluster is achieved through the -creation of a remote node connection resource. The remote node connection -resource both establishes the connection to the remote node and defines that -the remote node exists. Note that this resource is actually internal to -Pacemaker's controller. A metadata file for this resource can be found in -the ``/usr/lib/ocf/resource.d/pacemaker/remote`` file that describes what options -are available, but there is no actual **ocf:pacemaker:remote** resource agent -script that performs any work. + # ls -l /etc/pacemaker -Define the remote node connection resource to our remote node, -**remote1**, using the following command on any cluster node. +To see that it enables pacemaker_remote, run: .. code-block:: none - # pcs resource create remote1 ocf:pacemaker:remote - -That's it. After a moment you should see the remote node come online. - -.. code-block:: none - - Cluster name: mycluster - Stack: corosync - Current DC: node1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum - Last updated: Fri Jan 12 17:13:09 2018 - Last change: Fri Jan 12 17:02:02 2018 - - 3 nodes configured - 1 resources configured - - Online: [ node1 node2 ] - RemoteOnline: [ remote1 ] - - Full list of resources: - - remote1 (ocf::pacemaker:remote): Started node1 - - Daemon Status: - corosync: active/disabled - pacemaker: active/disabled - pcsd: active/enabled + # systemctl status pacemaker_remote + ● pacemaker_remote.service - Pacemaker Remote executor daemon + Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled; vendor preset: disabled) + Active: active (running) since Tue 2021-03-02 10:42:40 EST; 1min 23s ago + Docs: man:pacemaker-remoted + https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemaker_Remote/index.html + Main PID: 1139 (pacemaker-remot) + Tasks: 1 + Memory: 5.4M + CGroup: /system.slice/pacemaker_remote.service + └─1139 /usr/sbin/pacemaker-remoted + + Mar 02 10:42:40 remote1 systemd[1]: Started Pacemaker Remote executor daemon. + Mar 02 10:42:40 remote1 pacemaker-remoted[1139]: notice: Additional logging available in /var/log/pacemaker/pacemaker.log + Mar 02 10:42:40 remote1 pacemaker-remoted[1139]: notice: Starting Pacemaker remote executor + Mar 02 10:42:41 remote1 pacemaker-remoted[1139]: notice: Pacemaker remote executor successfully started and accepting connections Starting Resources on Remote Node ################################# Once the remote node is integrated into the cluster, starting resources on a remote node is the exact same as on cluster nodes. Refer to the `Clusters from Scratch `_ document for examples of resource creation. .. WARNING:: Never involve a remote node connection resource in a resource group, colocation constraint, or order constraint. .. index:: single: remote node; fencing Fencing Remote Nodes #################### Remote nodes are fenced the same way as cluster nodes. No special considerations are required. Configure fencing resources for use with remote nodes the same as you would with cluster nodes. Note, however, that remote nodes can never 'initiate' a fencing action. Only cluster nodes are capable of actually executing a fencing operation against another node. Accessing Cluster Tools from a Remote Node ########################################## Besides allowing the cluster to manage resources on a remote node, pacemaker_remote has one other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools (``crm_resource``, ``crm_mon``, ``crm_attribute``, ``crm_master``, etc.) to work on remote nodes natively. Try it: Run ``crm_mon`` on the remote node after pacemaker has integrated it into the cluster. These tools just work. These means resource agents such as promotable resources (which need access to tools like ``crm_master``) work seamlessly on the remote nodes. Higher-level command shells such as ``pcs`` may have partial support on remote nodes, but it is recommended to run them from a cluster node. + +Troubleshooting a Remote Connection +################################### + +Note: This section should not be done when the remote is connected to the cluster. + +Should connectivity issues occur, it can be worth verifying that the cluster nodes +can contact the remote node on port 3121. Here's a trick you can use. +Connect using ssh from each of the cluster nodes. The connection will get +destroyed, but how it is destroyed tells you whether it worked or not. + +If running the ssh command on one of the cluster nodes results in this +output before disconnecting, the connection works: + +.. code-block:: none + + # ssh -p 3121 remote1 + ssh_exchange_identification: read: Connection reset by peer + +If you see one of these, the connection is not working: + +.. code-block:: none + + # ssh -p 3121 remote1 + ssh: connect to host remote1 port 3121: No route to host + +.. code-block:: none + + # ssh -p 3121 remote1 + ssh: connect to host remote1 port 3121: Connection refused + +Once you can successfully connect to the remote node from the both +cluster nodes, you may move on to setting up Pacemaker on the +cluster nodes. diff --git a/doc/sphinx/Pacemaker_Remote/example.rst b/doc/sphinx/Pacemaker_Remote/example.rst deleted file mode 100644 index 7493c97d82..0000000000 --- a/doc/sphinx/Pacemaker_Remote/example.rst +++ /dev/null @@ -1,133 +0,0 @@ -.. index:: - single: guest node; example - -Guest Node Quick Example ------------------------- - -If you already know how to use Pacemaker, you'll likely be able to grasp this -new concept of guest nodes by reading through this quick example without -having to sort through all the detailed walk-through steps. Here are the key -configuration ingredients that make this possible using libvirt and KVM virtual -guests. These steps strip everything down to the very basics. - -Mile-High View of Configuration Steps -##################################### - -* Give each virtual machine that will be used as a guest node a static network - address and unique hostname. - -* Put the same authentication key with the path ``/etc/pacemaker/authkey`` on - every cluster node and virtual machine. This secures remote communication. - - Run this command if you want to make a somewhat random key: - - .. code-block:: none - - # dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1 - -* Install pacemaker_remote on every virtual machine, enabling it to start at - boot, and if a local firewall is used, allow the node to accept connections - on TCP port 3121. - - .. code-block:: none - - # yum install pacemaker-remote resource-agents - # systemctl enable pacemaker_remote - # firewall-cmd --add-port 3121/tcp --permanent - - .. NOTE:: - - If you just want to see this work, you may want to simply disable the local - firewall and put SELinux in permissive mode while testing. This creates - security risks and should not be done on a production machine exposed to the - Internet, but can be appropriate for a protected test machine. - -* Create a Pacemaker resource to launch each virtual machine, using the - **remote-node** meta-attribute to let Pacemaker know this will be a - guest node capable of running resources. - - .. code-block:: none - - # pcs resource create vm-guest1 VirtualDomain hypervisor="qemu:///system" config="vm-guest1.xml" meta remote-node="guest1" - - The above command will create CIB XML similar to the following: - - .. code-block:: xml - - - - - - - - - - - - - - -In the example above, the meta-attribute **remote-node="guest1"** tells Pacemaker -that this resource is a guest node with the hostname **guest1**. The cluster will -attempt to contact the virtual machine's pacemaker_remote service at the -hostname **guest1** after it launches. - -.. NOTE:: - - The ID of the resource creating the virtual machine (**vm-guest1** in the above - example) 'must' be different from the virtual machine's uname (**guest1** in the - above example). Pacemaker will create an implicit internal resource for the - pacemaker_remote connection to the guest, named with the value of **remote-node**, - so that value cannot be used as the name of any other resource. - -Using a Guest Node -================== - -Guest nodes will show up in ``crm_mon`` output as normal. For example, this is the -``crm_mon`` output after **guest1** is integrated into the cluster: - -.. code-block:: none - - Stack: corosync - Current DC: node1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum - Last updated: Fri Jan 12 13:52:39 2018 - Last change: Fri Jan 12 13:25:17 2018 via pacemaker-controld on node1 - - 2 nodes configured - 2 resources configured - - Online: [ node1 guest1] - - vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1 - -Now, you could place a resource, such as a webserver, on **guest1**: - -.. code-block:: none - - # pcs resource create webserver apache params configfile=/etc/httpd/conf/httpd.conf op monitor interval=30s - # pcs constraint location webserver prefers guest1 - -Now, the crm_mon output would show: - -.. code-block:: none - - Stack: corosync - Current DC: node1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum - Last updated: Fri Jan 12 13:52:39 2018 - Last change: Fri Jan 12 13:25:17 2018 via pacemaker-controld on node1 - - 2 nodes configured - 2 resources configured - - Online: [ node1 guest1] - - vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1 - webserver (ocf::heartbeat::apache): Started guest1 - -It is worth noting that after **guest1** is integrated into the cluster, nearly all the -Pacemaker command-line tools immediately become available to the guest node. -This means things like ``crm_mon``, ``crm_resource``, and ``crm_attribute`` will work -natively on the guest node, as long as the connection between the guest node -and a cluster node exists. This is particularly important for any promotable -clone resources executing on the guest node that need access to ``crm_master`` to -set transient attributes. diff --git a/doc/sphinx/Pacemaker_Remote/index.rst b/doc/sphinx/Pacemaker_Remote/index.rst index 68322b45d8..de8e898ad9 100644 --- a/doc/sphinx/Pacemaker_Remote/index.rst +++ b/doc/sphinx/Pacemaker_Remote/index.rst @@ -1,48 +1,44 @@ Pacemaker Remote ================ *Scaling High Availablity Clusters* Abstract -------- This document exists as both a reference and deployment guide for the Pacemaker Remote service. The example commands in this document will use: * |REMOTE_DISTRO| |REMOTE_DISTRO_VER| as the host operating system * Pacemaker Remote to perform resource management within guest nodes and remote nodes * KVM for virtualization * libvirt to manage guest nodes * Corosync to provide messaging and membership services on cluster nodes -* Pacemaker 1.1.16 [#]_ to perform resource management on cluster nodes +* Pacemaker 2 to perform resource management on cluster nodes * pcs as the cluster configuration toolset The concepts are the same for other distributions, virtualization platforms, toolsets, and messaging layers, and should be easily adaptable. Table of Contents ----------------- .. toctree:: :maxdepth: 3 :numbered: intro - example options kvm-tutorial baremetal-tutorial alternatives Index ----- * :ref:`genindex` * :ref:`search` - -.. [#] While this guide is part of the document set for Pacemaker 2.0, it - demonstrates the version available in the standard |REMOTE_DISTRO| repositories diff --git a/doc/sphinx/Pacemaker_Remote/intro.rst b/doc/sphinx/Pacemaker_Remote/intro.rst index 9c5dab81a0..93af71b1f7 100644 --- a/doc/sphinx/Pacemaker_Remote/intro.rst +++ b/doc/sphinx/Pacemaker_Remote/intro.rst @@ -1,186 +1,186 @@ Scaling a Pacemaker Cluster --------------------------- Overview ######## In a basic Pacemaker high-availability cluster [#]_ each node runs the full cluster stack of Corosync and all Pacemaker components. This allows great flexibility but limits scalability to around 16 nodes. To allow for scalability to dozens or even hundreds of nodes, Pacemaker allows nodes not running the full cluster stack to integrate into the cluster and have the cluster manage their resources as if they were a cluster node. Terms ##### .. index:: single: cluster node single: node; cluster node **cluster node** A node running the full high-availability stack of corosync and all Pacemaker components. Cluster nodes may run cluster resources, run all Pacemaker command-line tools (``crm_mon``, ``crm_resource`` and so on), execute fencing actions, count toward cluster quorum, and serve as the cluster's Designated Controller (DC). -.. index:: pacemaker_remoted +.. index:: pacemaker-remoted -**pacemaker_remoted** +**pacemaker-remoted** A small service daemon that allows a host to be used as a Pacemaker node - without running the full cluster stack. Nodes running ``pacemaker_remoted`` + without running the full cluster stack. Nodes running ``pacemaker-remoted`` may run cluster resources and most command-line tools, but cannot perform other functions of full cluster nodes such as fencing execution, quorum - voting, or DC eligibility. The ``pacemaker_remoted`` daemon is an enhanced - version of Pacemaker's local resource management daemon (LRMD). + voting, or DC eligibility. The ``pacemaker-remoted`` daemon is an enhanced + version of Pacemaker's local executor daemon (pacemaker-execd). .. index:: single: remote node single: node; remote node **pacemaker_remote** - The name of the systemd service that manages ``pacemaker_remoted`` + The name of the systemd service that manages ``pacemaker-remoted`` **Pacemaker Remote** A way to refer to the general technology implementing nodes running - ``pacemaker_remoted``, including the cluster-side implementation + ``pacemaker-remoted``, including the cluster-side implementation and the communication protocol between them. **remote node** - A physical host running ``pacemaker_remoted``. Remote nodes have a special + A physical host running ``pacemaker-remoted``. Remote nodes have a special resource that manages communication with the cluster. This is sometimes referred to as the *bare metal* case. .. index:: single: guest node single: node; guest node **guest node** - A virtual host running ``pacemaker_remoted``. Guest nodes differ from remote + A virtual host running ``pacemaker-remoted``. Guest nodes differ from remote nodes mainly in that the guest node is itself a resource that the cluster manages. .. NOTE:: *Remote* in this document refers to the node not being a part of the underlying corosync cluster. It has nothing to do with physical proximity. Remote nodes and guest nodes are subject to the same latency requirements as cluster nodes, which means they are typically in the same data center. .. NOTE:: It is important to distinguish the various roles a virtual machine can serve in Pacemaker clusters: * A virtual machine can run the full cluster stack, in which case it is a cluster node and is not itself managed by the cluster. * A virtual machine can be managed by the cluster as a resource, without the cluster having any awareness of the services running inside the virtual machine. The virtual machine is *opaque* to the cluster. - * A virtual machine can be a cluster resource, and run ``pacemaker_remoted`` + * A virtual machine can be a cluster resource, and run ``pacemaker-remoted`` to make it a guest node, allowing the cluster to manage services inside it. The virtual machine is *transparent* to the cluster. .. index:: single: virtual machine; as guest node Guest Nodes ########### **"I want a Pacemaker cluster to manage virtual machine resources, but I also want Pacemaker to be able to manage the resources that live within those virtual machines."** -Without ``pacemaker_remoted``, the possibilities for implementing the above use +Without ``pacemaker-remoted``, the possibilities for implementing the above use case have significant limitations: * The cluster stack could be run on the physical hosts only, which loses the ability to monitor resources within the guests. * A separate cluster could be on the virtual guests, which quickly hits scalability issues. * The cluster stack could be run on the guests using the same cluster as the physical hosts, which also hits scalability issues and complicates fencing. -With ``pacemaker_remoted``: +With ``pacemaker-remoted``: * The physical hosts are cluster nodes (running the full cluster stack). -* The virtual machines are guest nodes (running ``pacemaker_remoted``). +* The virtual machines are guest nodes (running ``pacemaker-remoted``). Nearly zero configuration is required on the virtual machine. * The cluster stack on the cluster nodes launches the virtual machines and - immediately connects to ``pacemaker_remoted`` on them, allowing the + immediately connects to ``pacemaker-remoted`` on them, allowing the virtual machines to integrate into the cluster. The key difference here between the guest nodes and the cluster nodes is that the guest nodes do not run the cluster stack. This means they will never become the DC, initiate fencing actions or participate in quorum voting. On the other hand, this also means that they are not bound to the scalability limits associated with the cluster stack (no 16-node corosync member limits to deal with). That isn't to say that guest nodes can scale indefinitely, but it is known that guest nodes scale horizontally much further than cluster nodes. Other than the quorum limitation, these guest nodes behave just like cluster nodes with respect to resource management. The cluster is fully capable of managing and monitoring resources on each guest node. You can build constraints against guest nodes, put them in standby, or do whatever else you'd expect to be able to do with cluster nodes. They even show up in ``crm_mon`` output as nodes. To solidify the concept, below is an example that is very similar to an actual deployment we test in our developer environment to verify guest node scalability: * 16 cluster nodes running the full Corosync + Pacemaker stack -* 64 Pacemaker-managed virtual machine resources running ``pacemaker_remoted`` +* 64 Pacemaker-managed virtual machine resources running ``pacemaker-remoted`` configured as guest nodes * 64 Pacemaker-managed webserver and database resources configured to run on the 64 guest nodes With this deployment, you would have 64 webservers and databases running on 64 virtual machines on 16 hardware nodes, all of which are managed and monitored by -the same Pacemaker deployment. It is known that ``pacemaker_remoted`` can scale +the same Pacemaker deployment. It is known that ``pacemaker-remoted`` can scale to these lengths and possibly much further depending on the specific scenario. Remote Nodes ############ **"I want my traditional high-availability cluster to scale beyond the limits imposed by the corosync messaging layer."** Ultimately, the primary advantage of remote nodes over cluster nodes is scalability. There are likely some other use cases related to geographically distributed HA clusters that remote nodes may serve a purpose in, but those use cases are not well understood at this point. Like guest nodes, remote nodes will never become the DC, initiate fencing actions or participate in quorum voting. That is not to say, however, that fencing of a remote node works any differently than that of a cluster node. The Pacemaker scheduler understands how to fence remote nodes. As long as a fencing device exists, the cluster is capable of ensuring remote nodes are fenced in the exact same way as cluster nodes. Expanding the Cluster Stack ########################### -With ``pacemaker_remoted``, the traditional view of the high-availability stack +With ``pacemaker-remoted``, the traditional view of the high-availability stack can be expanded to include a new layer: Traditional HA Stack ____________________ .. image:: images/pcmk-ha-cluster-stack.png :alt: Traditional Pacemaker+Corosync Stack :align: center HA Stack With Guest Nodes _________________________ .. image:: images/pcmk-ha-remote-stack.png - :alt: Pacemaker+Corosync Stack with pacemaker_remoted + :alt: Pacemaker+Corosync Stack with pacemaker-remoted :align: center .. [#] See the ``_ Pacemaker documentation, especially *Clusters From Scratch* and *Pacemaker Explained*. diff --git a/doc/sphinx/Pacemaker_Remote/kvm-tutorial.rst b/doc/sphinx/Pacemaker_Remote/kvm-tutorial.rst index 210af8021a..cb01d36530 100644 --- a/doc/sphinx/Pacemaker_Remote/kvm-tutorial.rst +++ b/doc/sphinx/Pacemaker_Remote/kvm-tutorial.rst @@ -1,623 +1,598 @@ .. index:: single: guest node; walk-through Guest Node Walk-through ----------------------- **What this tutorial is:** An in-depth walk-through of how to get Pacemaker to manage a KVM guest instance and integrate that guest into the cluster as a guest node. **What this tutorial is not:** A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of guest nodes as quickly as possible. -Configure the Physical Host -########################### - -.. NOTE:: - - For this example, we will use a single physical host named **example-host**. - A production cluster would likely have multiple physical hosts, in which case - you would run the commands here on each one, unless noted otherwise. - -Configure Firewall on Host -__________________________ - -On the physical host, allow cluster-related services through the local firewall: - -.. code-block:: none - - # firewall-cmd --permanent --add-service=high-availability - success - # firewall-cmd --reload - success - -.. NOTE:: - - If you are using iptables directly, or some other firewall solution besides - firewalld, simply open the following ports, which can be used by various - clustering components: TCP ports 2224, 3121, and 21064, and UDP port 5405. - - If you run into any problems during testing, you might want to disable - the firewall and SELinux entirely until you have everything working. - This may create significant security issues and should not be performed on - machines that will be exposed to the outside world, but may be appropriate - during development and testing on a protected host. - - To disable security measures: - - .. code-block:: none - - [root@pcmk-1 ~]# setenforce 0 - [root@pcmk-1 ~]# sed -i.bak "s/SELINUX=enforcing/SELINUX=permissive/g" /etc/selinux/config - [root@pcmk-1 ~]# systemctl mask firewalld.service - [root@pcmk-1 ~]# systemctl stop firewalld.service - [root@pcmk-1 ~]# iptables --flush - -Install Cluster Software -________________________ - -.. code-block:: none - - # yum install -y pacemaker corosync pcs resource-agents - -Configure Corosync -__________________ - -Corosync handles pacemaker's cluster membership and messaging. The corosync -config file is located in ``/etc/corosync/corosync.conf``. That config file must -be initialized with information about the cluster nodes before pacemaker can -start. - -To initialize the corosync config file, execute the following ``pcs`` command, -replacing the cluster name and hostname as desired: - -.. code-block:: none - - # pcs cluster setup --force --local --name mycluster example-host - -.. NOTE:: - - If you have multiple physical hosts, you would execute the setup command on - only one host, but list all of them at the end of the command. - -Configure Pacemaker for Remote Node Communication -_________________________________________________ - -Create a place to hold an authentication key for use with pacemaker_remote: - -.. code-block:: none - - # mkdir -p --mode=0750 /etc/pacemaker - # chgrp haclient /etc/pacemaker - -Generate a key: - -.. code-block:: none - - # dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1 - -.. NOTE:: - - If you have multiple physical hosts, you would generate the key on only one - host, and copy it to the same location on all hosts. - -Verify Cluster Software -_______________________ - -Start the cluster - -.. code-block:: none - - # pcs cluster start - -Verify corosync membership - -.. code-block:: none - - # pcs status corosync - - Membership information - ---------------------- - Nodeid Votes Name - 1 1 example-host (local) - -Verify pacemaker status. At first, the output will look like this: - -.. code-block:: none - - # pcs status - Cluster name: mycluster - WARNING: no stonith devices and stonith-enabled is not false - Stack: corosync - Current DC: NONE - Last updated: Fri Jan 12 15:18:32 2018 - Last change: Fri Jan 12 12:42:21 2018 by root via cibadmin on example-host - - 1 node configured - 0 resources configured - - Node example-host: UNCLEAN (offline) - - No active resources - - Daemon Status: - corosync: active/disabled - pacemaker: active/disabled - pcsd: active/enabled - -After a short amount of time, you should see your host as a single node in the -cluster: - -.. code-block:: none - - # pcs status - Cluster name: mycluster - WARNING: no stonith devices and stonith-enabled is not false - Stack: corosync - Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition WITHOUT quorum - Last updated: Fri Jan 12 15:20:05 2018 - Last change: Fri Jan 12 12:42:21 2018 by root via cibadmin on example-host - - 1 node configured - 0 resources configured - - Online: [ example-host ] - - No active resources - - Daemon Status: - corosync: active/disabled - pacemaker: active/disabled - pcsd: active/enabled - -Disable STONITH and Quorum -__________________________ - -Now, enable the cluster to work without quorum or stonith. This is required -for the sake of getting this tutorial to work with a single cluster node. - -.. code-block:: none - - # pcs property set stonith-enabled=false - # pcs property set no-quorum-policy=ignore - -.. WARNING:: - - The use of ``stonith-enabled=false`` is completely inappropriate for a production - cluster. It tells the cluster to simply pretend that failed nodes are safely - powered off. Some vendors will refuse to support clusters that have STONITH - disabled. We disable STONITH here only to focus the discussion on - pacemaker_remote, and to be able to use a single physical host in the example. - -Now, the status output should look similar to this: - -.. code-block:: none - - # pcs status - Cluster name: mycluster - Stack: corosync - Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum - Last updated: Fri Jan 12 15:22:49 2018 - Last change: Fri Jan 12 15:22:46 2018 by root via cibadmin on example-host +Configure Cluster Nodes +####################### - 1 node configured - 0 resources configured +This walk-through assumes you already have a Pacemaker cluster configured. For examples, we will use a cluster with two cluster nodes named pcmk-1 and pcmk-2. You can substitute whatever your node names are, for however many nodes you have. If you are not familiar with setting up basic Pacemaker clusters, follow the walk-through in the Clusters From Scratch document before attempting this one. - Online: [ example-host ] +You will need to add the remote node's hostname (we're using **guest1** in +this tutorial) to the cluster nodes' ``/etc/hosts`` files if you haven't already. +This is required unless you have DNS set up in a way where guest1's address can be +discovered. - No active resources - - Daemon Status: - corosync: active/disabled - pacemaker: active/disabled - pcsd: active/enabled - -Go ahead and stop the cluster for now after verifying everything is in order. +Execute the following on each cluster node, replacing the IP address with the +actual IP address of the remote node. .. code-block:: none - # pcs cluster stop --force + # cat << END >> /etc/hosts + 192.168.122.10 guest1 + END Install Virtualization Software _______________________________ -.. code-block:: none +On each node within your cluster, install virt-install, libvirt, and qemu-kvm. +Start and enable libvirtd. - # yum install -y kvm libvirt qemu-system qemu-kvm bridge-utils virt-manager - # systemctl enable libvirtd.service + .. code-block:: none + + # yum install -y virt-install libvirt qemu-kvm + # systemctl start libvirtd + # systemctl enable libvirtd Reboot the host. .. NOTE:: While KVM is used in this example, any virtualization platform with a Pacemaker resource agent can be used to create a guest node. The resource agent needs only to support usual commands (start, stop, etc.); Pacemaker implements the **remote-node** meta-attribute, independent of the agent. Configure the KVM guest ####################### Create Guest ____________ -We will not outline here the installation steps required to create a KVM -guest. There are plenty of tutorials available elsewhere that do that. -Just be sure to configure the guest with a hostname and a static IP address -(as an example here, we will use guest1 and 192.168.122.10). +Create a KVM guest to use as a guest node. Be sure to configure the guest with a +hostname and a static IP address (as an example here, we will use guest1 and 192.168.122.10). +Here's an example way to create a guest: + +* Download an .iso file from the `CentOS Mirrors List `_ into a directory on your cluster node. + +* Run the following command, using your own path for the **location** flag: + + .. code-block:: none + + # virt-install \ + --name guest-vm \ + --ram 1024 \ + --disk path=./guest-vm.qcow2,size=1 \ + --vcpus 2 \ + --os-type linux \ + --os-variant centos-stream8\ + --network bridge=virbr0 \ + --graphics none \ + --console pty,target_type=serial \ + --location \ + --extra-args 'console=ttyS0,115200n8 serial' .. index:: single: guest node; firewall Configure Firewall on Guest ___________________________ -On each guest, allow cluster-related services through the local firewall, -following the same procedure as in `Configure Firewall on Host`_. +On each guest, allow cluster-related services through the local firewall. Verify Connectivity ___________________ At this point, you should be able to ping and ssh into guests from hosts, and vice versa. -Configure pacemaker_remoted -___________________________ - -Install ``pacemaker_remoted``, and enable it to run at start-up. Here, we also -install the ``pacemaker`` package; it is not required, but it contains the -dummy resource agent that we will use later for testing. - -.. code-block:: none - - # yum install -y pacemaker pacemaker-remote resource-agents - # systemctl enable pacemaker_remote.service - -Copy the authentication key from a host: - -.. code-block:: none - - # mkdir -p --mode=0750 /etc/pacemaker - # chgrp haclient /etc/pacemaker - # scp root@example-host:/etc/pacemaker/authkey /etc/pacemaker - -Start ``pacemaker_remoted``, and verify the start was successful: - -.. code-block:: none - - # systemctl start pacemaker_remote - # systemctl status pacemaker_remote - - pacemaker_remote.service - Pacemaker Remote Service - Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled) - Active: active (running) since Thu 2013-03-14 18:24:04 EDT; 2min 8s ago - Main PID: 1233 (pacemaker_remot) - CGroup: name=systemd:/system/pacemaker_remote.service - └─1233 /usr/sbin/pacemaker-remoted - - Mar 14 18:24:04 guest1 systemd[1]: Starting Pacemaker Remote Service... - Mar 14 18:24:04 guest1 systemd[1]: Started Pacemaker Remote Service. - Mar 14 18:24:04 guest1 pacemaker-remoted[1233]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121. - -Verify Host Connection to Guest -_______________________________ - -Before moving forward, it's worth verifying that the host can contact the guest -on port 3121. Here's a trick you can use. Connect using ssh from the host. The -connection will get destroyed, but how it is destroyed tells you whether it -worked or not. - -First add guest1 to the host machine's ``/etc/hosts`` file if you haven't -already. This is required unless you have DNS setup in a way where **guest1**'s -address can be discovered. - -.. code-block:: none - - # cat << END >> /etc/hosts - 192.168.122.10 guest1 - END - -If running the ``ssh`` command on one of the cluster nodes results in this -output before disconnecting, the connection works: - -.. code-block:: none - - # ssh -p 3121 guest1 - ssh_exchange_identification: read: Connection reset by peer - -If you see one of these, the connection is not working: +Configure pacemaker_remote on Guest Node +________________________________________ -.. code-block:: none - - # ssh -p 3121 guest1 - ssh: connect to host guest1 port 3121: No route to host +Install the pacemaker_remote daemon on the guest node. Here, +we also install the ``pacemaker`` package; it is not required, but +it contains the dummy resource agent that we will use later +for testing. .. code-block:: none - # ssh -p 3121 guest1 - ssh: connect to host guest1 port 3121: Connection refused - -Once you can successfully connect to the guest from the host, shutdown the -guest. Pacemaker will be managing the virtual machine from this point forward. + # yum install -y pacemaker-remote resource-agents pcs pacemaker Integrate Guest into Cluster ############################ Now the fun part, integrating the virtual machine you've just created into the cluster. It is incredibly simple. Start the Cluster _________________ On the host, start Pacemaker. .. code-block:: none # pcs cluster start -Wait for the host to become the DC. The output of ``pcs status`` should look -as it did in `Disable Stonith and Quorum`_. +Wait for the host to become the DC. -Integrate as Guest Node -_______________________ +Integrate Guest Node into Cluster +_________________________________ -If you didn't already do this earlier in the verify host to guest connection -section, add the KVM guest's IP address to the host's ``/etc/hosts`` file so we -can connect by hostname. For this example: +We will use the following command, which creates the VirtualDomain resource, +creates and copies the key, and enables pacemaker_remote: .. code-block:: none - # cat << END >> /etc/hosts - 192.168.122.10 guest1 - END + # pcs cluster node add-guest guest1 -We will use the **VirtualDomain** resource agent for the management of the -virtual machine. This agent requires the virtual machine's XML config to be -dumped to a file on disk. To do this, pick out the name of the virtual machine -you just created from the output of this list. +Once the **vm-guest1** resource is started you will see **guest1** appear in the +``pcs status`` output as a node. The final ``pcs status`` output should look +something like this, and you can see that it created the VirtualDomain resource: .. code-block:: none - # virsh list --all - Id Name State - ---------------------------------------------------- - - guest1 shut off - -In my case I named it **guest1**. Dump the XML to a file somewhere on the host -using the following command. + # pcs status + Cluster name: mycluster + + Cluster Summary: + * Stack: corosync + * Current DC: pcmk-1 (version 2.0.5-8.el8-ba59be7122) - partition with quorum + * Last updated: Wed Mar 17 08:37:37 2021 + * Last change: Wed Mar 17 08:31:01 2021 by root via cibadmin on pcmk-1 + * 3 nodes configured + * 2 resource instances configured + + Node List: + * Online: [ pcmk-1 pcmk-2 ] + * GuestOnline: [ guest1@pcmk-1 ] + + Full List of Resources: + * vm-guest1 (ocf::heartbeat:VirtualDomain): pcmk-1 -.. code-block:: none + Daemon Status: + corosync: active/disabled + pacemaker: active/disabled + pcsd: active/enabled - # virsh dumpxml guest1 > /etc/pacemaker/guest1.xml +How pcs Configures the Guest +____________________________ -Now just register the resource with Pacemaker, and you're set! +To see that it created the key and copied it to all cluster nodes and the +guest, run: .. code-block:: none - # pcs resource create vm-guest1 VirtualDomain hypervisor="qemu:///system" \ - config="/etc/pacemaker/guest1.xml" meta remote-node=guest1 + # ls -l /etc/pacemaker -.. NOTE:: +To see that it enables pacemaker_remote, run: - This example puts the guest XML under ``/etc/pacemaker`` because the - permissions and SELinux labeling should not need any changes. - If you run into trouble with this or any step, try disabling SELinux - with ``setenforce 0``. If it works after that, see SELinux documentation - for how to troubleshoot, if you wish to reenable SELinux. +.. code-block:: none + # systemctl status pacemaker_remote + + ● pacemaker_remote.service - Pacemaker Remote executor daemon + Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled; vendor preset: disabled) + Active: active (running) since Wed 2021-03-17 08:31:01 EDT; 1min 5s ago + Docs: man:pacemaker-remoted + https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/ Pacemaker_Remote/index.html + Main PID: 90160 (pacemaker-remot) + Tasks: 1 + Memory: 1.4M + CGroup: /system.slice/pacemaker_remote.service + └─90160 /usr/sbin/pacemaker-remoted + + Mar 17 08:31:01 guest1 systemd[1]: Started Pacemaker Remote executor daemon. + Mar 17 08:31:01 guest1 pacemaker-remoted[90160]: notice: Additional logging available in /var/log/pacemaker/pacemaker.log + Mar 17 08:31:01 guest1 pacemaker-remoted[90160]: notice: Starting Pacemaker remote executor + Mar 17 08:31:01 guest1 pacemaker-remoted[90160]: notice: Pacemaker remote executor successfully started and accepting connections .. NOTE:: Pacemaker will automatically monitor pacemaker_remote connections for failure, so it is not necessary to create a recurring monitor on the **VirtualDomain** resource. -Once the **vm-guest1** resource is started you will see **guest1** appear in the -``pcs status`` output as a node. The final ``pcs status`` output should look -something like this. - -.. code-block:: none - - # pcs status - Cluster name: mycluster - Stack: corosync - Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum - Last updated: Fri Jan 12 18:00:45 2018 - Last change: Fri Jan 12 17:53:44 2018 by root via crm_resource on example-host - - 2 nodes configured - 2 resources configured - - Online: [ example-host ] - GuestOnline: [ guest1@example-host ] - - Full list of resources: - - vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host - - Daemon Status: - corosync: active/disabled - pacemaker: active/disabled - pcsd: active/enabled - Starting Resources on KVM Guest -_______________________________ +############################### The commands below demonstrate how resources can be executed on both the guest node and the cluster node. Create a few Dummy resources. Dummy resources are real resource agents used just for testing purposes. They actually execute on the host they are assigned to just like an apache server or database would, except their execution just means a file was created. When the resource is stopped, that the file it created is removed. .. code-block:: none # pcs resource create FAKE1 ocf:pacemaker:Dummy # pcs resource create FAKE2 ocf:pacemaker:Dummy # pcs resource create FAKE3 ocf:pacemaker:Dummy # pcs resource create FAKE4 ocf:pacemaker:Dummy # pcs resource create FAKE5 ocf:pacemaker:Dummy Now check your ``pcs status`` output. In the resource section, you should see something like the following, where some of the resources started on the cluster node, and some started on the guest node. .. code-block:: none - Full list of resources: - - vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host - FAKE1 (ocf::pacemaker:Dummy): Started guest1 - FAKE2 (ocf::pacemaker:Dummy): Started guest1 - FAKE3 (ocf::pacemaker:Dummy): Started example-host - FAKE4 (ocf::pacemaker:Dummy): Started guest1 - FAKE5 (ocf::pacemaker:Dummy): Started example-host + Full List of Resources: + * vm-guest1 (ocf::heartbeat:VirtualDomain): Started pcmk-1 + * FAKE1 (ocf::pacemaker:Dummy): Started guest1 + * FAKE2 (ocf::pacemaker:Dummy): Started guest1 + * FAKE3 (ocf::pacemaker:Dummy): Started pcmk-1 + * FAKE4 (ocf::pacemaker:Dummy): Started guest1 + * FAKE5 (ocf::pacemaker:Dummy): Started pcmk-1 The guest node, **guest1**, reacts just like any other node in the cluster. For example, pick out a resource that is running on your cluster node. For my purposes, I am picking FAKE3 from the output above. We can force FAKE3 to run on **guest1** in the exact same way we would any other node. .. code-block:: none # pcs constraint location FAKE3 prefers guest1 Now, looking at the bottom of the `pcs status` output you'll see FAKE3 is on **guest1**. .. code-block:: none - Full list of resources: - - vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host - FAKE1 (ocf::pacemaker:Dummy): Started guest1 - FAKE2 (ocf::pacemaker:Dummy): Started guest1 - FAKE3 (ocf::pacemaker:Dummy): Started guest1 - FAKE4 (ocf::pacemaker:Dummy): Started example-host - FAKE5 (ocf::pacemaker:Dummy): Started example-host + Full List of Resources: + * vm-guest1 (ocf::heartbeat:VirtualDomain): Started pcmk-1 + * FAKE1 (ocf::pacemaker:Dummy): Started guest1 + * FAKE2 (ocf::pacemaker:Dummy): Started guest1 + * FAKE3 (ocf::pacemaker:Dummy): Started guest1 + * FAKE4 (ocf::pacemaker:Dummy): Started pcmk-1 + * FAKE5 (ocf::pacemaker:Dummy): Started pcmk-1 Testing Recovery and Fencing -____________________________ +############################ Pacemaker's scheduler is smart enough to know fencing guest nodes associated with a virtual machine means shutting off/rebooting the virtual machine. No special configuration is necessary to make this happen. If you are interested in testing this functionality out, trying stopping the guest's pacemaker_remote daemon. This would be equivalent of abruptly terminating a cluster node's corosync membership without properly shutting it down. ssh into the guest and run this command. .. code-block:: none # kill -9 $(pidof pacemaker-remoted) Within a few seconds, your ``pcs status`` output will show a monitor failure, and the **guest1** node will not be shown while it is being recovered. .. code-block:: none # pcs status Cluster name: mycluster - Stack: corosync - Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum - Last updated: Fri Jan 12 18:08:35 2018 - Last change: Fri Jan 12 18:07:00 2018 by root via cibadmin on example-host - - 2 nodes configured - 7 resources configured - - Online: [ example-host ] - - Full list of resources: - - vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host - FAKE1 (ocf::pacemaker:Dummy): Stopped - FAKE2 (ocf::pacemaker:Dummy): Stopped - FAKE3 (ocf::pacemaker:Dummy): Stopped - FAKE4 (ocf::pacemaker:Dummy): Started example-host - FAKE5 (ocf::pacemaker:Dummy): Started example-host + + Cluster Summary: + * Stack: corosync + * Current DC: pcmk-1 (version 2.0.5-8.el8-ba59be7122) - partition with quorum + * Last updated: Wed Mar 17 08:37:37 2021 + * Last change: Wed Mar 17 08:31:01 2021 by root via cibadmin on pcmk-1 + * 3 nodes configured + * 7 resource instances configured + + Node List: + * Online: [ pcmk-1 pcmk-2 ] + * GuestOnline: [ guest1@pcmk-1 ] + + Full List of Resources: + * vm-guest1 (ocf::heartbeat:VirtualDomain): pcmk-1 + * FAKE1 (ocf::pacemaker:Dummy): Stopped + * FAKE2 (ocf::pacemaker:Dummy): Stopped + * FAKE3 (ocf::pacemaker:Dummy): Stopped + * FAKE4 (ocf::pacemaker:Dummy): Started pcmk-1 + * FAKE5 (ocf::pacemaker:Dummy): Started pcmk-1 Failed Actions: - * guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none', - last-rc-change='Fri Jan 12 18:08:29 2018', queued=0ms, exec=0ms + * guest1_monitor_30000 on pcmk-1 'unknown error' (1): call=8, status=Error, exitreason='none', + last-rc-change='Wed Mar 17 08:32:01 2021', queued=0ms, exec=0ms Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled + .. NOTE:: A guest node involves two resources: the one you explicitly configured creates the guest, and Pacemaker creates an implicit resource for the pacemaker_remote connection, which will be named the same as the value of the **remote-node** attribute of the explicit resource. When we killed pacemaker_remote, it is the implicit resource that failed, which is why the failed action starts with **guest1** and not **vm-guest1**. Once recovery of the guest is complete, you'll see it automatically get re-integrated into the cluster. The final ``pcs status`` output should look something like this. .. code-block:: none + # pcs status Cluster name: mycluster - Stack: corosync - Current DC: example-host (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum - Last updated: Fri Jan 12 18:18:30 2018 - Last change: Fri Jan 12 18:07:00 2018 by root via cibadmin on example-host - - 2 nodes configured - 7 resources configured - - Online: [ example-host ] - GuestOnline: [ guest1@example-host ] - - Full list of resources: - - vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host - FAKE1 (ocf::pacemaker:Dummy): Started guest1 - FAKE2 (ocf::pacemaker:Dummy): Started guest1 - FAKE3 (ocf::pacemaker:Dummy): Started guest1 - FAKE4 (ocf::pacemaker:Dummy): Started example-host - FAKE5 (ocf::pacemaker:Dummy): Started example-host + + Cluster Summary: + * Stack: corosync + * Current DC: pcmk-1 (version 2.0.5-8.el8-ba59be7122) - partition with quorum + * Last updated: Wed Mar 17 08:37:37 2021 + * Last change: Wed Mar 17 08:31:01 2021 by root via cibadmin on pcmk-1 + * 3 nodes configured + * 7 resource instances configured + + Node List: + * Online: [ pcmk-1 pcmk-2 ] + * GuestOnline: [ guest1@pcmk-1 ] + + Full List of Resources: + * vm-guest1 (ocf::heartbeat:VirtualDomain): pcmk-1 + * FAKE1 (ocf::pacemaker:Dummy): Stopped + * FAKE2 (ocf::pacemaker:Dummy): Stopped + * FAKE3 (ocf::pacemaker:Dummy): Stopped + * FAKE4 (ocf::pacemaker:Dummy): Started pcmk-1 + * FAKE5 (ocf::pacemaker:Dummy): Started pcmk-1 Failed Actions: - * guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none', + * guest1_monitor_30000 on pcmk-1 'unknown error' (1): call=8, status=Error, exitreason='none', last-rc-change='Fri Jan 12 18:08:29 2018', queued=0ms, exec=0ms Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled Normally, once you've investigated and addressed a failed action, you can clear the failure. However Pacemaker does not yet support cleanup for the implicitly created connection resource while the explicit resource is active. If you want to clear the failed action from the status output, stop the guest resource before clearing it. For example: .. code-block:: none # pcs resource disable vm-guest1 --wait # pcs resource cleanup guest1 # pcs resource enable vm-guest1 Accessing Cluster Tools from Guest Node -_______________________________________ +####################################### Besides allowing the cluster to manage resources on a guest node, pacemaker_remote has one other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools (``crm_resource``, ``crm_mon``, ``crm_attribute``, ``crm_master``, etc.) to work on guest nodes natively. Try it: Run ``crm_mon`` on the guest after pacemaker has integrated the guest node into the cluster. These tools just work. This means resource agents such as promotable resources (which need access to tools like ``crm_master``) work seamlessly on the guest nodes. Higher-level command shells such as ``pcs`` may have partial support on guest nodes, but it is recommended to run them from a cluster node. + +Guest nodes will show up in ``crm_mon`` output as normal. For example, this is the +``crm_mon`` output after **guest1** is integrated into the cluster: + +.. code-block:: none + + Cluster name: mycluster + + Cluster Summary: + * Stack: corosync + * Current DC: pcmk-1 (version 2.0.5-8.el8-ba59be7122) - partition with quorum + * Last updated: Wed Mar 17 08:37:37 2021 + * Last change: Wed Mar 17 08:31:01 2021 by root via cibadmin on pcmk-1 + * 2 nodes configured + * 2 resource instances configured + + Node List: + * Online: [ pcmk-1 ] + * GuestOnline: [ guest1@pcmk-1 ] + + Full List of Resources: + * vm-guest1 (ocf::heartbeat:VirtualDomain): Started pcmk-1 + +Now, you could place a resource, such as a webserver, on **guest1**: + +.. code-block:: none + + # pcs resource create webserver apache params configfile=/etc/httpd/conf/httpd.conf op monitor interval=30s + # pcs constraint location webserver prefers guest1 + +Now, the crm_mon output would show: + +.. code-block:: none + + Cluster name: mycluster + + Cluster Summary: + * Stack: corosync + * Current DC: pcmk-1 (version 2.0.5-8.el8-ba59be7122) - partition with quorum + * Last updated: Wed Mar 17 08:38:37 2021 + * Last change: Wed Mar 17 08:35:01 2021 by root via cibadmin on pcmk-1 + * 2 nodes configured + * 3 resource instances configured + + Node List: + * Online: [ pcmk-1 ] + * GuestOnline: [ guest1@pcmk-1 ] + + Full List of Resources: + * vm-guest1 (ocf::heartbeat:VirtualDomain): Started pcmk-1 + * webserver (ocf::heartbeat::apache): Started guest1 + +It is worth noting that after **guest1** is integrated into the cluster, nearly all the +Pacemaker command-line tools immediately become available to the guest node. +This means things like ``crm_mon``, ``crm_resource``, and ``crm_attribute`` will work +natively on the guest node, as long as the connection between the guest node +and a cluster node exists. This is particularly important for any promotable +clone resources executing on the guest node that need access to ``crm_master`` to +set transient attributes. + +Mile-High View of Configuration Steps +##################################### + +The command used in `Integrate Guest Node into Cluster`_ does multiple things. +If you'd like to each part manually, you can do so as follows. You'll see that the +end result is the same: + +* Later, we are going to put the same authentication key with the path + ``/etc/pacemaker/authkey`` on every cluster node and on every virtual machine. + This secures remote communication. + + Run this command on your cluster node if you want to make a somewhat random key: + + .. code-block:: none + + # dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1 + + +* To create the VirtualDomain resource agent for the management of the virtual + machine, Pacemaker requires the virtual machine's xml config file to be dumped + to a file -- which we can name as we'd like -- on disk. We named our virtual + machine guest1; for this example, we'll dump to the file /etc/pacemaker/guest1.xml + + .. code-block:: none + + # virsh dumpxml guest1 > /etc/pacemaker/guest1.xml + +* Install pacemaker_remote on the virtual machine, and if a local firewall is used, + allow the node to accept connections on TCP port 3121. + + .. code-block:: none + + # yum install pacemaker-remote resource-agents + # firewall-cmd --add-port 3121/tcp --permanent + + .. NOTE:: + + If you just want to see this work, you may want to simply disable the local + firewall and put SELinux in permissive mode while testing. This creates + security risks and should not be done on a production machine exposed to the + Internet, but can be appropriate for a protected test machine. + +* On a cluster node, create a Pacemaker VirtualDomain resource to launch the virtual machine. + + .. code-block:: none + + [root@pcmk-1 ~]# pcs resource create vm-guest1 VirtualDomain hypervisor="qemu:///system" config="vm-guest1.xml" meta + Assumed agent name 'ocf:heartbeat:VirtualDomain' (deduced from 'VirtualDomain') + +* Now use the following command to convert the VirtualDomain resource into a guest node + which we'll name guest1. By doing so, the /etc/pacemaker/authkey will get copied to + the guest node and the pacemaker_remote daemon will get started and enabled on the + guest node as well. + + .. code-block:: none + + [root@pcmk-1 ~]# pcs cluster node add-guest guest1 vm-guest1 + No addresses specified for host 'guest1', using 'guest1' + Sending 'pacemaker authkey' to 'guest1' + guest1: successful distribution of the file 'pacemaker authkey' + Requesting 'pacemaker_remote enable', 'pacemaker_remote start' on 'guest1' + guest1: successful run of 'pacemaker_remote enable' + guest1: successful run of 'pacemaker_remote start' + +* This will create CIB XML similar to the following: + + .. code-block:: xml + + + + + + + + + + + + + + + + + + + + .. code-block:: xml + + [root@pcmk-1 ~]# pcs resource status + * vm-guest1 (ocf::heartbeat:VirtualDomain): Stopped + + [root@pcmk-1 ~]# pcs resource config + Resource: vm-guest1 (class=ocf provider=heartbeat type=VirtualDomain) + Attributes: config=vm-guest1.xml hypervisor=qemu:///system + Meta Attrs: remote-addr=guest1 remote-node=guest1 + Operations: migrate_from interval=0s timeout=60s (vm-guest1-migrate_from-interval-0s) + migrate_to interval=0s timeout=120s (vm-guest1-migrate_to-interval-0s) + monitor interval=10s timeout=30s (vm-guest1-monitor-interval-10s) + start interval=0s timeout=90s (vm-guest1-start-interval-0s) + stop interval=0s timeout=90s (vm-guest1-stop-interval-0s) + +The cluster will attempt to contact the virtual machine's pacemaker_remote service at the +hostname **guest1** after it launches. + +.. NOTE:: + + The ID of the resource creating the virtual machine (**vm-guest1** in the above + example) 'must' be different from the virtual machine's uname (**guest1** in the + above example). Pacemaker will create an implicit internal resource for the + pacemaker_remote connection to the guest, named with the value of **remote-node**, + so that value cannot be used as the name of any other resource. + +Troubleshooting a Remote Connection +################################### + +Note: This section should not be done when the guest is connected to the cluster. + +Should connectivity issues occur, it can be worth verifying that the cluster nodes +can contact the remote node on port 3121. Here's a trick you can use. +Connect using ssh from each of the cluster nodes. The connection will get +destroyed, but how it is destroyed tells you whether it worked or not. + +If running the ssh command on one of the cluster nodes results in this +output before disconnecting, the connection works: + +.. code-block:: none + + # ssh -p 3121 guest1 + ssh_exchange_identification: read: Connection reset by peer + +If you see one of these, the connection is not working: + +.. code-block:: none + + # ssh -p 3121 guest1 + ssh: connect to host guest1 port 3121: No route to host + +.. code-block:: none + + # ssh -p 3121 guest1 + ssh: connect to host guest1 port 3121: Connection refused + +If you see this, then the connection is working, but port 3121 is attached +to SSH, which it should not be. + +.. code-block:: none + + # ssh -p 3121 guest1 + kex_exchange_identification: banner line contains invalid characters + +Once you can successfully connect to the guest from the host, you may +shutdown the guest. Pacemaker will be managing the virtual machine from +this point forward. diff --git a/doc/sphinx/Pacemaker_Remote/options.rst b/doc/sphinx/Pacemaker_Remote/options.rst index c855a1aedd..f14b479e78 100644 --- a/doc/sphinx/Pacemaker_Remote/options.rst +++ b/doc/sphinx/Pacemaker_Remote/options.rst @@ -1,146 +1,173 @@ .. index:: single: configuration Configuration Explained ----------------------- The walk-through examples use some of these options, but don't explain exactly what they mean or do. This section is meant to be the go-to resource for all the options available for configuring Pacemaker Remote. .. index:: pair: configuration; guest node single: guest node; meta-attribute Resource Meta-Attributes for Guest Nodes ######################################## When configuring a virtual machine as a guest node, the virtual machine is created using one of the usual resource agents for that purpose (for example, **ocf:heartbeat:VirtualDomain** or **ocf:heartbeat:Xen**), with additional meta-attributes. No restrictions are enforced on what agents may be used to create a guest node, but obviously the agent must create a distinct environment capable of running the pacemaker_remote daemon and cluster resources. An additional requirement is that fencing the host running the guest node resource must be sufficient for ensuring the guest node is stopped. This means, for example, that not all hypervisors supported by **VirtualDomain** may be used to create guest nodes; if the guest can survive the hypervisor being fenced, it may not be used as a guest node. Below are the meta-attributes available to enable a resource as a guest node and define its connection parameters. .. table:: **Meta-attributes for configuring VM resources as guest nodes** +------------------------+-----------------+-----------------------------------------------------------+ | Option | Default | Description | +========================+=================+===========================================================+ | remote-node | none | The node name of the guest node this resource defines. | | | | This both enables the resource as a guest node and | | | | defines the unique name used to identify the guest node. | | | | If no other parameters are set, this value will also be | | | | assumed as the hostname to use when connecting to | | | | pacemaker_remote on the VM. This value **must not** | | | | overlap with any resource or node IDs. | +------------------------+-----------------+-----------------------------------------------------------+ | remote-port | 3121 | The port on the virtual machine that the cluster will | | | | use to connect to pacemaker_remote. | +------------------------+-----------------+-----------------------------------------------------------+ | remote-addr | 'value of' | The IP address or hostname to use when connecting to | | | ``remote-node`` | pacemaker_remote on the VM. | +------------------------+-----------------+-----------------------------------------------------------+ | remote-connect-timeout | 60s | How long before a pending guest connection will time out. | +------------------------+-----------------+-----------------------------------------------------------+ .. index:: pair: configuration; remote node Connection Resources for Remote Nodes ##################################### A remote node is defined by a connection resource. That connection resource has instance attributes that define where the remote node is located on the network and how to communicate with it. Descriptions of these instance attributes can be retrieved using the following ``pcs`` command: .. code-block:: none # pcs resource describe remote ocf:pacemaker:remote - remote resource agent Resource options: server: Server location to connect to. This can be an ip address or hostname. port: tcp port to connect to. - reconnect_interval: Interval in seconds at which Pacemaker will attempt to - reconnect to a remote node after an active connection to - the remote node has been severed. When this value is - nonzero, Pacemaker will retry the connection - indefinitely, at the specified interval. + reconnect_interval: Interval in seconds at which Pacemaker will attempt to reconnect to a + remote node after an active connection to the remote node has been + severed. When this value is nonzero, Pacemaker will retry the connection + indefinitely, at the specified interval. As with any time-based actions, + this is not guaranteed to be checked more frequently than the value of the + cluster-recheck-interval cluster option. + When defining a remote node's connection resource, it is common and recommended to name the connection resource the same as the remote node's hostname. By default, if no ``server`` option is provided, the cluster will attempt to contact the remote node using the resource name as the hostname. -Example defining a remote node with the hostname **remote1**: - -.. code-block:: none - - # pcs resource create remote1 remote - -Example defining a remote node to connect to a specific IP address and port: - -.. code-block:: none - - # pcs resource create remote1 remote server=192.168.122.200 port=8938 - -.. index:: - single: configuration; environment variable - single: environment variable - Environment Variables for Daemon Start-up ######################################### Authentication and encryption of the connection between cluster nodes and nodes running pacemaker_remote is achieved using with `TLS-PSK `_ encryption/authentication over TCP (port 3121 by default). This means that both the cluster node and remote node must share the same private key. By default, this key is placed at ``/etc/pacemaker/authkey`` on each node. You can change the default port and/or key location for Pacemaker and ``pacemaker_remoted`` via environment variables. How these variables are set varies by OS, but usually they are set in the ``/etc/sysconfig/pacemaker`` or ``/etc/default/pacemaker`` file. .. code-block:: none #==#==# Pacemaker Remote - # Use a custom directory for finding the authkey. - PCMK_authkey_location=/etc/pacemaker/authkey + # Use the contents of this file as the authorization key to use with Pacemaker + # Remote connections. This file must be readable by Pacemaker daemons (that is, + # it must allow read permissions to either the hacluster user or the haclient + # group), and its contents must be identical on all nodes. The default is + # "/etc/pacemaker/authkey". + # PCMK_authkey_location=/etc/pacemaker/authkey + + # If the Pacemaker Remote service is run on the local node, it will listen + # for connections on this address. The value may be a resolvable hostname or an + # IPv4 or IPv6 numeric address. When resolving names or using the default + # wildcard address (i.e. listen on all available addresses), IPv6 will be + # preferred if available. When listening on an IPv6 address, IPv4 clients will + # be supported (via IPv4-mapped IPv6 addresses). + # PCMK_remote_address="192.0.2.1" + + # Use this TCP port number when connecting to a Pacemaker Remote node. This + # value must be the same on all nodes. The default is "3121". + # PCMK_remote_port=3121 + + # Use these GnuTLS cipher priorities for TLS connections. See: + # + # https://gnutls.org/manual/html_node/Priority-Strings.html + # + # Pacemaker will append ":+ANON-DH" for remote CIB access (when enabled) and + # ":+DHE-PSK:+PSK" for Pacemaker Remote connections, as they are required for + # the respective functionality. + # PCMK_tls_priorities="NORMAL" + + # Set bounds on the bit length of the prime number generated for Diffie-Hellman + # parameters needed by TLS connections. The default is not to set any bounds. + # + # If these values are specified, the server (Pacemaker Remote daemon, or CIB + # manager configured to accept remote clients) will use these values to provide + # a floor and/or ceiling for the value recommended by the GnuTLS library. The + # library will only accept a limited number of specific values, which vary by + # library version, so setting these is recommended only when required for + # compatibility with specific client versions. # - # Specify a custom port for Pacemaker Remote connections - PCMK_remote_port=3121 + # If PCMK_dh_min_bits is specified, the client (connecting cluster node or + # remote CIB command) will require that the server use a prime of at least this + # size. This is only recommended when the value must be lowered in order for + # the client's GnuTLS library to accept a connection to an older server. + # The client side does not use PCMK_dh_max_bits. + # + # PCMK_dh_min_bits=1024 + # PCMK_dh_max_bits=2048 Removing Remote Nodes and Guest Nodes ##################################### If the resource creating a guest node, or the **ocf:pacemaker:remote** resource creating a connection to a remote node, is removed from the configuration, the affected node will continue to show up in output as an offline node. If you want to get rid of that output, run (replacing ``$NODE_NAME`` appropriately): .. code-block:: none # crm_node --force --remove $NODE_NAME .. WARNING:: Be absolutely sure that there are no references to the node's resource in the configuration before running the above command. diff --git a/doc/sphinx/conf.py.in b/doc/sphinx/conf.py.in index 91c40b0404..d181147cd6 100644 --- a/doc/sphinx/conf.py.in +++ b/doc/sphinx/conf.py.in @@ -1,316 +1,316 @@ """ Sphinx configuration for Pacemaker documentation """ __copyright__ = "Copyright 2020 the Pacemaker project contributors" __license__ = "GNU General Public License version 2 or later (GPLv2+) WITHOUT ANY WARRANTY" # This file is execfile()d with the current directory set to its containing dir. # # Note that not all possible configuration values are present in this # autogenerated file. # # All configuration values have a default; values that are commented out # serve to show the default. import datetime import os import sys # Variables that can be used later in this file authors = "the Pacemaker project contributors" year = datetime.datetime.now().year doc_license = "Creative Commons Attribution-ShareAlike International Public License" doc_license += " version 4.0 or later (CC-BY-SA v4.0+)" # rST markup to insert at beginning of every document; mainly used for # # .. || replace:: # # where occurrences of || in the rST will be substituted with rst_prolog=""" .. |CFS_DISTRO| replace:: CentOS Stream .. |CFS_DISTRO_VER| replace:: 8 -.. |REMOTE_DISTRO| replace:: CentOS -.. |REMOTE_DISTRO_VER| replace:: 7.4 +.. |REMOTE_DISTRO| replace:: CentOS Stream +.. |REMOTE_DISTRO_VER| replace:: 8 """ # If extensions (or modules to document with autodoc) are in another directory, # add these directories to sys.path here. If the directory is relative to the # documentation root, use os.path.abspath to make it absolute, like shown here. #sys.path.insert(0, os.path.abspath('.')) # -- General configuration ----------------------------------------------------- # If your documentation needs a minimal Sphinx version, state it here. needs_sphinx = '1.0' # Add any Sphinx extension module names here, as strings. They can be extensions # coming with Sphinx (named 'sphinx.ext.*') or your custom ones. extensions = [] # Add any paths that contain templates here, relative to this directory. templates_path = ['_templates'] # The suffix of source filenames. source_suffix = '.rst' # The encoding of source files. #source_encoding = 'utf-8-sig' # The master toctree document. master_doc = 'index' # General information about the project. project = '%BOOK_ID%' copyright = "2009-%s %s. Released under the terms of the %s" % (year, authors, doc_license) # The version info for the project you're documenting, acts as replacement for # |version| and |release|, also used in various other places throughout the # built documents. # # The full version, including alpha/beta/rc tags. release = '%VERSION%' # The short X.Y version. version = release.rsplit('.', 1)[0] # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. #language = None # There are two options for replacing |today|: either, you set today to some # non-false value, then it is used: #today = '' # Else, today_fmt is used as the format for a strftime call. #today_fmt = '%B %d, %Y' # List of patterns, relative to source directory, that match files and # directories to ignore when looking for source files. exclude_patterns = ['_build'] # The reST default role (used for this markup: `text`) to use for all documents. #default_role = None # If true, '()' will be appended to :func: etc. cross-reference text. #add_function_parentheses = True # If true, the current module name will be prepended to all description # unit titles (such as .. function::). #add_module_names = True # If true, sectionauthor and moduleauthor directives will be shown in the # output. They are ignored by default. #show_authors = False # The name of the Pygments (syntax highlighting) style to use. pygments_style = 'vs' # A list of ignored prefixes for module index sorting. #modindex_common_prefix = [] # -- Options for HTML output --------------------------------------------------- # The theme to use for HTML and HTML Help pages. See the documentation for # a list of builtin themes. html_theme = 'pyramid' # Theme options are theme-specific and customize the look and feel of a theme # further. For a list of options available for each theme, see the # documentation. #html_theme_options = {} # Add any paths that contain custom themes here, relative to this directory. #html_theme_path = [] html_style = 'pacemaker.css' # The name for this set of Sphinx documents. If None, it defaults to # " v documentation". html_title = "%BOOK_TITLE%" # A shorter title for the navigation bar. Default is the same as html_title. #html_short_title = None # The name of an image file (relative to this directory) to place at the top # of the sidebar. #html_logo = None # The name of an image file (within the static path) to use as favicon of the # docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32 # pixels large. #html_favicon = None # Add any paths that contain custom static files (such as style sheets) here, # relative to this directory. They are copied after the builtin static files, # so a file named "default.css" will overwrite the builtin "default.css". html_static_path = [ '%SRC_DIR%/_static' ] # If not '', a 'Last updated on:' timestamp is inserted at every page bottom, # using the given strftime format. #html_last_updated_fmt = '%b %d, %Y' # If true, SmartyPants will be used to convert quotes and dashes to # typographically correct entities. #html_use_smartypants = True # Custom sidebar templates, maps document names to template names. #html_sidebars = {} # Additional templates that should be rendered to pages, maps page names to # template names. #html_additional_pages = {} # If false, no module index is generated. #html_domain_indices = True # If false, no index is generated. #html_use_index = True # If true, the index is split into individual pages for each letter. #html_split_index = False # If true, links to the reST sources are added to the pages. #html_show_sourcelink = True # If true, "Created using Sphinx" is shown in the HTML footer. Default is True. #html_show_sphinx = True # If true, "(C) Copyright ..." is shown in the HTML footer. Default is True. #html_show_copyright = True # If true, an OpenSearch description file will be output, and all pages will # contain a tag referring to it. The value of this option must be the # base URL from which the finished HTML is served. #html_use_opensearch = '' # This is the file name suffix for HTML files (e.g. ".xhtml"). #html_file_suffix = None # Output file base name for HTML help builder. htmlhelp_basename = 'Pacemakerdoc' # -- Options for LaTeX output -------------------------------------------------- latex_engine = "xelatex" latex_elements = { # The paper size ('letterpaper' or 'a4paper'). #'papersize': 'letterpaper', # The font size ('10pt', '11pt' or '12pt'). #'pointsize': '10pt', # Additional stuff for the LaTeX preamble. #'preamble': '', } # Grouping the document tree into LaTeX files. List of tuples # (source start file, target name, title, author, documentclass [howto/manual]). latex_documents = [ ('index', '%BOOK_ID%.tex', '%BOOK_TITLE%', authors, 'manual'), ] # The name of an image file (relative to this directory) to place at the top of # the title page. #latex_logo = None # For "manual" documents, if this is true, then toplevel headings are parts, # not chapters. #latex_use_parts = False # If true, show page references after internal links. #latex_show_pagerefs = False # If true, show URL addresses after external links. #latex_show_urls = False # Documents to append as an appendix to all manuals. #latex_appendices = [] # If false, no module index is generated. #latex_domain_indices = True # -- Options for manual page output -------------------------------------------- # One entry per manual page. List of tuples # (source start file, name, description, authors, manual section). man_pages = [ ('index', '%BOOK_ID%', 'Part of the Pacemaker documentation set', [authors], 8) ] # If true, show URL addresses after external links. #man_show_urls = False # -- Options for Texinfo output ------------------------------------------------ # Grouping the document tree into Texinfo files. List of tuples # (source start file, target name, title, author, # dir menu entry, description, category) texinfo_documents = [ ('index', '%BOOK_ID%', '%BOOK_TITLE%', authors, '%BOOK_TITLE%', 'Pacemaker is an advanced, scalable high-availability cluster resource manager.', 'Miscellaneous'), ] # Documents to append as an appendix to all manuals. #texinfo_appendices = [] # If false, no module index is generated. #texinfo_domain_indices = True # How to display URL addresses: 'footnote', 'no', or 'inline'. #texinfo_show_urls = 'footnote' # -- Options for Epub output --------------------------------------------------- # Bibliographic Dublin Core info. epub_title = '%BOOK_TITLE%' epub_author = authors epub_publisher = 'ClusterLabs.org' epub_copyright = copyright # The language of the text. It defaults to the language option # or en if the language is not set. #epub_language = '' # The scheme of the identifier. Typical schemes are ISBN or URL. epub_scheme = 'URL' # The unique identifier of the text. This can be a ISBN number # or the project homepage. epub_identifier = 'http://www.clusterlabs.org/pacemaker/doc/2.0/%BOOK_ID%/epub/%BOOK_ID%.epub' # A unique identification for the text. epub_uid = 'ClusterLabs.org-Pacemaker-%BOOK_ID%' # A tuple containing the cover image and cover page html template filenames. #epub_cover = () # HTML files that should be inserted before the pages created by sphinx. # The format is a list of tuples containing the path and title. #epub_pre_files = [] # HTML files that should be inserted after the pages created by sphinx. # The format is a list of tuples containing the path and title. #epub_post_files = [] # A list of files that should not be packed into the epub file. epub_exclude_files = [ '_static/doctools.js', '_static/jquery.js', '_static/searchtools.js', '_static/underscore.js', '_static/basic.css', '_static/websupport.js', 'search.html', ] # The depth of the table of contents in toc.ncx. #epub_tocdepth = 3 # Allow duplicate toc entries. #epub_tocdup = True