Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1469584

Summary:	[Docs][RFE][Director] Batch size configuration for node deployments
Product:	Red Hat OpenStack	Reporter:	Dan Macpherson <dmacpher>
Component:	documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Lopes <mlopes>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	12.0 (Pike)	CC:	lbopf, mburns, mlopes, srevivo
Target Milestone:	ga	Keywords:	Documentation, FutureFeature, Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	docs-accepted
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-19 04:20:45 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:
Bug Depends On:	1427326
Bug Blocks:

Description Dan Macpherson 2017-07-11 14:08:38 UTC

== DECRIPTION ==
Deploying an overcloud with a large number nodes at once can result in a failed deployment (similar to the symptoms described in BZ 1410977 on OSP10). Rules of thumb have evolved to workaround this consisting of: 

1. Using scheduler hints to pin node placement instead of just letting tripleo's nova scheduler schedule the ironic nodes
2. Ensuring the undercloud.conf IP ranges are not too small
3. Deploying in batches 

== DOCS IMPACT ==
Requires some minor documentation on changing the Batch Size and note not to exceed 30.

Comment 1 Lucy Bopf 2017-08-08 02:36:25 UTC

Assigning to Dan for review.