Just for reference, our current Rackspace commitment is to support current API and one version back. Anything older will be marked as depricated and we do not commit that it will work. By the way, this is merely a goal at this point since there is only one version. However, we are trying to live up to that goal as we transition to Nova. So, we plan to support Cloud Servers 1.0 and the OpenStack API on both our current codebase as well as our initial Nova implementation.
Again, that is a Rackspace goal and something we should have an option to provide as a deployer of Nova - not something that is appropriate for all implementations. Troy On Mar 3, 2011, at 10:22 AM, Trey Morris wrote: maybe I'm missing something, but if you don't want to run a recent API why should you expect to be able to run it with a recent release of nova? I think trying to support older and new versions at the same time would clip our wings, or at the very least add some nastiness to the code. If someone wants to run old API, they should have to run old openstack with it. If they want new openstack, they should run the new API. I do apologize if I am in fact missing something. -tr3buchet On Thu, Mar 3, 2011 at 9:05 AM, Thierry Carrez <[email protected]<mailto:[email protected]>> wrote: Brian Waldon wrote: > Currently, the Openstack API includes a Versions WSGI application. The > intended purpose is to detail all versions of the API that are reachable > by a client. Currently, it only supports "v1.0." As we move towards the > Cactus release, we need to add support for the new "v1.1" specification. > The intention of the Versions app seems to be to deploy multiple > versions of the OS API within the same codebase. Since these two > versions have significant differences, having to support each in the > same code seems unnatural. > > With the existing approach, versioning could be accomplished multiple > ways: version-specific "if" statements, version-specific class > hierarchies, etc. I feel this is inelegant and could be accomplished a > much cleaner way. I propose we move the responsibilities of the Versions > app out of the nova codebase and into the hands of the operator of the > api endpoints. With this approach, the code would not unnecessarily > increase in complexity as more versions of the api are released. The > major drawback of this strategy is that each release of Openstack > Compute could support a single OS API version. For the OpenStack API to grow a significant partner ecosystem, it seems important to me to support at least the recent versions of the API in new releases of Openstack Compute... -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected]<mailto:[email protected]> Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at [email protected]<mailto:[email protected]>, and delete the original message. Your cooperation is appreciated. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected]<mailto:[email protected]> Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
