Open Stack

On 13/02/15 16:01 +0100, Jordan Pittier wrote:
>>What is the difference between just calling the Glance API to upload an image,
>versus adding add() functionality to the HTTP image store?
>You mean using "glance image-create --location http://server1/myLinuxImage [..]
>" ? If so, I guess adding the add() functionality will save the user from
>having to find the right POST curl/wget command to properly upload his image.

I believe it's more complex than this. Having an `add` method for the
HTTP store implies:

- Figuring out the http method the server expects (POST/PUT)
- Adding support for at least few HTTP auth methods
- Having a sufixed URL where we're sure glance will have proper
  permissions to upload data.
- Handling HTTP responses from the server w.r.t the status of the data
  upload. For example: What happens if the remote http server runs out
  of space? What's the response status going to be like? How can we
  make glance agnostic to these discrepancies across HTTP servers so
  that it's consistent in its responses to glance users?
- How can we handle quota?

I'm not fully opposed, although it sounds like not worth it code-wise,
maintenance-wise and performance-wise. The user will have to run just
1 command but at the cost of all of the above.

Do the points listed above make sense to you?

Cheers,
Flavio

>
>On Fri, Feb 13, 2015 at 3:55 PM, Jay Pipes <jaypipes at gmail.com> wrote:
>
>    On 02/13/2015 09:47 AM, Jordan Pittier wrote:
>   
>        Hi list,
>
>        I would like to add the 'add' capability to the HTTP glance store.
>
>        Let's say I (as an operator or cloud admin) provide an HTTP server
>        where
>        (authenticated/trusted) users/clients can make the following HTTP
>        request :
>
>        POST http://server1/myLinuxImage HTTP/1.1
>        Host: server1
>        Content-Length: 256000000
>        Content-Type: application/octet-stream
>
>        mybinarydata[..]
>
>        Then the HTTP server will store the binary data, somewhere (for
>        instance
>        locally), some how (for instance in a plain file), so that the data is
>        later on accessible by a simple GET http://server1/myLinuxImage
>
>        In that case, this HTTP server could easily be a full fleshed Glance
>        store.
>
>        Questions :
>        1) Has this been already discussed/proposed ? If so, could someone give
>        me a pointer to this work ?
>        2) Can I start working on this ? (the 2 main work items are : 'add an
>        add method to glance_store._drivers.http.__Store' and 'add a delete
>        method to glance_store._drivers.http.__Store (HTTP DELETE method)'
>
>
>    What is the difference between just calling the Glance API to upload an
>    image, versus adding add() functionality to the HTTP image store?
>
>    Best,
>    -jay
>
>    __________________________________________________________________________
>    OpenStack Development Mailing List (not for usage questions)
>    Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

>__________________________________________________________________________
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-- 
@flaper87
Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150213/6cf3cdd4/attachment.pgp>