Re: [openstack-dev] Removing OS_AUTH_SYSTEM
On Fri, Jun 21, 2013 at 5:46 PM, Monty Taylor mord...@inaugust.com wrote: This is some preliminary works to move novaclient to use keystoneclient instead of implementing its own[1] client to keystone. If the OS_AUTH_SYSTEM feature was really needed[2] we should then moving it to keystoneclient. Agree. If this is a general feature someone needs, we should move it to keystoneclient. agreed, I have started a review here which move alvaro works from novaclient to keystoneclient : https://review.openstack.org/#/c/36427/ Let me know alvaro if that would work for you before I polish it (fixing the tests) and get it ready for reviews. Chmouel. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Removing OS_AUTH_SYSTEM
Hello, We have discussed this some time ago to remove the OS_AUTH_SYSTEM from novaclient since this was implemented for RAX and these days RAX has moved to pyrax. Since last time I have looked into this it seems that there was some updates to it : https://github.com/openstack/python-novaclient/blob/master/novaclient/auth_plugin.py This made me wondering if it was needed by other people and why? This is some preliminary works to move novaclient to use keystoneclient instead of implementing its own[1] client to keystone. If the OS_AUTH_SYSTEM feature was really needed[2] we should then moving it to keystoneclient. Thoughts? Chmouel. [1] weirdo with bunch of obsoletes stuff I may need to add. [2] and IMO this goes against a one true open cloud. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
