Description of problem:
Pacemaker is effectively a superset of what rgmanager can do.
Some of the requested features of rgmanager which are already features of Pacemaker:
* Resource-dependency model instead of service model (upgrade path required)
* Time-based resource control (bug #310361)
* Per-resource restart counters (bug #449833)
* Disable monitoring of specific resources (bug #449835)
* Promote/demote/alternate behaviors (bug #451848)
This bug depends on a way to preserve rolling upgrade:
1. bug #303171 - we must be able to stop rgmanager in RHEL5 without stopping
services, so that when we start pacemaker, it can just "take over" running services
2. bug #456897 - we must be able to provide customers with an upgrade path for
their rgmanager configuration
*** Bug 493474 has been marked as a duplicate of this bug. ***
Release note added. If any revisions are required, please set the
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
Pacemaker component in RHEL6.0 is TechPreview. It is not fully integrated with the Red Hat cluster stack, but can be used as a standalone component for managing highly available services.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
@@ -1 +1 @@
-Pacemaker component in RHEL6.0 is TechPreview. It is not fully integrated with the Red Hat cluster stack, but can be used as a standalone component for managing highly available services.+Pacemaker, a scalable high-availability cluster resource manager, is included in Red Hat Enterprise Linux 6 as a Technology Preview. Pacemaker is not fully integrated with the Red Hat cluster stack.
The packages are included, but I have no idea what is needed to verify that everything that needs to be included IS included. I could use some direction from development.
A quick look at the packages I noticed that there isn't an init script, nor a "pacemaker" man page.
Since this is a tech-preview package I expect that verifying the package is included and complete is enough to satisfy this bug. Verification of this bug in no way states that pacemaker works or that you can migrate from rgmanager.
Indeed there is no init script nor binary called pacemaker.
I can imagine that this was probably quite confusing.
If you want to start pacemaker and see it running, then I'd recommend the Clusters from Scratch guide (in PDF or html):
Otherwise, look for me on the internal IRC (beekhof on #cluster) or email and I'll help any way I can.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.