Hi,
On a different list we're talking about improving/new features on the
client side of OpenStack APIs and this one came up (please see below).
Although API-ref is doing a great job, I believe the question is: Can we
achieve an equivalent of aws-sdk? For instance could we have each
project's API to publish its own schema?
I suppose this would fit under the API-WG umbrella. Would that be
correct? Could someone in the group provide feedback please?
Trying to find current work around this, I can see the API capabilities
discovery [1] & [2] is great but, it seems to me that part of the
challenge for the WG is a lack of schema too. Wouldn't it make sense to
have a standardized way for all services APIs (at least on the public
side) to publish their schema (including version/microversions details)
before going any further?
Thanks,
Gilles
[1] https://etherpad.openstack.org/p/ptg-architecture-workgroup
[2] https://review.openstack.org/#/c/386555/
-------- Forwarded Message --------
Subject: Re: Misty 0.2.0
Date: Fri, 10 Mar 2017 09:19:44 +0100
From: Ladislav Smola <lsm...@redhat.com>
To: Gilles Dubreuil <gil...@redhat.com>
CC: Marek Aufart <mauf...@redhat.com>, Tzu-Mainn Chen
<tzuma...@redhat.com>, Petr Blaho <pbl...@redhat.com>
Hola,
would be nice to see this moving in the direction of aws-sdk, where it
just holds API schema (that you would get from OpenStack itself) and
the whole client is generated from it. But I assume this needs the
API-ref to be in a good shape.
Ladislav
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
