Booting from volume shouldn't require specifying an image
Bug #1008622 reported by
Lorin Hochstein
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Nikola Đipanov |
Bug Description
Booting from volume fails unless the user specifies an image:
$ nova boot --flavor 2 --key_name foo --block_
Generates the following error:
Invalid imageRef provided. (HTTP 400)
In general, booting from a volume should not require an image being specified.
See https:/
Changed in nova: | |
status: | New → Confirmed |
summary: |
- Booting from volume requires specifying an image + Booting from volume shouldn't require specifying an image |
Changed in nova: | |
importance: | Undecided → Wishlist |
Changed in nova: | |
assignee: | nobody → Sathish Nagappan (sathish-nagappan) |
Changed in nova: | |
assignee: | Sathish Nagappan (sathish-nagappan) → nobody |
Changed in nova: | |
assignee: | nobody → Nikola Đipanov (ndipanov) |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/16099 github. com/openstack/ nova/commit/ 1d00dfcfbb9bdef f358503fefefc7e 6e7b4903eb
Committed: http://
Submitter: Jenkins
Branch: master
commit 1d00dfcfbb9bdef f358503fefefc7e 6e7b4903eb
Author: Nikola Dipanov <email address hidden>
Date: Wed Nov 7 18:56:35 2012 +0100
Boot from volume without image supplied
This patch allows for booting instances without supplying an image if
there is block device mapping supplied. It makes changes to nova API
and
compute services to handle requests that do not have any image
supplied.
Also it makes rescue and rebuild work with instances started from
volume.
Finally the patch introduces tests to make sure the system acts as
expected, and in the process fixes and refactors some old tests to make
them test for cases this new functionality can introduce.
This patch is intended to be a proof of concept and a first step /etherpad. openstack. org/grizzly- boot-from- volumes.
towards
a more cleaner interface for booting from volumes, outlined in
https:/
This patch also introduces a slight modification of the nova API so I mapping provided.
am flagging it with DocImpact. The change is that if the os-volumes
extension is used ImageRef does not need to be supplied to the create
server API call provided there is block_device_
Also note that this is the first step towards introducing a 'volume' device_ mapping (they will still be used but not for the boot
parameter
for starting instances which will replace the somewhat unintuitive
block_
device).
This patch is coupled with I5ba9b0f35a5084 aa91eca260f46ca c83b8b6591e
that provides changes to the nova client.
Implements: blueprint improve- boot-from- volume
Fixes bug #1008622
Change-Id: I530760cfaa5eb0 cae590c7383e084 0c6b3f896b9