openstack-poc team mailing list archive

[Jay Pipes <jaypipes@xxxxxxxxx>]

On Wed, Sep 7, 2011 at 12:16 PM, Paul Voccio <openstack@xxxxxxxxxxxxxxx> wrote:
> Wouldn't this mean that versions of the API for projects would then have a
> version that is reflective of the release and not a spec number?  Version
> 1.1 doesn't mean anything in Diablo if it doesn't adhere to the 1.1 guide?
>  The api would be versioned for diablo and we would start a new version for
> essex?

Perhaps I wasn't specific enough... sorry about that.

I mean that we guarantee that whatever latest version of an API a
project supports for a release, clients that communicate on that API
can be assured that the servers built in the next release series will
at a minimum support that API version, along with any new API versions
that might have been added in the new release series.

For instance, if Compute API 1.1 is what is supported in the Diablo
release series for Nova, then we make the guarantee that all the
server code in the Essex release series supports the 1.1 API, even if
during the Essex release series, a new Compute 2.0, 2.1, and 2.2 API
comes out.

Does that make more sense?

Cheers,
-jay