[openstack-dev] [marconi] Reconsidering the unified API model

Devananda van der Veen devananda.vdv at gmail.com
Wed Jun 11 23:26:09 UTC 2014

On Tue, Jun 10, 2014 at 1:23 AM, Flavio Percoco <flavio at redhat.com> wrote:
>> Against:
>>  • Makes it hard for users to create applications that work across
>> multiple
>>    clouds, since critical functionality may or may not be available in a
>> given
>>    deployment. (counter: how many users need cross-cloud compatibility?
>> Can
>>    they degrade gracefully?)

The OpenStack Infra team does.

> This is definitely unfortunate but I believe it's a fair trade-off. I
> believe the same happens in other services that have support for
> different drivers.

I disagree strongly on this point.

Interoperability is one of the cornerstones of OpenStack. We've had
panels about it at summits. Designing an API which is not
interoperable is not "a fair tradeoff" for performance - it's
destructive to the health of the project. Where other projects have
already done that, it's unfortunate, but let's not plan to make it

A lack of interoperability not only prevents users from migrating
between clouds or running against multiple clouds concurrently, it
hurts application developers who want to build on top of OpenStack
because their applications become tied to specific *implementations*
of OpenStack.

Just my 2c,

More information about the OpenStack-dev mailing list