Open Stack

Hi VK,
 
Besides the option laid out by Alex and Izy, currently you could take advantage of the bittorrent and image_cache functionality provided by nova. In this case you would need to download an image from glance once and then it could be pulled in from the image_cache for subsequent requests. Similar but not so much helpful for smaller deployments would be the bittorrent stuff.
 
thanks,
-Nikhil
 
-----Original Message-----
From: "VK Kumar" <vkkumar.live at gmail.com>
Sent: Tuesday, February 5, 2013 12:44am
To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] Glance to refer images on a image library rather than upload



Thanks Alex and Izy.
Your replies confirm that my first part of the assumption that when location is provide the image in not uploaded into glance.
Will check the patch links if the following is also eliminated by the patches.
"Then whenever an image is requested to be downloaded from glance, glance will first download the image data from the specified location and then pass it on."
What I was thinking was that when nova boot is done for an image with location on a http server, glance will not get the image, instead it will pass on the information such as image meta-data and http location to compute so that compute can get the image. This makes sense in cases where the compute nodes have direct access to the http server repository location (SAN) and transfer would be faster.
@Izy patch seems to address this, let me check.
Thanks again!
VK Kumar



On Tue, Feb 5, 2013 at 7:53 AM, [mailto:lzy.dev at gmail.com] lzy.dev at gmail.com <[mailto:lzy.dev at gmail.com] lzy.dev at gmail.com> wrote:
@VK
 If you give "location" option when you create glance image, glance
 will just register it  and set status to "active" but not upload.

 @Alex Meade
 I'm developing an iSCSI store driver for Glance, it also be used to
 avoid downloading/uploading operation for nova-compute and user. It
 can support multiple path accessing:

[https://review.openstack.org/#/c/20593/] https://review.openstack.org/#/c/20593/



 On Tue, Feb 5, 2013 at 6:43 AM, Alex Meade <[mailto:alex.meade at rackspace.com] alex.meade at rackspace.com> wrote:
 > Hi VK,
 >
 > Currently, the answer is sort of. There is work going into bypassing glance
 > when downloading from an image store so that it goes straight from the image
 > store to the compute node. There was a recent patch
 > ([https://review.openstack.org/#/c/19408/] https://review.openstack.org/#/c/19408/) for making this work when nova has
 > access to the same filesystem as glance and glance is using the filesystem
 > as the image store.
 >
 > Other than this I do not believe there is a way to avoid the extra download
 > to glance.
 >
 > Specifying the location just makes it so that an image can be added to
 > glance without uploading data to glance. Then whenever an image is requested
 > to be downloaded from glance, glance will first download the image data from
 > the specified location and then pass it on.
 >
 > Does this answer your question?
 >
 > -Alex Meade
 >
 >
 >
 > -----Original Message-----
 > From: "VK Kumar" <[mailto:vkkumar.live at gmail.com] vkkumar.live at gmail.com>
 > Sent: Thursday, January 31, 2013 6:34am
 > To: [mailto:openstack-dev at lists.openstack.org] openstack-dev at lists.openstack.org
 > Subject: [openstack-dev] Glance to refer images on a image library rather
 > than upload
 >
 > Hi All,
 > Is there a way to add an image from an existing image library (file share)
 > into glance so that the image is not copied to the glance server?
 > When ever nova boot is used, the image is then directly copied from the
 > image server to the compute node.
 > I am not sure if using the location option as http/s3/switf url still copies
 > the image or references it.
 > glance add location=http+s3://AWSACCOUNTID:<email address
 > hidden>/BUCKET/OBJECTNAME name="My S3 Image" disk_format=ami
 > container_format=ami is_public=True
 >
 > Thanks,
 > VK Kumar.
 >> _______________________________________________
 > OpenStack-dev mailing list
 > [mailto:OpenStack-dev at lists.openstack.org] OpenStack-dev at lists.openstack.org
 > [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 >

 _______________________________________________
 OpenStack-dev mailing list
[mailto:OpenStack-dev at lists.openstack.org] OpenStack-dev at lists.openstack.org
[http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130205/81788be1/attachment.html>