Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Google Cloud Platform icon
Labs

Install and Configure a Pacemaker Cluster

Pacemaker is a high-availability Cluster Resource Manager (CRM) that runs on a group of servers in order to minimize downtime. Resources managed by Pacemaker will be moved in the event of a node failure and can be configured to run in tandem with other resources. In this lesson, you are tasked with installing and configuring a Pacemaker cluster that manages an Apache HTTP server resource as well as an IP resource.

Google Cloud Platform icon
Labs

Path Info

Level
Clock icon Advanced
Duration
Clock icon 1h 30m
Published
Clock icon Nov 12, 2018

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Install the required packages for Pacemaker and PCS on each cluster node.

    Install the pacemaker and pcs packages.

  2. Challenge

    Start and enable the pcsd service on each cluster node.

    On each node, start and enable pcsd.

  3. Challenge

    Set the password for the hacluster user on each cluster node to "pacemaker”.

    Set the password for the hacluster user to pacemaker. Do not include the quotes and ignore the bad password warning.

  4. Challenge

    On pacemaker1, use pcs to authenticate to pcsd on the cluster nodes as the hacluster user.

    Run the pcs authentication command from pacemaker1 and supply a username and password.

  5. Challenge

    Generate and synchronize the Corosync configuration to both cluster nodes for a cluster named cluster1.

    Generate and synchronize the Corosync configuration and start up the cluster.

  6. Challenge

    Set the stonith-enabled property to false.

    Set the property with the pcs property command.

  7. Challenge

    Add an IP resource named cluster_ip.

    Create an IP resource with the pcs resource command. Name the cluster_ip, with an IP address of 10.0.1.50, a netmask of 24, and a monitor interval of 30 seconds.

  8. Challenge

    Add an Apache HTTP server as a cluster resource.

    Use the pcs resource command to create the resource. The resource should be named apache, use /etc/httpd/conf/httpd.conf as the configuration file, use http://localhost/server-status as the status URL, and have a monitor interval of 1 minute.

  9. Challenge

    Set a colocation constraint so that the `apache` and `cluster_ip` resources always run on the same host.

    Use the pcs constraint command to set the colocation constraint.

  10. Challenge

    Set an order constraint so that the `cluster_ip` resource starts before the `apache` resource.

    Use the pcs constraint command to set the order constraint.

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans