Bug 1303090

Summary:	[Docs] [Director] Section 7.6 should add flavor information
Product:	Red Hat OpenStack	Reporter:	Ruchika K <rkharwar>
Component:	documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED NOTABUG	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0 (Kilo)	CC:	adahms, rkharwar, yeylon
Target Milestone:	ga	Keywords:	Documentation
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-09 03:08:54 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:
Embargoed:

Description Ruchika K 2016-01-29 14:06:06 UTC

Description of problem:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html-single/Director_Installation_and_Usage/index.html#sect-Scaling_the_Overcloud 
Section 7.6 (regarding scaling a cloud) it appears there should be a few steps on flavor association of the newly added node to the type control/compute/ceph

Version-Release number of selected component (if applicable):
7.2

How reproducible:

NA
Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Andrew Dahms 2016-02-08 03:04:26 UTC

Assigning to Dan for review.

Comment 3 Dan Macpherson 2016-02-09 02:19:26 UTC

Hi Ruchika,

The flavor information should already be created for either the Basic or Advanced scenario:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html-single/Director_Installation_and_Usage/index.html#sect-Creating_Flavors_for_the_Basic_Scenario

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html-single/Director_Installation_and_Usage/index.html#sect-Advanced-Creating_Hardware_Profiles

These flavors are linked to the node using the following command (which is included in the instructions):

$ ironic node-update [NODE UUID] add properties/capabilities='profile:compute,boot_option:local'

The this sets the profile to 'compute'. This links to the compute flavor, which is also tagged 'profile:compute'. The director deploys the node as a flavor depending on what it reads for 'profile:*' for both the node and the flavor.

If you do not set a profile, the director defaults to the 'baremetal' flavor, which should also already be created as per the instructions above.

Please let me know if there was anything else to add to this bug. If not, I'll close it.