Open Stack

I agree that, while it's a pain, supporting old versions of the API is the best way to grow adoption. For many shops, simply supporting OpenStack API is a large engineering effort ... having to revisit it every version update might bust the camels back. Easy to see why Amazon goes back so far.

There was a discussion in the old DirectAPI thread about how versioning might be implemented.

-S

________________________________
From: f Brian Waldon [brian.waldon at rackspace.com]
Sent: Thursday, March 03, 2011 5:33 PM

So I also think it is great to support multiple apis (and major versions). Right now I am more concerned with how we should accomplish this in the code. Does anyone have any objection to creating a different directory under nova/api per api and major version with a common set of code shared between them?





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 abuse at rackspace.com, and delete the original message.
Your cooperation is appreciated.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110304/853075c4/attachment.html>