Open Stack

On 16 Jan 2014, at 13:06, Jesse Noller <jesse.noller at RACKSPACE.COM> wrote:

>> Since it’s pretty easy to get lost among all the opinions I’d like to clarify/ask a couple of things:
>> 
>> Keeping all the clients physically separate/combining them in to a single library. Two things here:
>> In case of combining them, what exact project are we considering? If this list is limited to core projects like nova and keystone what policy could we have for other projects to join this list? (Incubation, graduation, something else?)
>> 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.
> 
> Keeping them separate is awesome for *us* but really, really, really sucks for users trying to use the system. 

You may be right but not sure that adding another line into requirements.txt is a huge loss of usability.

Renat Akhmerov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140116/7555d8e3/attachment.html>