<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 7, 2014 at 8:32 AM, Brian Curtin <span dir="ltr"><<a href="mailto:brian@python.org" target="_blank">brian@python.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, May 7, 2014 at 7:38 AM, Doug Hellmann<br>
<<a href="mailto:doug.hellmann@dreamhost.com">doug.hellmann@dreamhost.com</a>> wrote:<br>
> On Tue, May 6, 2014 at 5:45 PM, Joe Gordon <<a href="mailto:joe.gordon0@gmail.com">joe.gordon0@gmail.com</a>> wrote:<br>
>><br>
>><br>
>><br>
>> On Tue, May 6, 2014 at 6:54 AM, Dean Troyer <<a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a>> wrote:<br>
>>><br>
>>> On Tue, May 6, 2014 at 7:02 AM, Thierry Carrez <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Would you take over the Python client libraries as well ? On one hand<br>
>>>> 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>
>>><br>
>>><br>
>>> The future of the existing client libs has not been settled, my working<br>
>>> assumption is that they would remain with their home programs as they are<br>
>>> now. From the start OpenStackClient was meant to be a clean-slate for the<br>
>>> CLI and the Python SDK is taking the same basic approach.<br>
>><br>
>><br>
>><br>
>> Very excited for the OpenStackClient, it is already way nicer then the<br>
>> existing clients.<br>
>><br>
>><br>
>> Just working this out in my head. So the work flow would be:<br>
>><br>
>> 1. At first ClientTools consist of just the OpenStackClient<br>
>> 2. When the pythonSDK is ready to move off of stackforge, it will live in<br>
>> ClientTools<br>
>> 3. Specific python-*clients will be rewritten (from scratch?) to use the<br>
>> PythonSDK. But this time they won't have a built in CLI. These libraries<br>
>> will live along side the respective servers (so nova's python-novaclient<br>
>> will live in Compute)? All while moving OpenStackClient to the new libraries<br>
>><br>
>><br>
>> Is that what you are proposing?<br>
><br>
> My understanding is that the SDK aims to be a ground-up replacement<br>
> for the existing disparate client libraries. Whether that replacement<br>
> is appropriate for use inside OpenStack may be up for debate (I think<br>
> I remember someone saying that wasn't necessarily a goal, with the<br>
> focus being on end users, but I haven't been able to attend many of<br>
> the meetings so my information may be out of date).<br>
<br>
</div></div>Ideally the python-openstacksdk becomes the one-stop shop for<br>
interacting with OpenStack as an OpenStack contributor, an operator,<br>
an end-user of an OpenStack cloud, etc. If you're writing Python code<br>
to work with OpenStack, that would be the place to go for code, tools,<br>
examples, and documentation.<br></blockquote><div><br></div><div><br></div><div>Cool, that is even better.</div><div><br></div><div>So then step 3 would be:</div><div><br></div><div>* Each project can continue maintaining there existing python-*client or just deprecate it in favor of the what ClientTools will have.</div>
<div><br></div><div>If so that sounds great.</div><div><br></div><div><br></div><div>Would client tools be limited to only a pythonSDK or in the future could it potentially have other languages?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><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>
</div></div></blockquote></div><br></div></div>