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.

Bug 788636

Summary: Document RRP configuration through ccs command in 6.4
Product: Red Hat Enterprise Linux 6 Reporter: Steven J. Levine <slevine>
Component: doc-Cluster_AdministrationAssignee: Steven J. Levine <slevine>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3CC: cfeist, fdinitto, lhh, slevine
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-25 18:31:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Steven J. Levine 2012-02-08 16:52:03 UTC
As per BZ#733298, RHEL 6.3 will allow configuration of Redundant Ring Protocol. As per BZ#758823, there will be updates to the ccs command to account for this. This BZ is to note that this feature will need to be added to the ccs documentation in the Cluster Administration document.

Comment 1 Steven J. Levine 2012-03-13 16:17:32 UTC
Moving this to RHEL 6.4, as per Sayan's instructions:

Let's not document RRP now. We'll will work with our one customer to teach them how to use it.

Sayan

On 03/13/2012 12:11 PM, Steven Levine wrote:
> At this point, based on my understanding of where RRP support stands, I
> would like to confirm and clarify the documentation plans for how to
> address (or not address) this feature in RHEL 6.3.
>
> Although there are 2 components to this feature (corosync and DLM over
> SCTP), my understanding after talking with Dave Teigland is that you
> would really need to use both components for the feature to be useful.
> This would mean that even if the corosync aspect is supported, if the
> DLM over SCTP aspect is in technical preview then RRP support as a whole
> would remain in technical preview. Is that correct?
>
> Or, specifically, do I document RRP configuration (with luci, ccs, and
> the cluster.conf file) in RHEL 6.3?
>
> In the past, in cluster documentation, we have not documented features
> in tech. preview in the regular documentation. Those features are
> documented in the release notes and called out as being in technical
> preview, but once they are in the regular documentation set on
> redhat.com they imply some level of promise that there will be full
> support in the next (or a near future) release. Those released documents
> have a life of their own. It seems a bad idea to document a
> not-yet-supported feature that we may withdraw, in the standard document
> set.
>
> So even though Conga in 6.3 shows a configuration screen for RRP
> components, and the ccs command supports this as well, I am currently
> thinking that I should not call out this feature in the 6.3 Cluster
> Administration document (or suggest that John Ha add an overview of the
> feature to the HA Add-On Overview).
>
> Does this make sense?
>
> -Steven
>
>
>
>
>
>
>
>
>
>
>
>