Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1249836 - [RFE] openstack baremetal configure boot needs an image suffix option
[RFE] openstack baremetal configure boot needs an image suffix option
Status: CLOSED CURRENTRELEASE
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 8.0 (Liberty)
Assigned To: Marek Aufart
Raviv Bar-Tal
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-03 19:44 EDT by Graeme Gillies
Modified: 2017-07-03 19:10 EDT (History)
11 users (show)

See Also:
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 12:54:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 221655 None None None Never

  None (edit)
Description Graeme Gillies 2015-08-03 19:44:35 EDT
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 03:44:09 EDT
More generic way was chosen - added options to specify kernel and ramdisk image names.
Comment 5 Raviv Bar-Tal 2016-03-24 05:05:17 EDT
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 05:16:40 EDT
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 16:47:27 EDT
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 9 Graeme Gillies 2016-04-11 20:50:31 EDT
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 04:30:07 EDT
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 12:54:35 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.