Independent boot from volume
Bug #1159824 reported by
Vincent Hou
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Wishlist
|
Vincent Hou |
Bug Description
So far when we try to boot from a volume, we need to specify both block-device-
What we can do:
For image which has kernel and ramdisk, we can also copy them into two other volumes, set bootable to false for them and create the link with the bootable volume.
There are some attributes like disk format, container format, checksum, etc. We can also copy them into key-value pairs and save into volume_
Changed in cinder: | |
status: | New → Confirmed |
Changed in cinder: | |
importance: | Undecided → Wishlist |
Changed in cinder: | |
assignee: | nobody → Vincent Hou (houshengbo) |
Changed in nova: | |
assignee: | nobody → Vincent Hou (houshengbo) |
tags: | added: volumes |
no longer affects: | nova |
Changed in cinder: | |
milestone: | none → havana-2 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/34705
Review: https:/