openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #24342
OpenStack API versions and release content
-
To:
OpenStack Maillist <openstack@xxxxxxxxxxxxxxxxxxx>
-
From:
Farhan Patwa <Farhan.Patwa@xxxxxxxx>
-
Date:
Tue, 11 Jun 2013 21:46:27 +0000
-
Accept-language:
en-US
-
Thread-index:
AQHOZu0ga2OldpEPBkeb1NiIVHTdfw==
-
Thread-topic:
OpenStack API versions and release content
-
User-agent:
Microsoft-MacOutlook/14.3.2.130206
Hi all,
I am just trying to understand the motivation behind creations API versions and how that ties in to a release content.
As per listed documentation (http://docs.openstack.org/api/openstack-compute/2/content/Versions-d1e1193.html)
"New Features and functionality that break API-compatibility necessitate a new version. When new API version are released older versions are marked as deprecated."
My questions are:
1.) Is the assumption here that operators may update the release but opt to stay with an older API version to get bug fixes etc.?
2.) Do new versions have to be deployed with a new release? Keystone has V3 version, but I don't see it being available for use in devstack or Grizzly release (based on my assumption that the command 'keystone discover' will display supported API versions)
3.) Do versions have their own release schedule (so Keystone V3 is part of Grizzly code but the implementation is not yet complete or supported??)
I would really appreciate if someone can shed light on this.
Thanks for your time,
-Farhan Patwa.
Follow ups