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> Vish On Mar 11, 2013, at 6:24 AM, Logan McNaughton <lo...@bacoosta.com> 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 > Grizzly? > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
