<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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.<div><br></div><div>nova boot --block-device-mapping vda=<snap-id>:snap:<size>:True</div><div><br></div><div><br></div><div>You cannot currently pass an image id and get a volume backed instance. It requires two steps</div><div><br></div><div>cinder create --image-id=<image-id></div><div>nova boot --block-device-mapping vda=<vol-id></div><div><br></div><div>Vish</div><div><br></div><div><br><div><br><div><div>On Mar 11, 2013, at 6:24 AM, Logan McNaughton <<a href="mailto:logan@bacoosta.com">logan@bacoosta.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">Will Grizzly support specifying an empty Cinder volume as an instance's root device?</p><p dir="ltr">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?</p>
_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></div></div></body></html>