[Openstack-docs] 2013.2 tag seems broken ?

Waines, Greg Greg.Waines at windriver.com
Wed Sep 3 15:20:36 UTC 2014


Thanks Anne.

But the individual APIs, say Compute API, are not up-versioned every OpenStack Release.

However the individual APIs, say Compute API V2, (I believe) are extended every OpenStack Release … possibly new requests, possibly new parameters for requests, possibly new attributes in responses.

So there are going to be IceHouse(say)-specific changes in (say) Compute API V2 … correct ?

But it sounds like there is no tag or commit that represents an ‘up-to-Havana only’ version of Compute API V2 … correct ?


Greg.





From: annegentle at justwriteclick.com [mailto:annegentle at justwriteclick.com] On Behalf Of Anne Gentle
Sent: Tuesday, September 02, 2014 11:36 PM
To: Waines, Greg
Cc: openstack-docs at lists.openstack.org
Subject: Re: [Openstack-docs] 2013.2 tag seems broken ?



< SNIP >



We have had this discussion in the past, read it at http://lists.openstack.org/pipermail/openstack-docs/2014-April/004337.html. The basic problem with tagging API docs is that there's not a map from say, havana, to API versions. The deployers choices for that particular release would look something like this:

Block Storage API v1 or v2
Compute API v2
Identity API v2.0 or v3
Image Service v1, v1.1, or v2
(not Database service, they weren't integrated then)
Networking API v2.0
Object Storage v1
Orchestration v1
Telemetry v2

So I think there are  3*2*3*4*2*2*2*2 = 1152 possibilities of combining API versions a cloud provider offers for Havana, where you can choose not to deploy an API endpoint at all. We can't dictate to the provider "you must run these API versions when running havana" so I've avoided tagging the docs for overhead and maintenance and explanatory reasons. :)

Hopefully these explanations makes sense to you, sounds like you've guessed right all along. I certainly want our docs to be re-used and they're licensed completely for re-use, but I'm pretty sure I can't accurately say which API calls go with a particular release. I definitely want to hear ideas though!
Thanks for asking -
Anne




thanks in advance,
Greg.


_______________________________________________
Openstack-docs mailing list
Openstack-docs at lists.openstack.org<mailto:Openstack-docs at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140903/dea2681e/attachment.html>


More information about the Openstack-docs mailing list