Re: [openstack-dev] Fw: [Heat] Enhancement on addition to heat template with glance
On Tue, Jan 13, 2015 at 05:50:57PM +0530, Anusha Rayani wrote: Hello Steve, Thanks for your response. Yes,we do have an resource class defined in Heat to upload an image, but in this case we can only use the image from URL where as using --file option to glance image-create we can upload a disk image from local filesystem to glance. $ glance image-create --file FILE Local file that contains disk image to be uploaded during creation. Alternatively, images can be passed to the client via stdin. However GlanceImage class has only an option to upload the image from location/URL. Heat resources are a representation of the underlying API, you're referring to a convenience function which is part of python-glanceclient, which can read a local file and upload the binary image data to the glance API. I don't think having such an interface to the Heat resource makes sense, for the following reasons: 1. The heat service has no access to your local filesystem, so you'd have to upload the entire binary image to heat, then we'd have to upload it again to glance, this is a huge and unjustified overhead IMO. 2. There are several existing patterns which solve this, such as: - uploading the image via glance image-create then passing the ID in to the heat stack as a parameter - hosting the image in swift or a webserver and passing the URL to heat then consuming it via GlanceImage Can you explain why uploading the image to heat would be worthwhile, vs one of the other interfaces I just mentioned? Thanks, Steve __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Fw: [Heat] Enhancement on addition to heat template with glance
Hello All, I would like to implement glance image upload based on the path given from the HOT template. Currently I could see we can give already uploaded image id/name. Please let me know any further suggestions on this. Thanks, Anusha Rayani =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Fw: [Heat] Enhancement on addition to heat template with glance
On Tue, Jan 13, 2015 at 03:33:09PM +0530, Anusha Rayani wrote: Hello All, I would like to implement glance image upload based on the path given from the HOT template. You may need to provide more details - heat already accepts a location property? https://github.com/openstack/heat/blob/master/heat/engine/resources/glance_image.py#L97 If you have an image locally, you probably need to either make it available via a web server or upload it to swift, then pass the URL to heat. It doesn't really make sense to upload the entire image via heat from a local path, if that's what you mean? Steve __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Fw: [Heat] Enhancement on addition to heat template with glance
Hello Steve, Thanks for your response. Yes,we do have an resource class defined in Heat to upload an image, but in this case we can only use the image from URL where as using --file option to glance image-create we can upload a disk image from local filesystem to glance. $ glance image-create --file FILE Local file that contains disk image to be uploaded during creation. Alternatively, images can be passed to the client via stdin. However GlanceImage class has only an option to upload the image from location/URL. Thanks, Anusha Rayani Tata Consultancy Services Cell:- 9703299907 Mailto: anusha.ray...@tcs.com Website: http://www.tcs.com Experience certainty. IT Services Business Solutions Consulting -Steven Hardy sha...@redhat.com wrote: - To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org From: Steven Hardy sha...@redhat.com Date: 01/13/2015 05:04PM Subject: Re: [openstack-dev] Fw: [Heat] Enhancement on addition to heat template with glance On Tue, Jan 13, 2015 at 03:33:09PM +0530, Anusha Rayani wrote: Hello All, I would like to implement glance image upload based on the path given from the HOT template. You may need to provide more details - heat already accepts a location property? https://github.com/openstack/heat/blob/master/heat/engine/resources/glance_image.py#L97 If you have an image locally, you probably need to either make it available via a web server or upload it to swift, then pass the URL to heat. It doesn't really make sense to upload the entire image via heat from a local path, if that's what you mean? Steve __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
