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

Bug 1249836

Summary:	[RFE] openstack baremetal configure boot needs an image suffix option
Product:	Red Hat OpenStack	Reporter:	Graeme Gillies <ggillies>
Component:	python-tripleoclient	Assignee:	Marek Aufart <maufart>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Raviv Bar-Tal <rbartal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	achernet, ddomingo, dtantsur, ggillies, hbrock, jcoufal, jslagle, maufart, mburns, mcornea, rhel-osp-director-maint
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-0.1.1-1.el7ost	Doc Type:	Enhancement
Doc Text:	With the 'openstack baremetal' utility, you can now specify specific images during boot configuration. Specifically, you can now use the '--deploy-kernel' and '--deploy-ramdisk' options to specify a kernel or ramdisk image, respectively.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-04 16:54:35 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 Graeme Gillies 2015-08-03 23:44:35 UTC

Currently when you run

openstack baremetal configure boot

it will look for images with fixed names (overcloud-full, bm-deploy) and configure the ironic machines to use those images

It would be good to have the ability to specify an image suffix to the command and the tool will look for images with that suffix and use them instead. E.g.

openstack baremetal configure boot 2015-06-30.1

Would use the images

bm-deploy-kernel-2015-06-30.1
bm-deploy-ramdisk-2015-06-30.1
overcloud-full-2015-06-30.1
overcloud-full-initrd-2015-06-30.1
overcloud-full-vmlinuz-2015-06-30.1

That way we can start to allow people to utilise multiple images inside the undercloud glance, to do testing and rollback of new/old images

Regards,

Graeme

Comment 3 Marek Aufart 2015-09-10 07:44:09 UTC

More generic way was chosen - added options to specify kernel and ramdisk image names.

Comment 5 Raviv Bar-Tal 2016-03-24 09:05:17 UTC

In the scenarion when use run the --deploy-ramdisk and the --deploy-kernel in two different commands the second image is changed back to default 


Reproduce:
1. set deploy ramdisk --deploy-ramdisk my-ramdisk
*deployed_ramdisk of ironic node is changed

2. set deploy  kernel --deploy-kernel my-kernel
* deployed_kernel of ironic node is changed

** deployed_ramdisk of ironic node is changed back to bm-deploy-ramdisk

Comment 6 Marek Aufart 2016-03-24 09:16:40 UTC

This behaviour happends because both arguments (--deploy-ramdisk and --deploy-kernel) have a default value, which "changes back" the unused argument.

I don't think this is a failure. Anyway we need clarify it.

Comment 8 Mike Burns 2016-04-07 20:47:27 UTC

This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 9 Graeme Gillies 2016-04-12 00:50:31 UTC

Has this actually been implemented in OSP 8? I'm reading the comments and it looks like some functionality was implemented, but I'm not entirely sure

Regards,

Graeme

Comment 10 Marek Aufart 2016-04-13 08:30:07 UTC

This was implemented (is in upstream). The bug failed QA because, I believe, misunderstanding, so I added needinfo there.

Marek

Comment 11 Dmitry Tantsur 2016-10-04 16:54:35 UTC

Hi folks, I believe this feature was done long ago, and it's fair to request both arguments to be provided. If you think it's a UX problem, please open another report.