We had a discussion with API WG today about what it means to be an
EXPERIMENTAL API and here's the takeway from that discussion.
- API's can be experimental, but mark it clearly in the docs as such
- Experimental means a breaking change may be introduced
- Use /x1/ instead of /v1/ in the
Thanks Lakshmi, that's useful.
So, we want to release Artifacts API in Kilo as experimental. We do need
some early adopters to begin working with it (the initial interest was from
Heat and Murano projects, and the OVA/OVF initiative for Images as well) in
the next cycle and provide some feedback
On 03/12/2015 01:19 PM, Sampath, Lakshmi wrote:
We had a discussion with API WG today about what it means to be an EXPERIMENTAL
API and here's the takeway from that discussion.
All experimental means with regards to an API is we reserve the right
to completely abandon this or change it in
On Thu, Mar 12, 2015 at 1:42 PM, Brian Rosmaita
brian.rosma...@rackspace.com wrote:
I don't know how elaborate we want to get here, but Everett Toews had an
interesting suggestion in the openstack-api channel. It would go something
like this:
(1) User gets /x1/search endpoint from service
This would require some changes to how python-glanceclient parses
versions. Even if the keystone catalog has a version string in it (which
typically is not the case for glance) the version parsing in common/utils
only recognizes version strings beginning with 'v'.
Would it be sensible to add
I don't know how elaborate we want to get here, but Everett Toews had an
interesting suggestion in the openstack-api channel. It would go something
like this:
(1) User gets /x1/search endpoint from service catalog
(2) User does some request against /x1/search
(3) User receives 400 with an error
On Mar 12, 2015, at 1:42 PM, Brian Rosmaita brian.rosma...@rackspace.com
wrote:
I don't know how elaborate we want to get here, but Everett Toews had an
interesting suggestion in the openstack-api channel. It would go something
like this:
(1) User gets /x1/search endpoint from service
