<div dir="ltr">Jay, I am afraid I didn't understand your point.<div><br></div><div>Could you rephrase/elaborate on "<span style="color:rgb(80,0,80);font-size:12.8000001907349px">What is the difference between just calling the Glance API to upload </span><span style="color:rgb(80,0,80);font-size:12.8000001907349px">an image, versus adding add()" please ?</span></div><div><span style="color:rgb(80,0,80);font-size:12.8000001907349px">Currently, you can't call the Glance API to upload an image if the default_store is the HTTP store. </span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 13, 2015 at 5:17 PM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 02/13/2015 10:01 AM, Jordan Pittier wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
>What is the difference between just calling the Glance API to upload<br>
an image, versus adding add() functionality to the HTTP image store?<br>
You mean using "glance image-create --location<br>
<a href="http://server1/myLinuxImage" target="_blank">http://server1/myLinuxImage</a> [..]" ? If so, I guess adding the add()<br>
functionality will save the user from having to find the right POST<br>
curl/wget command to properly upload his image.<br>
</blockquote>
<br></span>
How so?<br>
<br>
If the user is already using Glance, they can use either the Glance REST API or the glanceclient tools.<br>
<br>
-jay<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
On Fri, Feb 13, 2015 at 3:55 PM, Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a><br></span><div><div class="h5">
<mailto:<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>>> wrote:<br>
<br>
On 02/13/2015 09:47 AM, Jordan Pittier wrote:<br>
<br>
Hi list,<br>
<br>
I would like to add the 'add' capability to the HTTP glance store.<br>
<br>
Let's say I (as an operator or cloud admin) provide an HTTP<br>
server where<br>
(authenticated/trusted) users/clients can make the following<br>
HTTP request :<br>
<br>
POST <a href="http://server1/myLinuxImage" target="_blank">http://server1/myLinuxImage</a> HTTP/1.1<br>
Host: server1<br>
Content-Length: 256000000<br>
Content-Type: application/octet-stream<br>
<br>
mybinarydata[..]<br>
<br>
Then the HTTP server will store the binary data, somewhere (for<br>
instance<br>
locally), some how (for instance in a plain file), so that the<br>
data is<br>
later on accessible by a simple GET <a href="http://server1/myLinuxImage" target="_blank">http://server1/myLinuxImage</a><br>
<br>
In that case, this HTTP server could easily be a full fleshed<br>
Glance store.<br>
<br>
Questions :<br>
1) Has this been already discussed/proposed ? If so, could<br>
someone give<br>
me a pointer to this work ?<br>
2) Can I start working on this ? (the 2 main work items are :<br>
'add an<br></div></div>
add method to glance_store._drivers.http.___<u></u>_Store' and 'add a<br>
delete<br>
method to glance_store._drivers.http.___<u></u>_Store (HTTP DELETE method)'<span class=""><br>
<br>
<br>
What is the difference between just calling the Glance API to upload<br>
an image, versus adding add() functionality to the HTTP image store?<br>
<br>
Best,<br>
-jay<br>
<br></span>
______________________________<u></u>______________________________<u></u>__________________<span class=""><br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br></span>
OpenStack-dev-request@lists.__<a href="http://openstack.org?subject:__unsubscribe" target="_blank"><u></u>openstack.org?subject:__<u></u>unsubscribe</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">http://OpenStack-dev-request@<u></u>lists.openstack.org?subject:<u></u>unsubscribe</a>><br>
<a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack-dev</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a>><span class=""><br>
<br>
<br>
<br>
<br>
______________________________<u></u>______________________________<u></u>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<u></u>openstack.org?subject:<u></u>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<u></u>______________________________<u></u>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<u></u>openstack.org?subject:<u></u>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div>