[Yahoo-eng-team] [Bug 1523447] Re: When multiple cinder backend enabled , Cinder picks up first enabled backend during boot from image(create new volume)

2016-03-03 Thread Matt Riedemann
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

[Yahoo-eng-team] [Bug 1523447] Re: When multiple cinder backend enabled , Cinder picks up first enabled backend during boot from image(create new volume)

2015-12-07 Thread deepali verneya
** No longer affects: cinder -- 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

[Yahoo-eng-team] [Bug 1523447] Re: When multiple cinder backend enabled , Cinder picks up first enabled backend during boot from image(create new volume)

2015-12-07 Thread Mitsuhiro Tanino
This is because Nova does not pass any volume type during volume creation at "boot from image (Create new volume)". There is a proposal to support volume type during "boot from image (Create new volume)" but based on the comment on review 241065, this API will be removed in the future. Therefore,