Reviewed: https://review.openstack.org/398359 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=91d048dbde83a52f43aceebaf1b1e1ef0937602d Submitter: Jenkins Branch: master
commit 91d048dbde83a52f43aceebaf1b1e1ef0937602d Author: Gyorgy Szombathelyi <[email protected]> Date: Wed Nov 16 14:37:38 2016 +0100 Allow keystone v3 in the designate driver Using the loader from keystoneauth1, it is possible to easily use keystone v3 options in [designate]. For the end user, it means she/he must specify designate.auth_type, then she/he can specify an Keystone v3 endpoint in designate.auth_url. Change-Id: I8bb02f11e60767dacdf6ac852979cfa82de1e08b Closes-bug: #1585976 DocImpact ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1585976 Title: Designate plugin lacks of Keystone authentication options Status in neutron: Fix Released Bug description: The designate plugin has a very simple keystone authentication: - It supports only keystone v2 - It doesn't honor any certificates (client or CA), nor insecure TLS option It would be good to re-use the nova auth part (even the keystoneauth1 lib). To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1585976/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
