![]() ![]() Example set of opt-out location constraints 6.3. Example set of opt-in location constraints 6.2. Example of an OCF resource with a disabled health check 6.1. An OCF resource with two recurring health checks performing different levels of checks 5.10. An OCF resource with custom timeouts for its implicit actions 5.9. An OCF resource with a recurring health check 5.8. Displaying the metadata for the Dummy resource agent template 5.7. An example OCF resource with instance attributes 5.6. An LSB resource with cluster options 5.5. Deleting an option that is listed twice 4.1. An example of the fields set for a cib object 3.2. Using a sandbox to make multiple changes atomically 3.1. OCF Return Codes and How They are Handled E.1. Types of recovery performed by the cluster B.4. Authoritative Sources for State Information 12.2. Environment variables supplied with Master notify actions 12.1. Role implications of OCF return codes 10.9. Additional constraint options relevant to multi-state resources 10.8. Multi-state specific resource configuration options 10.7. Properties of a Multi-State Resource 10.6. Environment variables supplied with Clone notify actions 10.5. Clone specific configuration options 10.4. Common Options for a 'ping' Resource 10.1. Extra top-level CIB options for remote access 9.3. Environment Variables Used to Connect to Remote Instances of the CIB 9.2. Properties of a Collocation Constraint 8.1. Properties of an Ordering Constraint 6.3. Options for Simple Location Constraints 6.2. Properties Maintained by the Cluster 3.4. Resource history of a pingd clone with multiple jobs A monitor operation performed by the cluster to determine the current state of the apcstonith resource 12.5. A record of the apcstonith resource 12.4. Example set of transient node attributes for node "cl-virt-1" 12.3. A bare-bones status entry for a healthy node called cl-virt-1 12.2. Obtaining a list of STONITH Parameters 12.1. How the cluster translates the pingd constraint 11.1. The result of using crm_attribute to specify which kernel pcmk-1 is running 6.1. ![]() Creating and displaying the active sandbox 2.7. Searching for STONITH related configuration items 2.6. Safely using an editor to modify a subsection of the cluster configuration 2.5. Safely using an editor to modify the cluster configuration 2.4. Upgrading the Configuration from 0.6 F.1. How Does the Cluster Interpret the OCF Return Codes? B.3.1. Multi-state - Resources That Have Multiple Modes 10.3.1. Clones - Resources That Should be Active on Multiple Hosts 10.2.1. Reloading Services After a Definition Change 10. Reusing Rules, Options and Sets of Operations 9.5. Moving Resources Due to Connectivity Changes 9.3.4. Specifying When Recurring Actions are Performed 9.3. Connecting to the Cluster Configuration from a Remote Machine 9.2. Using Rules to Control Cluster Options 8.6. Using Rules to Control Resource Options 8.5. Using score-attribute Instead of score 8.4. Using Rules to Determine Resource Location 8.3.1. Receiving Notification of Cluster Events 7.1. Placing Resources Relative to other Resources 6.4.1. Specifying the Order Resources Should Start/Stop In 6.3.1. What if Two Nodes Have the Same Score 6.3. Deciding Which Nodes a Resource Can Run On 6.2.1. When Resources Take a Long Time to Start/Stop 5.8.2. Setting Global Defaults for Operations 5.8.1. Setting Global Defaults for Resource Options 5.6. When Options are Listed More Than Once 4. Querying and Setting Cluster Options 3.2.3. Do I Need to Update the Configuration on all Cluster Nodes? 3. Making Configuration Changes in a Sandbox 2.7. Updating the Configuration Without Using XML 2.6. Quickly Deleting Part of the Configuration 2.5. How Should the Configuration be Updated? 2.4. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |