yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

As noted in comment 3, if you want to use a specific type of volume when
booting a server, you need to first create that server via cinder APIs
with the proper type, then provide that volume to the nova boot command
so we boot from that volume (and attach it to the created server).  Nova
isn't updating the boot from server functionality to allow sending a
volume type since we don't want to expand our footprint in proxying
other services APIs.

** Changed in: nova
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1523447

Title:
  When multiple cinder backend enabled ,Cinder picks up first enabled
  backend during  boot from image(create new volume)

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  Steps to reproduce-

  	1- Enable Cinder Block storage driver .For example - HPE 3PAR FC/iSCSI or HPE Lefthand .
  	2- Enable another Cinder Block storage driver . Eg VMWARE VMFS driver.
  	3-  Try to launch an instance by selecting option "boot from image (Create new volume)" using image <image-name>.VMDK

  Actual Behaviour  -

   Cinder uses the volume type info to associate the request during the
  create volume call. However in this case it goes with the default
  volume host, that would be the first one in the enabled backend as
  there is no way to specify volume type  during this operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1523447/+subscriptions