Bug 1041990

Summary:	[RFE][horizon]: Use new block device mapping for booting from volume
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aortega, athomas, jschluet, markmc, mrunge, nbarcet, yeylon
Target Milestone:	beta	Keywords:	FutureFeature
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/horizon-block-device-mapping-v2
Whiteboard:	upstream_milestone_liberty-1 upstream_status_implemented upstream_definition_approved
Fixed In Version:	python-django-horizon-8.0.0-5.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-07 20:58:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2013-12-12 20:28:02 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/horizon-block-device-mapping-v2.

Description:

Right now, when booting from a volume, horizon uses a different block_device_mapping depending on the source: v1 if the source is  a volume or an snapshot and v2 if it is an image.

https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L571

The "create instance" menu should check if BMDv2 extension is enabled in the server side. If that is the case, booting from a volume, a volume created from a snapshot or an image should be enabled and using the BDMv2 API call.

If only BDMv1 is enabled in the server, booting an instance from a volume created from an image shouldn't be allowed. All the other options would use the BDMv2 API call.

In the case where none of the extensions is enabled, it shouldn't be allowed to boot from a volume at all.

Specification URL (additional information):

None

Comment 4 Ido Ovadia 2016-02-23 17:06:58 UTC

Verified on: python-django-horizon-8.0.1-1.el7ost.noarch
========================================================
1. Sanity test - Pass
2.  Booting from Volume - Pass
    Booting from image (create new volume) - Pass 
    Booting from volume snapshot (create new volume) - Pass


Note: All extensions are enabled by default, can't configure which version to   
use (BMDv1 or BMDv2)

Comment 6 errata-xmlrpc 2016-04-07 20:58:41 UTC

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://rhn.redhat.com/errata/RHEA-2016-0603.html