Bug 1376549

Summary:	Add new cluster considerations section to Pacemaker reference for rhel 6
Product:	Red Hat Enterprise Linux 6	Reporter:	Steven J. Levine <slevine>
Component:	doc-Cluster_General	Assignee:	Steven J. Levine <slevine>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.9	CC:	cfeist, ctowsley, ecs-bugs, rhel-docs, syangsao
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1373624	Environment:
Last Closed:	2017-03-22 19:12:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1373624
Bug Blocks:

Description Steven J. Levine 2016-09-15 16:45:30 UTC

This bug and a separate one about DHCP were turned into a new section of the Pacemaker reference for RHEL 7 that should be added to the RHEL 6 document as well.

+++ This bug was initially created as a clone of Bug #1373624 +++

The RHEL 7 HA Add-On Reference only mentions the 16-node limit for clusters as an aside in the section on Pacemaker remote. This needs to be included in a more prominent place.

(And also added to the RHEL 6 Pacemaker manual)

Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

--- Additional comment from Steven J. Levine on 2016-09-15 12:41:23 EDT ---

This limitation has been added to the 7.3 draft as part of section 1.5:

http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Enterprise_Linux-7-High_Availability_Add-On_Reference%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#s1-configfileoverview-HAAR

Comment 1 Chris Feist 2016-11-04 22:17:16 UTC

One thing that I would add in the section about the 16 node limitation is that by utilizing pacemaker_remote you can go far above 16 nodes (I don't have the actual limits for pacemaker remote, but I will see if I can find them out).

Comment 2 Steven J. Levine 2016-11-17 16:32:01 UTC

Chris:  The actual note about 16-nodes in the RHEl 7 doc does specify that you can use pacemaker remote to get around this (although it doesn't give an upper limit).

Red Hat does not support cluster deployments greater than 16 full cluster nodes. It is possible, however, to scale beyond that limit with remote nodes running the pacemaker_remote service. For information on the pacemaker_remote service, see Section 9.3, “The pacemaker_remote Service”.

Comment 4 Steven J. Levine 2016-11-17 17:49:34 UTC

Section 1.4 here:

http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Enterprise_Linux-6-Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#s1-configconsider-HAAR

Comment 6 Steven J. Levine 2017-03-22 19:12:50 UTC

The RHEL 6 document on the portal now contains this new section, as section 1.4:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker/s1-configconsider-HAAR.html