Lesson plan

Linux-HA

The Linux-HA (High-Availability Linux) project provides a high-availability (clustering) solution for Linux, FreeBSD, OpenBSD, Solaris and Mac OS X which promotes reliability, availability, and serviceability (RAS). The project's main software product is Heartbeat, a GPL-licensed portable cluster management program for high-availability clustering. Its most important features are: * no fixed maximum number of nodes - Heartbeat can be used to build large clusters as well as very simple ones * resource monitoring: resources can be automatically restarted or moved to another node on failure * fencing mechanism to remove failed nodes from the cluster * sophisticated policy-based resource management, resource inter-dependencies and constraints * time-based rules allow for different policies depending on time * several resource scripts (for Apache, IBM Db2, Oracle, PostgreSQL etc.) included * Graphical user interface (GUI) for configuring, controlling and monitoring resources and nodes

Back to article

Article summary

The Linux-HA (High-Availability Linux) project provides a high-availability (clustering) solution for Linux, FreeBSD, OpenBSD, Solaris and Mac OS X which promotes reliability, availability, and serviceability (RAS). The project's main software product is Heartbeat, a GPL-licensed portable cluster management program for high-availability clustering. Its most important features are: * no fixed maximum number of nodes - Heartbeat can be used to build large clusters as well as very simple ones * resource monitoring: resources can be automatically restarted or moved to another node on failure * fencing mechanism to remove failed nodes from the cluster * sophisticated policy-based resource management, resource inter-dependencies and constraints * time-based rules allow for different policies depending on time * several resource scripts (for Apache, IBM Db2, Oracle, PostgreSQL etc.) included * Graphical user interface (GUI) for configuring, controlling and monitoring resources and nodes

Key claims

  1. release date: 1998-11-15 — source: Wikipedia · confidence 0.95

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. The record states that the release date is "1998-11-15". What evidence would count against this claim?
  3. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  4. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.