Improve the booting from volume interface
The aim of this blueprint is to improve the interface for booting from volumes. Some discussion around this occured on the Grizzly summit, and was sumarized in the following etherpad https:/
This blueprint will cover the following functionality:
* Make Nova able to boot without image
* Make Cinder relate image metadata when the volume is created with an --image_id (done already, see https:/
* Make this data available through the Cinder API
* Make nova consider this data when booting from volume using bdms
* Add the --volume option to nova boot
* Extend nova API to return more details about the volumes attached and also be more explicit when an instance is booted from a volume
* Add the --kernel and --ramdisk options to nova boot
Note that bits of this blueprint require changes to Cinder as well.
For more details see the related discussion on the dev ML http://
Further steps outlined in the etherpad will be done in separate blueprints.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Medium
- Drafter:
- Nikola Đipanov
- Direction:
- Approved
- Assignee:
- Nikola Đipanov
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Good progress
- Milestone target:
- None
- Started by
- Vish Ishaya
- Completed by
- Russell Bryant
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Boot from volume without image supplied
Gerrit topic: https:/
Addressed by: https:/
Extract image metadata from Cinder
Addressed by: https:/
New block device API extension - WIP
Addressed by: https:/
Add conversion between local and volume storage on boot
Gerrit topic: https:/
Addressed by: https:/
Libvirt driver create images even without meta
Addressed by: https:/
Prevent rescue for volume-backed instances
Gerrit topic: https:/
Addressed by: https:/
Fix resize when instance has no image
Addressed by: https:/
Fix resize when instance has no image
Nikola indicated that almost all of this is covered by https:/