Savaged by Softdog, a Cautionary Tale
Hardware is imperfect, and software contains bugs. Don’t use software based watchdogs and expect to survive the latter.
Cluster admins are naturally a cautious bunch, so in order to make 1.1 more palatable, we have also created two new schemas.
Schemas can be thought of as a contract between the developers and admins. They are a declaration of what we support.
The set is the new set of validation types:
pacemaker-1.0 is (and will remain) identical to what people are using now
When new features are added, their configuration syntax will first appear in pacemaker-1.1. If, based on your feedback, a feature’s syntax needs to be modified we will change it here and solicit further feedback.
Once a feature has been locked down and become stable, its configuration pieces will be added to pacemaker-1.2. Once a feature appears in pacemaker-1.2, we will not change its syntax in any 1.1 or 1.2 release.
It means that when used with the pacemaker-1.0 or pacemaker-1.2 schemas, 1.1 can be safely used in production in the same manner as 1.0 is today.
Yes. 1.0 i still supported and will recieve all relevant bug fixes until at least 2012. See our releases page.
Users of RPM-based distributions will be able to install in the usual manner. However, to avoid forcing everyone to upgrade, packages will be located under:
At this time the intention is to only produce packages for the most recent openSUSE (11.2), Fedora (12), and EPEL (5) based distributions. If you would like to try 1.1 but your distribution/version is not listed, please contact the project and we’ll see what we can do.
Packages should be available in the next week “or so”.