On Wed, Jan 30, 2013 at 7:39 AM, Lei Zhang <zhang.lei....@gmail.com> wrote:
> I also have a question. What's the requirement for the image? I found > nothing int the doc. > > > On Tue, Jan 29, 2013 at 5:38 PM, Benoit ML <ben4...@gmail.com> wrote: > >> Hello, >> >> Thank you ! nice :) >> I'm really impatient to test cinder with NetApp device (soon it will be). >> >> In the documentation : >> >> http://docs.openstack.org/trunk/openstack-compute/admin/content/boot-from-volume.html >> The process is quite painful ... >> >> Regards, >> >> 2013/1/29 Avishay Traeger <avis...@il.ibm.com>: >> > Benoit, >> > >> > openstack-bounces+avishay=il.ibm....@lists.launchpad.net wrote on >> > 01/29/2013 10:56:33 AM: >> >> Hello, >> >> >> >> I have an openstack installation with 1 controller node, 1 network >> >> node and 2 compute node, configured with GRE tunnel for the network, >> >> and NFS backend for volumes. >> >> >> >> I'd like to create a bootable cinder volume from a glance image to >> >> have persistant disque for VMs, and tests live migration in this >> >> setup. >> >> >> >> But when I ask cinder to create a volume from a image, cinder report >> >> "not supported" ... And I have look into the code, it's seems to be >> >> supportend only with Ceph/Rados or Iscsi driver. >> >> >> >> So I have many questions : >> >> - Any plan to support it for other driver/setupe like : NetAppIscsi >> >> (or netappNFS Driver) ; NFS driver ? >> > >> > I have a patch submitted that will implement this for all iSCSI drivers: >> > https://review.openstack.org/#/c/19808/ >> > I don't know about NetApp's plans for other drivers. >> > >> >> - Any simple way to create a bootable cinder volume from the >> >> controller node shell ? (In the doc I must mount the volume on a VM >> >> ... create partition .. copy data and so on ; lots of manipulation..) >> > >> > I don't understand this question. >> > >> >> And of course, I have the same question for cinder snapshot. >> >> >> >> Thank you in advance ! >> >> >> >> Regards, >> >> >> >> -- >> >> -- >> >> Benoit >> > >> > Thanks, >> > Avishay >> > >> >> >> >> -- >> -- >> Benoit >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> > > > > -- > Lei Zhang > > Blog: http://jeffrey4l.github.com > twitter/weibo: @jeffrey4l > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > In Grizzly you can add an image-id to the create call. The create will do a conversion on the image to raw and write it to the volume directly, then you can boot it in Nova. The sequence is something like this: cinder create --image-id <image-id> --display-name mybootable-vol 10 nova boot --image <image-id> --flavor <flavor-id> --block-device-mapping vda=<uuid-of-volume-you-just-created> --key-name <my-key> my-test-instance The implementatio in Folsom isn't quite as far along.
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp