-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/06/2010 02:17 AM, David Lutterkort wrote:
> Hi,
> 
> I would like to get quickly to a point where we can declare the current
> Deltacloud API stable, and be reasonably confident that we can evolve
> the API in a way that will maintain backwards compatibility.
> 
> Unfortunately, there are a few goofups in the current Deltacloud API
> that we need to fix before we can declare the API stable, since fixing
> them will break API compatibility. In no specific order, the issues I am
> aware of are
> 
> 
>       * returning full objects when listing a collection: this is a
>         pretty serious issue. For example, for Terremark, returning a
>         list of full image details requires first calling to Terremark
>         to get a list of images without details, then retrieving the
>         detail of each image. That can be a long and slow process,
>         leading to timeout issues for clients. The best way to fix this
>         is to return full image details on GET /api/images from drivers
>         where that is cheap, and only an abbreviated list of images,
>         i.e. with only a URL and id for the image, from drivers like
>         Terremark. We'll probably have to deal with other lists in a
>         similar manner.

ACK.

>       * returning the representation of a new instance from a
>         POST /api/instances: again, in some drivers, like Terremark,
>         that requires making two calls to the backend cloud, which is
>         too fragile for this operation. Instead, the result from
>         POST /api/instances should contain the URL of the new instance
>         in a Location: header, and optionally the instance
>         representation for drivers where that is cheap to do.

Sounds good for me. ACK.

>       * the list of actions for an instance is misleading: we report
>         <link rel='ACTION' href='URL'/> - that is not enough, since it
>         gives no indication what HTTP method should be used to perform
>         the action. It's generally POST, but for destroying an instance,
>         you are supposed to do a DELETE on the instance URL. We
>         therefore need to include a method in the <link/> tag

ACK. There is a patch:

https://fedorahosted.org/pipermail/deltacloud-devel/2010-May/001118.html

- - Michal

- -- 
- --------------------------------------------------------
Michal Fojtik, [email protected], +420 532 294 4307
Ruby / Ruby On Rails Developer
Deltacloud API: http://deltacloud.org
- --------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEbBAEBAgAGBQJL4se8AAoJEEwRP1Pf2/iqiHkH+LLGvb1kBDI2AiMX6L6GdBYq
ywoSzgCLeh2xiYhcf6UbjdmPlfX4YS6IvueSrIN451iHoFt2iiSjBh9xMW3zDlXo
udK/sV1wcIeB+AYgrcuwwYzqsqdWS2iVP/Wfy46YaUZZhpqywfT6kWxT8p8rPiT7
3JBjKmAx+pmiqIjHX0xTSDQgZLZjt7PSIUdgLo/bv+ZsT4iIiKbSUKeBg1LlEIfK
D1C9U2HoHLRcFxVwa0ErZN4xeU6BPLnoXJcrDa8IOu7z+scdA7UTLM0Cp7YPQAeo
uxFXOyBv1nWks0aSyzcK4dZa5Mq7/i0ZOYWSGBmeDUyVEUbAk48JOdD0/ReYhw==
=ryWX
-----END PGP SIGNATURE-----
_______________________________________________
deltacloud-devel mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/deltacloud-devel

Reply via email to