Table of Contents
-
Pacemaker Explained
-
Introduction
-
The Scope of this Document
-
What Is Pacemaker?
-
Cluster Architecture
-
Pacemaker Architecture
-
Node Redundancy Designs
-
Host-Local Configuration
-
Configuration Value Types
-
Scores
-
Local Options
-
Cluster-Wide Configuration
-
Configuration Layout
-
CIB Properties
-
Cluster Options
-
Cluster Nodes
-
Defining a Cluster Node
-
Where Pacemaker Gets the Node Name
-
Node Attributes
-
Setting and querying node attributes
-
Special node attributes
-
Tracking Node Health
-
Node Health Attributes
-
Node Health Strategy
-
Exempting a Resource from Health Restrictions
-
Configuring Node Health Agents
-
Cluster Resources
-
What is a Cluster Resource?
-
Resource Standards
-
Open Cluster Framework
-
Systemd
-
Linux Standard Base
-
System Services
-
STONITH
-
Nagios Plugins
-
Upstart
-
Resource Properties
-
Resource Options
-
Resource Meta-Attributes
-
Setting Global Defaults for Resource Meta-Attributes
-
Resource Instance Attributes
-
Resource Operations
-
Operation Properties
-
Monitoring Resources for Failure
-
Setting Global Defaults for Operations
-
When Implicit Operations Take a Long Time
-
Multiple Monitor Operations
-
Disabling a Monitor Operation
-
Specifying When Recurring Actions are Performed
-
Handling Resource Failure
-
Failure Counts
-
Failure Response
-
Reloading an Agent After a Definition Change
-
Migrating Resources
-
Resource Constraints
-
Deciding Which Nodes a Resource Can Run On
-
Location Properties
-
Asymmetrical “Opt-In” Clusters
-
Symmetrical “Opt-Out” Clusters
-
What if Two Nodes Have the Same Score
-
Specifying locations using pattern matching
-
Specifying the Order in which Resources Should Start/Stop
-
Ordering Properties
-
Optional and mandatory ordering
-
Symmetric and asymmetric ordering
-
Placing Resources Relative to other Resources
-
Colocation Properties
-
Mandatory Placement
-
Advisory Placement
-
Colocation by Node Attribute
-
Colocation Influence
-
Resource Sets
-
Ordering Sets of Resources
-
Ordered Set
-
Ordering Multiple Sets
-
Resource Set OR Logic
-
Colocating Sets of Resources
-
External Resource Dependencies
-
Fencing
-
What Is Fencing?
-
Why Is Fencing Necessary?
-
Fence Devices
-
Fence Agents
-
When a Fence Device Can Be Used
-
Limitations of Fencing Resources
-
Special Meta-Attributes for Fencing Resources
-
Special Instance Attributes for Fencing Resources
-
Default Check Type
-
Unfencing
-
Fencing and Quorum
-
Fencing Timeouts
-
Fence Devices Dependent on Other Resources
-
Configuring Fencing
-
Example Fencing Configuration
-
Fencing Topologies
-
Example Dual-Layer, Dual-Device Fencing Topologies
-
Remapping Reboots
-
Alerts
-
Alert Agents
-
Alert Recipients
-
Alert Meta-Attributes
-
Alert Instance Attributes
-
Alert Filters
-
Rules
-
Rule Options
-
Rule Conditions and Contexts
-
Date/Time Expressions
-
Date Specifications
-
Durations
-
Example Date/Time Expressions
-
Node Attribute Expressions
-
Resource Type Expressions
-
Example Resource Type Expressions
-
Operation Type Expressions
-
Example Operation Type Expressions
-
Using Rules to Determine Resource Location
-
Location Rules Based on Other Node Properties
-
Using score-attribute Instead of score
-
Specifying location scores using pattern submatches
-
Using Rules to Define Options
-
Using Rules to Control Resource Options
-
Using Rules to Control Resource Defaults
-
Using Rules to Control Cluster Options
-
Collective Resources
-
Groups - A Syntactic Shortcut
-
Group Properties
-
Group Options
-
Group Instance Attributes
-
Group Contents
-
Group Constraints
-
Group Stickiness
-
Clones - Resources That Can Have Multiple Active Instances
-
Anonymous versus Unique Clones
-
Promotable clones
-
Clone Properties
-
Clone Options
-
Clone Contents
-
Clone Instance Attribute
-
Clone Constraints
-
Clone Stickiness
-
Monitoring Promotable Clone Resources
-
Determining Which Instance is Promoted
-
Bundles - Containerized Resources
-
Bundle Prerequisites
-
Bundle Properties
-
Bundle Container Properties
-
Bundle Network Properties
-
Bundle Storage Properties
-
Bundle Primitive
-
Bundle Node Attributes
-
Bundle Meta-Attributes
-
Limitations of Bundles
-
Reusing Parts of the Configuration
-
Reusing Resource Definitions
-
Configuring Resources with Templates
-
Using Templates in Constraints
-
Using Templates in Resource Sets
-
Reusing Rules, Options and Sets of Operations
-
Tagging Configuration Elements
-
Configuring Tags
-
Using Tags in Constraints and Resource Sets
-
Filtering With Tags
-
Utilization and Placement Strategy
-
Utilization attributes
-
Placement Strategy
-
How Multiple Capacities Combine
-
Order of Resource Assignment
-
Limitations
-
Access Control Lists (ACLs)
-
ACL Prerequisites
-
ACL Configuration
-
ACL Roles
-
ACL Targets and Groups
-
ACL Examples
-
ACL Limitations
-
Actions performed via IPC rather than the CIB
-
ACLs and Pacemaker Remote
-
Status
-
Node State
-
Transient Node Attributes
-
Node History
-
Resource History
-
Action History
-
Simple Operation History Example
-
Complex Operation History Example
-
Multi-Site Clusters and Tickets
-
Challenges for Multi-Site Clusters
-
Conceptual Overview
-
Ticket
-
Dead Man Dependency
-
Cluster Ticket Registry
-
Configuration Replication
-
Configuring Ticket Dependencies
-
Managing Multi-Site Clusters
-
Granting and Revoking Tickets Manually
-
Granting and Revoking Tickets via a Cluster Ticket Registry
-
General Management of Tickets
-
For more information
-
Sample Configurations
-
Empty
-
Simple
-
Advanced Configuration