Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionSteven J. Levine
2017-04-20 21:03:13 UTC
For RHEL 7.4 we will be adding support for managing containers with Pacemaker, as technical preview. This BZ is to provide a placeholder for how to address the documentation.
Much is not yet set on this feature, so my proposal is that for this technical preview we provide the documentation for this feature as a Portal article, introducing the feature and noting its uses and including a configuration procedure.
As the interface changes it should be much easier to update a Portal article than the Pacemaker reference, and the updates can be collaborative as we learn more things to note. If at any time we feel this is stable enough to move to the Pacemaker reference (as a standalone chapter), we can do that, but my first pass thought is that we leave it as a Portal article until it is fully supported.
We can add relevant features BZs directly to this BZ.