Re: [Openstack] Volume booting and HVM

2012-10-26 Thread John Garbutt
Just a heads up. There are a few bugs in that area that have been fixed in 
Grizzly, and are not yet backported to Folsom stable. Things like deleting the 
root volume after terminating a boot from volume instance.

 -Original Message-
 From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net
 [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On
 Behalf Of Egoitz Aurrekoetxea Aurre
 Sent: Monday, October 22, 2012 10:35 AM
 To: Vishvananda Ishaya
 Cc: openstack@lists.launchpad.net
 Subject: Re: [Openstack] Volume booting and HVM
 
 Thank you very much Vishvananda
 
 Best regards,
 
 El 22/10/2012, a las 18:53, Vishvananda Ishaya vishvana...@gmail.com
 escribió:
 
  The ability to clone an image to a volume was only recently added to cinder,
 so there is no automatic clone on boot in horizon yet. You will have to 
 manually
 create a volume from an image and then boot from it.
 
  For older versions of openstack, the instructions are here:
 
  http://docs.openstack.org/trunk/openstack-compute/admin/content/boot-f
  rom-volume.html
 
  In folsom you can skip the mount and copy step and just create a volume
 directly from an image:
 
  IMAGE_ID=f4addd24-4e8a-46bb-b15d-fae2591f1a35
  cinder create --image-id $IMAGE_ID --display-name my-volume 10
  VOLUME_ID=uuid from above command $ nova boot --image $IMAGE_ID
  --flavor 2 --key_name mykey --block_device_mapping vda=$VOLUME_ID
  boot-from-vol-test
 
  Vish
 
  On Oct 22, 2012, at 4:02 AM, Egoitz Aurrekoetxea Aurre
 ego...@ramattack.net wrote:
 
  Good morning,
 
  I have noticed I was confused about the volume concept and booting from
 volume. I was thinking, when I clicked in Horizon boot from volume AND
 selected an HVM image (located at glance) that image was being dumped to the
 volume, and following times that volume would be able to boot by it's own. But
 have seen when I terminate de instance I'm not getting my purpose and I'm not
 able to later boot from that volume with preserved changes (configs and so)..
 How could I manage for getting my goal??. We're used to use the vms with
 XenCenter and then I was able to stop a vm and later to boot it. I'm looking 
 for a
 similar manner with Openstack. I though I was get my goal by selecting booting
 from volume AND launching and image..
 
  Any help would be very appreciated,
  Best regards
  ___
  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

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Volume booting and HVM

2012-10-22 Thread Vishvananda Ishaya
The ability to clone an image to a volume was only recently added to cinder, so 
there is no automatic clone on boot in horizon yet. You will have to manually 
create a volume from an image and then boot from it.

For older versions of openstack, the instructions are here:

http://docs.openstack.org/trunk/openstack-compute/admin/content/boot-from-volume.html

In folsom you can skip the mount and copy step and just create a volume 
directly from an image:

IMAGE_ID=f4addd24-4e8a-46bb-b15d-fae2591f1a35
cinder create --image-id $IMAGE_ID --display-name my-volume 10
VOLUME_ID=uuid from above command 
$ nova boot --image $IMAGE_ID --flavor 2 --key_name mykey 
--block_device_mapping vda=$VOLUME_ID boot-from-vol-test

Vish

On Oct 22, 2012, at 4:02 AM, Egoitz Aurrekoetxea Aurre ego...@ramattack.net 
wrote:

 Good morning,
 
 I have noticed I was confused about the volume concept and booting from 
 volume. I was thinking, when I clicked in Horizon boot from volume AND 
 selected an HVM image (located at glance) that image was being dumped to the 
 volume, and following times that volume would be able to boot by it's own. 
 But have seen when I terminate de instance I'm not getting my purpose and I'm 
 not able to later boot from that volume with preserved changes (configs and 
 so)…. How could I manage for getting my goal??. We're used to use the vms 
 with XenCenter and then I was able to stop a vm and later to boot it. I'm 
 looking for a similar manner with Openstack. I though I was get my goal by 
 selecting booting from volume AND launching and image….
 
 Any help would be very appreciated,
 Best regards
 ___
 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