Red Hat Bugzilla – Bug 1162961
[RFE][horizon]: Add Bootable flag to Create and Edit Volume Panels
Last modified: 2015-08-05 09:15:47 EDT
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/volume-bootable-flag. Description: Add a "Bootable" checkbox to the "Project -> Volumes" create and edit panels. Motivation: This will expose the current Cinder CLI command "cinder set-bootable" in the Horizon UI. $ cinder help set-bootable usage: cinder set-bootable <volume> <True|true|False|false> Update bootable status of a volume. Positional arguments: <volume> ID of the volume to update. <True|true|False|false> Flag to indicate whether volume is bootable. UX: 1) Need to add a new "Bootable" checkbox to the "Project -> Volumes" "Create Volume" dialog. It will be shown/hidden and set to a default value based on the following: Volume Source = "Image" - checkbox will be hidden. Created volume will be bootable. Volume Source = "No source, empty volume" - checkbox will be shown and set to false. Volume Source = "Volume" - checkbox will be shown and will be set to the "bootable" state of the selected source volume. In the case of creating a volume from an "image", the "cinder create" volume command will automatically make the volume bootable. In the case of creating a volume from no source, if the user checks the "Bootable" flag, an additional "cinder set-bootable" call will be made. In the case of creating a volume from a source volume, an additional "cinder set-bootable" call will be made IF the new volume will have a different bootable state than that of the source volume. 2) Need to add a new "Bootable" checkbox to the "Project -> Volumes" "Edit Volume" dialog. It will be initially set to the current bootable state of the volume. Outside Dependencies: N/A Requirements Update Required: N/A Doc Impact: N/A Specification URL (additional information): None
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1548