← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1652344] [NEW] Allow keystone v3 in the designate driver

 

Public bug reported:

https://review.openstack.org/398359
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 91d048dbde83a52f43aceebaf1b1e1ef0937602d
Author: Gyorgy Szombathelyi <gyurco@xxxxxxxxxxx>
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

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: doc neutron

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1652344

Title:
      Allow keystone v3 in the designate driver

Status in neutron:
  New

Bug description:
  https://review.openstack.org/398359
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 91d048dbde83a52f43aceebaf1b1e1ef0937602d
  Author: Gyorgy Szombathelyi <gyurco@xxxxxxxxxxx>
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1652344/+subscriptions


Follow ups