Open Stack

On Tue, Sep 23, 2014 at 12:15 PM, Kevin L. Mitchell <
kevin.mitchell at rackspace.com> wrote:

> One of the things that's been bothering me about OpenStack for a while
> now is the fact that we have all these different APIs on different
> endpoints.  What I've been wondering about is if we should create a
> unified ReST API service to replace the service from all of the
> individual projects.  Then, users can just hit that one service to
> handle all their different interactions.
>

I've done this occasionally using Apache as the endpoint and
rewriting/forwarding URLs to the native servers.  As we add APIs to using
mod_wsgi this only becomes easier.  It's not doable directly in DevStack
yet, although maybe we should convert the tls-proxy service from using stud
to Apache, then a single endpoint could be an option on top of that.

Also this would tremendously simplify using JSON Home from the client
standpoint as there should then be only one doc to cache and parse. And if
not that, at least getting all of the API versions in one round trip.

dt

-- 

Dean Troyer
dtroyer at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140923/f695c2fb/attachment.html>