This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag

Homepage

About Us

Contact Us

Legal Info

How To Contribute

Security Issues

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.
To get rid of this notice, you may want to browse the old wiki instead.

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2017-07-20 14:50:43

Resource Agent

A resource agent is an encapsulation of information about a particular kind of cluster resource. It knows how to do several kinds of things for its ResourceAgentType, and for a ResourceInstance of its own type. All the types of resource agents we support resemble standard LSB init scripts a great deal.

There are three types of agents supported by v2 of Heartbeat when used with the CRM. In order of encouraged usage they are:

  1. OCFResourceAgent

  2. LSBResourceAgent

  3. HeartbeatResourceAgent

When crm yes is not present in ha.cf, or version 1.x is used, OCFResourceAgents are not supported.

Operations which Heartbeat can perform on a ResourceInstance include:

  • start - enable or start the given resource

  • stop - disable or stop the given resource

  • status - return the status of the given resource

NOTE: In the OCF spec, the status operation has been replaced with monitor.

Additionally, OCF agents must support:

Resource agents are typically (but not necessarily) coded as shell scripts. They are synchronous in nature. That is, you start them, and they complete some time later, and you are expected to wait for them to complete. Certain operations (notably start, stop and monitor) may take considerable time to complete. Considerable time means seconds to many minutes in some cases.

NOTE: Heartbeat cluster resources should only be started/stopped by Heartbeat itself -- e.g., shared filesystems managed by Heartbeat should not be automounted by the operating system.

See Also

HeartbeatResourceAgent, OCFResourceAgent, and LSBResourceAgent