openstack team mailing list archive
Mailing list archive
Re: Cinder volume as root in Grizzly?
Oh great! I didn't realize you can create a cinder volume from an image. So
can I pass cinder a QCOW2 image, then boot from that volume?
On Mar 11, 2013 7:16 PM, "Vishvananda Ishaya" <vishvananda@xxxxxxxxx> wrote:
> Not exactly, although you can do something similar in both folsom and
> grizzly. If you have a volume snapshot you can pass it in the
> block_device_mapping when you boot an instance and nova will automatically
> create a volume from the snapshot and boot from it. If you also set
> delete_on_terminate true you have roughly the same experience as an EBS
> backed instance.
> nova boot --block-device-mapping vda=<snap-id>:snap:<size>:True
> You cannot currently pass an image id and get a volume backed instance. It
> requires two steps
> cinder create --image-id=<image-id>
> nova boot --block-device-mapping vda=<vol-id>
> On Mar 11, 2013, at 6:24 AM, Logan McNaughton <logan@xxxxxxxxxxxx> wrote:
> Will Grizzly support specifying an empty Cinder volume as an instance's
> root device?
> Right now you need to setup the volume before hand and you can "boot from
> volume". But will there be support similar to AWS EBS-backed instances in
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp