[Pacemaker] ANNOUNCE: Pacemaker 0.7.0 (unstable) now available
Andrew Beekhof
abeekhof at suse.de
Wed Jun 25 15:00:38 UTC 2008
Hi All,
This has taken a bit longer than I intended, but it's finally time for
a new Pacemaker feature release.
There's lots of good stuff, the configuration should be a little
easier to understand (yet more powerful), has lower performance
overheads and some great improvements to the CLI tools - including the
ability to test configuration changes in a sandbox before committing
them to the cluster!
It also comes with a stack independent pingd and a STONITH subsystem
(Dejan is maintaining that) which supports both OpenAIS and Heartbeat.
Packages for Pacemaker and it's immediate dependancies can be
downloaded from:
http://software.opensuse.org/download/server:/ha-clustering:/UNSTABLE
To avoid wasting resources, I'll be enabling distributions on an as-
needed basis.
So if you can't find packages for your favorite one, just let me know
and I'll enable it.
The source can be obtained from:
http://hg.clusterlabs.org/pacemaker/unstable-0.7/archive/Pacemaker-0.7.0.tar.bz2
For a breakdown of the available packages and what parts are optional,
please refer to
http://clusterlabs.org/mw/Install#Package_List
As I hope is clear from the subject and included URLs, 0.7 is NOT
STABLE.
That means:
- there will be new features added (or possibly removed)
- the behavior of features may change
- the configuration syntax may change
- some features may not be stable or complete
For more details:
http://www.clusterlabs.org/mw/Releases
Also, it means that there is plenty of things that are not yet
documented.
That process starts soon but I'm always happy to answer questions on
anything that is unclear.
regards,
Andrew
Begin lazy paste from the changelog...
* Update source tarball to revision: bde0c7db74fb tip
* Statistics:
Changesets: 439
Diff: 676 files changed, 41310 insertions(+), 52071
deletions(-)
* Changes added since stable-0.6
+ High: A new tool for setting up and invoking CTS
+ High: Admin: All tools now use --node (-N) for specifying node
unames
+ High: Admin: All tools now use --xml-file (-x) and --xml-text (-
X) for specifying where to find XML blobs
+ High: cib: Cleanup the API - remove redundant input fields
+ High: cib: Implement CIB_shadow - a facility for making and
testing changes before uploading them to the cluster
+ High: cib: Make registering per-op callbacks an API call and
renamed (for clarity) the API call for requesting notifications
+ High: Core: Add a facility for automatically upgrading old
configurations
+ High: Core: Adopt libxml2 as the XML processing library - all
external clients need to be recompiled
+ High: Core: Allow sending TLS messages larger than the MTU
+ High: Core: Fix parsing of time-only ISO dates
+ High: Core: Smarter handling of XML values containing quotes
+ High: Core: XML memory corruption - catch, and handle, cases
where we're overwriting an attribute value with itself
+ High: Core: The xml ID type doesn't allow UUIDs that start with a
number
+ High: Core: Implement XPath based versions of query/delete/
replace/modify
+ High: Core: Remove some HA2.0.(3,4) compatability code
+ High: crmd: Overhaul the detection of nodes that are starting vs.
failed
+ High: PE: Bug LF:1459 - Allow failures to expire
+ High: PE: Have the PE do non-persistent configuration upgrades
before performing calculations
+ High: PE: Replace failure-stickiness with a simple 'migration-
threshold'
+ High: TE: Simplify the design by folding the tengine process into
the crmd
+ Medium: Admin: Bug LF:1438 - Allow the list of all/active
resource operations to be queried by crm_resource
+ Medium: Admin: Bug LF:1708 - crm_resource should print a warning
if an attribute is already set as a meta attribute
+ Medium: Admin: Bug LF:1883 - crm_mon should display fail-count
and operation history
+ Medium: Admin: Bug LF:1883 - crm_mon should display operation
timing data
+ Medium: Admin: Bug N:371785 - crm_resource -C doesn't also clean
up fail-count attributes
+ Medium: Admin: crm_mon - include timing data for failed actions
+ Medium: ais: Read options from the environment since objdb isn't
completely usable yet
+ Medium: cib: Add sections for op_defaults and rsc_defaults
+ Medium: cib: Better matching notification callbacks (for
detecting duplicates and removal)
+ Medium: cib: Bug LF:1348 - Allow rules and attribute sets to be
referenced for use in other objects
+ Medium: cib: BUG LF:1918 - By default, all cib calls now timeout
after 30s
+ Medium: cib: Detect updates that decrease the version tuple
+ Medium: cib: Implement a client-side operation timeout - Requires
LHA update
+ Medium: cib: Implement callbacks and async notifications for
remote connections
+ Medium: cib: Make cib->cmds->update() an alias for modify at the
API level (also implemented in cibadmin)
+ Medium: cib: Mark the CIB as disconnected if the IPC connection
is terminated
+ Medium: cib: New call option 'cib_can_create' which can be passed
to modify actions - allows the object to be created if it doesn't
exist yet
+ Medium: cib: Reimplement get|set|delete attributes using XPath
+ Medium: cib: Remove some useless parts of the API
+ Medium: cib: Remove the 'attributes' scaffolding from the new
format
+ Medium: cib: Implement the ability for clients to connect to
remote servers
+ Medium: Core: Add support for validating xml against RelaxNG
schemas
+ Medium: Core: Allow more than one item to be modified/deleted in
XPath based operations
+ Medium: Core: Fix the sort_pairs function for creating sorted xml
objects
+ Medium: Core: iso8601 - Implement subtract_duration and fix
subtract_time
+ Medium: Core: Reduce the amount of xml copying occuring
+ Medium: Core: Support value='value+=N' XML updates (in addtion to
value='value++')
+ Medium: crmd: Add support for lrm_ops->fail_rsc if its available
+ Medium: crmd: HB - watch link status for node leaving events
+ Medium: crmd: Bug LF:1924 - Improved handling of lrmd disconnects
and shutdowns
+ Medium: crmd: Do not wait for actions with a start_delay over 5
minutes. Confirm them immediately
+ Medium: PE: Bug LF:1328 - Don't fencing nodes in clusters without
managed resources
+ Medium: PE: Bug LF:1461 - Give transient node attributes (in
<status/>) preference over persistent ones (in <nodes/>)
+ Medium: PE: Bug LF:1884, Bug LF:1885 - Implement N:M ordering and
colocation constraints
+ Medium: PE: Bug LF:1886 - Create a resource and operation
'defaults' config section
+ Medium: PE: Bug LF:1892 - Allow recurring actions to be triggered
at known times
+ Medium: PE: Bug LF:1926 - Probes should complete before stop
actions are invoked
+ Medium: PE: Fix the standby when it's set as a transient attribute
+ Medium: PE: Implement a global 'stop-all-resources' option
+ Medium: PE: Implement cibpipe, a tool for performing/simulating
config changes "offline"
+ Medium: PE: We don't allow colocation with specific clone instances
+ Medium: Tools: pingd - Implement a stack-independant version of
pingd
+ Medium: xml: Ship an xslt for upgrading from 0.6 to 0.7
More information about the Pacemaker
mailing list