grizzly: Boot from volume without image supplied

Bug #1087051 reported by Tom Fifield
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openstack-api-site
Fix Released
Medium
Diane Fleming
openstack-manuals
Fix Released
Medium
Diane Fleming

Bug Description

If https://review.openstack.org/16099 is merged, a new feature is added to nova.

    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
    towards
    a more cleaner interface for booting from volumes, outlined in
    https://etherpad.openstack.org/grizzly-boot-from-volumes.

    This patch also introduces a slight modification of the nova API so I
    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_mapping provided.

    Also note that this is the first step towards introducing a 'volume'
    parameter
    for starting instances which will replace the somewhat unintuitive
    block_device_mapping (they will still be used but not for the boot
    device).

    This patch is coupled with I5ba9b0f35a5084aa91eca260f46cac83b8b6591e
    that provides changes to the nova client.

Tom Fifield (fifieldt)
Changed in openstack-api-site:
milestone: none → grizzly
Changed in openstack-manuals:
milestone: none → grizzly
tags: added: compute-api nova
Changed in openstack-manuals:
status: New → Confirmed
Changed in openstack-api-site:
status: New → Confirmed
Changed in openstack-manuals:
importance: Undecided → High
Changed in openstack-api-site:
importance: Undecided → High
Tom Fifield (fifieldt)
Changed in openstack-manuals:
importance: High → Medium
Changed in openstack-api-site:
importance: High → Medium
Changed in openstack-api-site:
assignee: nobody → Diane Fleming (diane-fleming)
Changed in openstack-manuals:
assignee: nobody → Diane Fleming (diane-fleming)
Revision history for this message
Joe T (joe-topjian-v) wrote :

While users can now boot volumes without specifying an image on the command line, Horizon is still requesting that an image be specified:

https://bugs.launchpad.net/horizon/+bug/1163566

Changed in openstack-api-site:
status: Confirmed → In Progress
Revision history for this message
Tom Fifield (fifieldt) wrote :

Hi,

This is marked as in progress - can we get a status update?

Revision history for this message
Diane Fleming (diane-fleming) wrote :

Tom, sorry for the delay - working on this now (8/21)

Revision history for this message
Diane Fleming (diane-fleming) wrote :

Hey Tom, I cannot boot an instance from a volume to save my life! Do you have any examples of the command flow using the nova and cinder clients? Or can you point me to someone who does? Thanks!

Revision history for this message
Jon Proulx (jproulx) wrote :

Hi Diane, I use boot from volume in my production environment (not extensively but but enough that I know how to make it work), Can reassign to me if you like.

also shouldn't this be mered with https://bugs.launchpad.net/openstack-api-site/+bug/1215081?

Revision history for this message
Tom Fifield (fifieldt) wrote :

This is now much easier in Havana.

Changed in openstack-manuals:
status: Confirmed → Fix Released
Changed in openstack-api-site:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.