<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 6, 2014 at 6:54 AM, Dean Troyer <span dir="ltr"><<a href="mailto:dtroyer@gmail.com" target="_blank">dtroyer@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="">On Tue, May 6, 2014 at 7:02 AM, Thierry Carrez <span dir="ltr"><<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>></span> wrote:<br>
</div><div class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Would you take over the Python client libraries as well ? On one hand<br></div>
they need /some/ domain expertise, but on the other I see no reason to<br>
special-case Python against other SDKs, and that may give the libraries<br>
a bit more attention and convergence (they currently are the ugly<br>
stepchild in some programs, and vary a lot).<br></blockquote><div><br></div></div><div>The future of the existing client libs has not been settled, my working assumption is that they would remain with their home programs as they are now. From the start OpenStackClient was meant to be a clean-slate for the CLI and the Python SDK is taking the same basic approach.</div>
</div></div></div></blockquote><div><br></div><div><br></div><div>Very excited for the OpenStackClient, it is already way nicer then the existing clients.</div><div><br></div><div><br></div><div>Just working this out in my head. So the work flow would be:</div>
<div><br></div><div>1. At first ClientTools consist of just the OpenStackClient</div><div>2. When the pythonSDK is ready to move off of stackforge, it will live in ClientTools</div><div>3. Specific python-*clients will be rewritten (from scratch?) to use the PythonSDK. But this time they won't have a built in CLI. These libraries will live along side the respective servers (so nova's python-novaclient will live in Compute)? All while moving OpenStackClient to the new libraries</div>
<div><br></div><div><br></div><div>Is that what you are proposing?</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">
<div class="gmail_quote"><div class="">
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In the case you'd absorb the Python client libraries, it might make<br>
sense to ship the keystone middleware in a separate package that would<br>
still live in the Identity program.</blockquote><div><br></div></div><div>This needs to happen anyway, it's time for my semi-annual request to dolphm...</div><div class=""><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>I think we need people caring for the end user and their experience of<br></div>
interacting with an OpenStack-backed cloud. I understand that CLI/SDK<br>
specialists and GUI-oriented specialists are different crowds, but they<br>
share the same objective and would benefit IMHO from being in the same<br>
program. There could be two subteams to care for specialists in both<br>
areas (or even 3 if you separate the CLI and SDK folks). Overall from<br>
the TC perspective it would make a much stronger proposal if you somehow<br>
could present a united (and without overlap) proposal.</blockquote><div><br></div></div><div>To be honest, until the most recent ML thread I hadn't thought about the UX team or even if they were active. We have three basic categories of projects delivering code: web UI (Horizon), CLI (OpenStackClient) and SDK (at least three active language-based teams). They all should consume the output from a UX R&D effort, I guess I am open on the program structure to make that work. Horizon is already a part of a program, OSC needs to be and the SDKs will also need to be in the near future.</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div><br></div><div>dt</div><div><br></div></font></span></div><span class="HOEnZb"><font color="#888888">-- <br><br>Dean Troyer<br><a href="mailto:dtroyer@gmail.com" target="_blank">dtroyer@gmail.com</a><br>
</font></span></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>