[openstack-dev] [nova] how to handle vendor-specific API microversions?

Dan Smith dms at danplanet.com
Fri Mar 27 18:44:02 UTC 2015

> To quote John from an earlier email in this thread:
> Its worth noting, we do have the "experimental" flag:
> "
> The first header specifies the version number of the API which was
> executed. Experimental is only returned if the operator has made a
> modification to the API behaviour that is non standard. This is only
> intended to be a transitional mechanism while some functionality used
> by cloud operators is upstreamed and it will be removed within a small
> number of releases.
> "
> So if you have an extension that gets accepted upstream you can use the
> experimental flag until you migrate to the upstream version of the
> extension.

Yes, but please note the last sentence in the quoted bit. This is to
help people clean their dirty laundry. Going forward, you shouldn't
expect to deliver features to your customers via this path.

> That is *not* what I would call interoperability, this is exactly what
> we do not want.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150327/d04abd72/attachment.pgp>

More information about the OpenStack-dev mailing list