Open Stack

On Tue, May 6, 2014 at 7:02 AM, Thierry Carrez <thierry at openstack.org>wrote:

> 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.
>
>
I believe that UX and DevEx are different areas of expertise and OpenStack
could benefit more from a separate focused DevEx program.

I'm not sure Dean's proposal is quite "DevEx" though, and I don't know if a
rename alone would take care of what I think it is.

- SDK maintenance and testing
- App-dev focus on docs
- Focus on improving automation tasks with unified CLI
- Processes and governance that could be separate from contrib devs
- Releases separate from the every six month timed release in order to
serve app devs better with quicker turnaround (similar to the CLIs now)
- Integrated client with the goal of eliminating the client-per-project mess

Dean, what do you think of these ideas? Is there enough in common with the
CLI user and app dev to consider this DevEx umbrella the program? Do you
plan to get rid of <project>-clients, and does it make sense to do so? Also
how do you plan to transition away from DevStack PTL role, have you found a
replacement?

Thanks for asking early, sure saves that Summit energy for me,
Anne



>  --
> Thierry Carrez (ttx)
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140506/94ec975d/attachment.html>