[openstack-dev] a "common" client library
Sean Dague
sean at dague.net
Mon Jan 20 12:18:46 UTC 2014
On 01/19/2014 11:50 PM, Jesse Noller wrote:
>
> On Jan 19, 2014, at 5:37 PM, Jamie Lennox <jamielennox at redhat.com
> <mailto:jamielennox at redhat.com>> wrote:
>
>> On Sat, 2014-01-18 at 09:13 -0500, Doug Hellmann wrote:
>>> I like the idea of a fresh start, but I don't think that's
>>> incompatible with the other work to clean up the existing clients.
>>> That cleanup work could help with creating the backwards compatibility
>>> layer, if a new library needs to include one, for example.
>>>
>>>
>>> As far as namespace packages and separate client libraries, I'm torn.
>>> It makes sense, and I originally assumed we would want to take that
>>> approach. The more I think about it, though, the more I like the
>>> approach Dean took with the CLI, creating a single repository with a
>>> team responsible for managing consistency in the UI.
>>>
>>>
>>> Doug
>>
>> This *is* the approach Dean took with the CLI. Have a package that
>> provides the CLI but then have the actual work handed off to the
>> individual clients (with quite a lot of glue).
>
> And I think many of us are making the argument (or trying to) that the
> “a lot of glue” approach is wrong and unsustainable for both a unified
> CLI long term *and especially* for application developers.
100% agree. At some point take a look at the tempest rest client, and
you can see how entirely crazy different the APIs are between services -
https://github.com/openstack/tempest/blob/master/tempest/common/rest_client.py#L506
(The Tempest client is in no way a paragon of virtues, but by writing
our own client we've really discovered how lumpy this API is).
So I'm highly supportive of taking all the clients into a single
separate program which would produce the official python SDK, as well as
a unified CLI for OpenStack. The server programs should just be
producing server stacks, that end with the API. I think that would
empower a set of people that were most concerned with operator and
developer UX to be able to look at OpenStack as a whole.
-Sean
--
Sean Dague
Samsung Research America
sean at dague.net / sean.dague at samsung.com
http://dague.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140120/dec4997f/attachment.pgp>
More information about the OpenStack-dev
mailing list