Open Stack

Dean Troyer wrote:
> I want to open the discussion of an OpenStack Client Tools program
> proposal to a wider audience.  It would initially consist of
> OpenStackClient and eventually add the existing SDK projects as they are
> ready to join. The initial wiki page is at
> https://wiki.openstack.org/wiki/ClientTools.  I do want to have the
> proposal made before the summit, but not necessarily the TC consideration.

Would you take over the Python client libraries as well ? On one hand
they need /some/ domain expertise, but on the other I see no reason to
special-case Python against other SDKs, and that may give the libraries
a bit more attention and convergence (they currently are the ugly
stepchild in some programs, and vary a lot).

In the case you'd absorb the Python client libraries, it might make
sense to ship the keystone middleware in a separate package that would
still live in the Identity program.

> There has recently been some discussion (specifically around summit
> sessions) regarding the overlap of client code and the user experience
> team.  This is one of the things I want to get some feedback on before
> making a formal proposal.  

I think we need people caring for the end user and their experience of
interacting with an OpenStack-backed cloud. I understand that CLI/SDK
specialists and GUI-oriented specialists are different crowds, but they
share the same objective and would benefit IMHO from being in the same
program. There could be two subteams to care for specialists in both
areas (or even 3 if you separate the CLI and SDK folks). Overall from
the TC perspective it would make a much stronger proposal if you somehow
could present a united (and without overlap) proposal.

-- 
Thierry Carrez (ttx)