[openstack-dev] a "common" client library

Renat Akhmerov rakhmerov at mirantis.com
Thu Jan 16 22:46:08 UTC 2014

On 16 Jan 2014, at 12:36, Dean Troyer <dtroyer at gmail.com> wrote:

> I've already written a POC for solum and some other things to demonstrate how to add additional projects simply by installing the python-*client package.  https://github.com/dtroyer/python-oscplugin is a trivial example.

Thanks, this link is helpful.
> In terms of granularity and easiness of development I’m for keeping them separate but have them use the same boilerplate code, basically we need a OpenStack Rest Client Framework which is flexible enough to address all the needs in an abstract domain agnostic manner. I would assume that combining them would be an additional organizational burden that every stakeholder would have to deal with.
> If it is not a library that is actually shared you will get back to the current situation over time. 

How is that different from any other oslo stuff?
> Has anyone ever considered an idea of generating a fully functional REST client automatically based on an API specification (WADL could be used for that)? Not sure how convenient it would be, it really depends on a particular implementation, but as an idea it could be at least thought of. Sounds a little bit crazy though, I recognize it :).
> When you have stable and accurate documents of this sort, let's talk.  You may have noticed that few (any?) of the recent major API revs are documented in this manner…

There’s still something to work on for us.. As far as what I’ve written, just a crazy idea that came to my mind. After all, everyone’s phone has lots of things that were considered crazy years ago.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140116/658ef363/attachment.html>

More information about the OpenStack-dev mailing list