On Thu, Jan 16, 2014 at 9:54 AM, Alexei Kornienko < alexei.kornie...@gmail.com> wrote: > > Knowing usual openstack workflow I'm afraid that #1,#2 with a waterfall > approach may take years to be complete. > And after they'll be approved it will become clear that this architecture > is already outdated. > We try to use iterative approach for clients refactoring. > We started our work from removing code duplication because it already > gives a direct positive effect on client projects. > If you can show us better way of moving forward please help us by > uploading patches on this topic. > > Talk is cheap. Show me the code. (c) Linus >
python-keystoneclient has the Session bits commiited, and the auth bits in flight. So we'll all be using it one way or another. OSC has a very-slimmed-down model for replacing the REST and API layers already present underneath the object-store commands as an experiment to see how slim I could make then and still be usable. It isn't necessarily what I want to ship everywhere, but the REST layer is eerily similar to Jamie's in keystoneclient. There's why my bias... dt -- Dean Troyer dtro...@gmail.com
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
