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 address hidden> 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
Reviewed: https:/ /review. openstack. org/398359 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=91d048dbde8 3a52f43aceebaf1 b1e1ef0937602d
Committed: https:/
Submitter: Jenkins
Branch: master
commit 91d048dbde83a52 f43aceebaf1b1e1 ef0937602d
Author: Gyorgy Szombathelyi <email address hidden>
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 auth_type,
keystone v3 options in [designate].
For the end user, it means she/he must specify designate.
then she/he can specify an Keystone v3 endpoint in designate.auth_url.
Change-Id: I8bb02f11e60767 dacdf6ac852979c fa82de1e08b
Closes-bug: #1585976
DocImpact