<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div><br>
</div>
<div><br>
On Jan 16, 2014, at 5:42 AM, "Chris Jones" <<a href="mailto:cmsj@tenshu.net">cmsj@tenshu.net</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>Hi</div>
<div><br>
</div>
<div>Once a common library is in place, is there any intention to (or resistance against) collapsing the clients into a single project or even a single command (a la busybox)?</div>
<div><br>
</div>
<div>(I'm thinking reduced load for packagers, simpler installation for users, etc)<br>
<br>
<div>Cheers,</div>
<div>--</div>
<div>Chris Jones</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Based on the email I sent; ideally we'd expand the blueprint to include these details and speak to the PTLs for each project.</div>
<div><br>
</div>
<div>Ideally (IMO) yes - long term they would be collapsed into one or two packages to install. However at very least the code can be made so that the core functionality is in the common/single sdk backend and openstackcli, and each project CLI can derive their
named/branded project specific one for that.</div>
<div><br>
</div>
<div>For standalone installs of nova or swift for example; not pushing users to use the entire openstackclient makes sense, instead guiding users to use a tool dedicated to that.</div>
<div><br>
</div>
<div>There are pros and cons on both sides, meeting in the middle at least collapses the heavy lifting into the common code base.</div>
<br>
<blockquote type="cite">
<div>
<div><br>
On 15 Jan 2014, at 19:37, Doug Hellmann <<a href="mailto:doug.hellmann@dreamhost.com">doug.hellmann@dreamhost.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div class="gmail_default" style="font-size:small">Several people have mentioned to me that they are interested in, or actively working on, code related to a "common" client library -- something meant to be reused directly as a basis for creating a common library
for all of the openstack clients to use. There's a blueprint [1] in oslo, and I believe the keystone devs and unified CLI teams are probably interested in ensuring that the resulting API ends up meeting all of our various requirements.</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">If you're interested in this effort, please subscribe to the blueprint and use that to coordinate efforts so we don't produce more than one common library. ;-)</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">Thanks,</div>
<div class="gmail_default" style="font-size:small">Doug</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">[1] <a href="https://blueprints.launchpad.net/oslo/+spec/common-client-library-2">https://blueprints.launchpad.net/oslo/+spec/common-client-library-2</a></div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>OpenStack-dev mailing list</span><br>
<span><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a></span><br>
<span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br>
</div>
</blockquote>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>OpenStack-dev mailing list</span><br>
<span><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a></span><br>
<span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br>
</div>
</blockquote>
</body>
</html>