Pacemaker Explained

Configuring Pacemaker Clusters

Abstract

This document definitively explains Pacemaker’s features and capabilities, particularly the XML syntax used in Pacemaker’s Cluster Information Base (CIB).

Table of Contents

• 1. Introduction
  • 1.1. The Scope of this Document
  • 1.2. What Is Pacemaker?
    • 1.2.1. Cluster Architecture
    • 1.2.2. Pacemaker Architecture
    • 1.2.3. Node Redundancy Designs
• 2. Cluster-Wide Configuration
  • 2.1. Configuration Layout
  • 2.2. CIB Properties
  • 2.3. Cluster Options
• 3. Cluster Nodes
  • 3.1. Defining a Cluster Node
    • 3.1.1. Where Pacemaker Gets the Node Name
  • 3.2. Node Attributes
    • 3.2.1. Setting and querying node attributes
    • 3.2.2. Special node attributes
  • 3.3. Tracking Node Health
    • 3.3.1. Node Health Attributes
    • 3.3.2. Node Health Strategy
    • 3.3.3. Exempting a Resource from Health Restrictions
    • 3.3.4. Configuring Node Health Agents
• 4. Cluster Resources
  • 4.1. What is a Cluster Resource?
  • 4.2. Resource Classes
    • 4.2.1. Open Cluster Framework
    • 4.2.2. Systemd
    • 4.2.3. Linux Standard Base
    • 4.2.4. Upstart
    • 4.2.5. System Services
    • 4.2.6. STONITH
    • 4.2.7. Nagios Plugins
  • 4.3. Resource Properties
  • 4.4. Resource Options
    • 4.4.1. Resource Meta-Attributes
    • 4.4.2. Setting Global Defaults for Resource Meta-Attributes
    • 4.4.3. Resource Instance Attributes
  • 4.5. Resource Operations
    • 4.5.1. Operation Properties
    • 4.5.2. Monitoring Resources for Failure
    • 4.5.3. Monitoring Resources When Administration is Disabled
    • 4.5.4. Setting Global Defaults for Operations
    • 4.5.5. When Implicit Operations Take a Long Time
    • 4.5.6. Multiple Monitor Operations
    • 4.5.7. Disabling a Monitor Operation
• 5. Resource Constraints
  • 5.1. Scores
    • 5.1.1. Infinity Math
  • 5.2. Deciding Which Nodes a Resource Can Run On
    • 5.2.1. Location Properties
    • 5.2.2. Asymmetrical “Opt-In” Clusters
    • 5.2.3. Symmetrical “Opt-Out” Clusters
    • 5.2.4. What if Two Nodes Have the Same Score
    • 5.2.5. Specifying locations using pattern matching
  • 5.3. Specifying the Order in which Resources Should Start/Stop
    • 5.3.1. Ordering Properties
    • 5.3.2. Optional and mandatory ordering
  • 5.4. Placing Resources Relative to other Resources
    • 5.4.1. Colocation Properties
    • 5.4.2. Mandatory Placement
    • 5.4.3. Advisory Placement
    • 5.4.4. Colocation by Node Attribute
    • 5.4.5. Colocation Influence
  • 5.5. Resource Sets
  • 5.6. Ordering Sets of Resources
    • 5.6.1. Ordered Set
    • 5.6.2. Ordering Multiple Sets
    • 5.6.3. Resource Set OR Logic
  • 5.7. Colocating Sets of Resources
• 6. Fencing
  • 6.1. What Is Fencing?
  • 6.2. Why Is Fencing Necessary?
  • 6.3. Fence Devices
  • 6.4. Fence Agents
  • 6.5. When a Fence Device Can Be Used
  • 6.6. Limitations of Fencing Resources
  • 6.7. Special Meta-Attributes for Fencing Resources
  • 6.8. Special Instance Attributes for Fencing Resources
  • 6.9. Default Check Type
  • 6.10. Unfencing
  • 6.11. Fencing and Quorum
  • 6.12. Fencing Timeouts
  • 6.13. Fence Devices Dependent on Other Resources
  • 6.14. Configuring Fencing
    • 6.14.1. Example Fencing Configuration
  • 6.15. Fencing Topologies
    • 6.15.1. Example Dual-Layer, Dual-Device Fencing Topologies
  • 6.16. Remapping Reboots
• 7. Alerts
  • 7.1. Alert Agents
  • 7.2. Alert Recipients
  • 7.3. Alert Meta-Attributes
  • 7.4. Alert Instance Attributes
  • 7.5. Alert Filters
  • 7.6. Using the Sample Alert Agents
  • 7.7. Writing an Alert Agent
• 8. Rules
  • 8.1. Rule Properties
  • 8.2. Node Attribute Expressions
  • 8.3. Date/Time Expressions
    • 8.3.1. Date Specifications
    • 8.3.2. Durations
    • 8.3.3. Example Time-Based Expressions
  • 8.4. Resource Expressions
    • 8.4.1. Example Resource-Based Expressions
  • 8.5. Operation Expressions
    • 8.5.1. Example Operation-Based Expressions
  • 8.6. Using Rules to Determine Resource Location
    • 8.6.1. Location Rules Based on Other Node Properties
    • 8.6.2. Using score-attribute Instead of score
    • 8.6.3. Specifying location scores using pattern submatches
  • 8.7. Using Rules to Define Options
    • 8.7.1. Using Rules to Control Resource Options
    • 8.7.2. Using Rules to Control Resource Defaults
    • 8.7.3. Using Rules to Control Cluster Options
• 9. Advanced Configuration
  • 9.1. Specifying When Recurring Actions are Performed
  • 9.2. Handling Resource Failure
    • 9.2.1. Failure Counts
    • 9.2.2. Failure Response
  • 9.3. Moving Resources
    • 9.3.1. Moving Resources Manually
    • 9.3.2. Moving Resources Due to Connectivity Changes
    • 9.3.3. Migrating Resources
  • 9.4. Reloading an Agent After a Definition Change
• 10. Advanced Resource Types
  • 10.1. Groups - A Syntactic Shortcut
    • 10.1.1. Group Properties
    • 10.1.2. Group Options
    • 10.1.3. Group Instance Attributes
    • 10.1.4. Group Contents
    • 10.1.5. Group Constraints
    • 10.1.6. Group Stickiness
  • 10.2. Clones - Resources That Can Have Multiple Active Instances
    • 10.2.1. Anonymous versus Unique Clones
    • 10.2.2. Promotable clones
    • 10.2.3. Clone Properties
    • 10.2.4. Clone Options
    • 10.2.5. Clone Contents
    • 10.2.6. Clone Instance Attribute
    • 10.2.7. Clone Constraints
    • 10.2.8. Clone Stickiness
    • 10.2.9. Clone Resource Agent Requirements
    • 10.2.10. Monitoring Promotable Clone Resources
    • 10.2.11. Determining Which Instance is Promoted
  • 10.3. Bundles - Containerized Resources
    • 10.3.1. Bundle Prerequisites
    • 10.3.2. Bundle Properties
    • 10.3.3. Bundle Container Properties
    • 10.3.4. Bundle Network Properties
    • 10.3.5. Bundle Storage Properties
    • 10.3.6. Bundle Primitive
    • 10.3.7. Bundle Node Attributes
    • 10.3.8. Bundle Meta-Attributes
    • 10.3.9. Limitations of Bundles
• 11. Reusing Parts of the Configuration
  • 11.1. Reusing Resource Definitions
    • 11.1.1. Configuring Resources with Templates
    • 11.1.2. Using Templates in Constraints
    • 11.1.3. Using Templates in Resource Sets
  • 11.2. Reusing Rules, Options and Sets of Operations
  • 11.3. Tagging Configuration Elements
    • 11.3.1. Configuring Tags
    • 11.3.2. Using Tags in Constraints and Resource Sets
    • 11.3.3. Filtering With Tags
• 12. Utilization and Placement Strategy
  • 12.1. Utilization attributes
  • 12.2. Placement Strategy
  • 12.3. Allocation Details
    • 12.3.1. Which node is preferred to get consumed first when allocating resources?
    • 12.3.2. Which node has more free capacity?
    • 12.3.3. Which resource is preferred to be assigned first?
  • 12.4. Limitations and Workarounds
• 13. Access Control Lists (ACLs)
  • 13.1. ACL Prerequisites
  • 13.2. ACL Configuration
  • 13.3. ACL Roles
  • 13.4. ACL Targets and Groups
  • 13.5. ACL Examples
  • 13.6. ACL Limitations
    • 13.6.1. Actions performed via IPC rather than the CIB
    • 13.6.2. ACLs and Pacemaker Remote
• 14. Status – Here be dragons
  • 14.1. Node Status
  • 14.2. Transient Node Attributes
  • 14.3. Operation History
    • 14.3.1. Simple Operation History Example
    • 14.3.2. Complex Operation History Example
• 15. Multi-Site Clusters and Tickets
  • 15.1. Challenges for Multi-Site Clusters
  • 15.2. Conceptual Overview
    • 15.2.1. Ticket
    • 15.2.2. Dead Man Dependency
    • 15.2.3. Cluster Ticket Registry
    • 15.2.4. Configuration Replication
  • 15.3. Configuring Ticket Dependencies
  • 15.4. Managing Multi-Site Clusters
    • 15.4.1. Granting and Revoking Tickets Manually
    • 15.4.2. Granting and Revoking Tickets via a Cluster Ticket Registry
    • 15.4.3. General Management of Tickets
  • 15.5. For more information
• 16. Sample Configurations
  • 16.1. Empty
  • 16.2. Simple
  • 16.3. Advanced Configuration

Index

• Index
• Search Page