Hi

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)?

(I'm thinking reduced load for packagers, simpler installation for users, etc)

Cheers,
--
Chris Jones

> On 15 Jan 2014, at 19:37, Doug Hellmann <doug.hellm...@dreamhost.com> wrote:
> 
> 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.
> 
> 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. ;-)
> 
> Thanks,
> Doug
> 
> 
> [1] https://blueprints.launchpad.net/oslo/+spec/common-client-library-2
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to