Bug 1381730

Summary:	Ability to install different qcow2 images on compute and controller nodes
Product:	Red Hat OpenStack	Reporter:	bigswitch <rhosp-bugs-internal>
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	9.0 (Mitaka)	CC:	ccopello, dbecker, dcadzow, dmacpher, jslagle, mburns, morazi, rhel-osp-director-maint, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-11 16:56:45 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:

Description bigswitch 2016-10-04 20:37:22 UTC

Description of problem:

During the overcloud deployment, we patch a few rpms into the qcow2 image (eg: ivs.rpm) which we do not want on the controller nodes. Likewise, we will need to have different rpms on compute nodes based on the type of virtual switch installed on them (IVS vs NFVSwitch). Hence, we need the ability use and specify different qcow2 images for compute and controller nodes.

Comment 1 Mike Burns 2016-10-21 17:20:02 UTC

James,  this exists today, right?

Comment 2 James Slagle 2016-10-25 10:49:15 UTC

yes, have a look at the paramters called <role>Image in overcloud-without-mergepy.yaml.

The controller image is specified with the controllerImage paramater.
The compute image is specified with the NovaImage paramter.

Comment 3 Mike Burns 2016-11-04 17:21:23 UTC

Thanks James.

Moving this to documentation so we can include the info in our docs.

Comment 4 Dan Macpherson 2018-03-19 11:15:29 UTC

Scoping old bug.

So this should now be do-able from OSP10+ using the [ROLE]Image parameter. For example, ControllerImage.

There are some other parameters that are [ROLE]-based and are worth documenting for OSP10.

For OSP11+, we introduced the Overcloud Params guide. However, [ROLE]Image didn't make it for some reason:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html/overcloud_parameters/role_based_parameters

Need to investigate why.

Comment 7 Dan Macpherson 2019-12-11 16:56:45 UTC

Parameter now available in OSP13 guide:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/overcloud_parameters/index#role-based-parameters