On Wed, Apr 6, 2016 at 3:26 PM Boris Pavlovic <bpavlo...@mirantis.com> wrote:
> > 2) This will reduce scope of Keystone, which means 2 things > 2.1) Smaller code base that has less issues and is simpler for testing > 2.2) Keystone team would be able to concentrate more on fixing > perf/scalability issues of authorization, which is crucial at the moment > for large clouds. > I'm not sure that this is entirely true. If we truly just split up the project, meaning we don't remove functionality, then we'd have the same number of bugs and work. It would just be split across two projects. I think the current momentum to get out of the authn business is still our best bet. As Steve mentioned this is ongoing work. -- David
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
