[openstack-dev] a "common" client library
jamielennox at redhat.com
Tue Jan 21 18:55:35 UTC 2014
don't do this here - the thread is way too deep already.
If we get into discussing individual points let's do one question per thread and prefix the emails with [client] or something to tie it all together
----- Original Message -----
> From: "Alexei Kornienko" <alexei.kornienko at gmail.com>
> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> Sent: Wednesday, 22 January, 2014 4:35:39 AM
> Subject: Re: [openstack-dev] a "common" client library
> I would like to propose to use this thread to gather and discuss software
> requirements that our clients should meet.
> Later we'll summarize all the requirements and use them during our work of
> improving the clients.
> By reaching listed requirements we'll be able to evaluate the success of our
> To start this discussion:
> * API versioning should be encapsulated inside of the client.
> From the end user perspective using the code should look something like:
> import openstack.nova
> nova = openstack.nova.create_client(...params TBD...)
> Reasoning for this requirement:
> If user would have to specify version explicitly his code will only work with
> specific version of client/api or user would have to write several code
> paths for different api versions.
> We will have an interface (abstact class) that would contain all the methods
> available in latest API.
> Different versions of the API would implement this methods. In case method
> cannot be implemented with existing API it should raise
> "UnsupportedOperation" exception.
> user - developer who uses the client/openstack API
> Please share your thoughts about this requirement/other requirements.
> Looking forward for your replies,
> Alexei Kornienko
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev