There is no public api to get auth_token from client

Bug #1150051 reported by Nachi Ueno
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-neutronclient
Fix Released
Wishlist
Oleg Bondarev

Bug Description

There is no public api to get auth_token from client.
When we use python-quantumclient with eventlet, we need to initialize quantum for each eventlet thread. We can re-use auth_token on different quantum client object for that case. However current client didn't provide public api to get auth.

Nachi Ueno (nati-ueno)
Changed in python-quantumclient:
status: New → Confirmed
importance: Undecided → Wishlist
Nachi Ueno (nati-ueno)
description: updated
Changed in python-quantumclient:
assignee: nobody → Oleg Bondarev (obondarev)
Changed in python-quantumclient:
status: Confirmed → In Progress
summary: - There is no public api to get auto_token from client
+ There is no public api to get auth_token from client
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-quantumclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/24167

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-quantumclient (master)

Reviewed: https://review.openstack.org/24167
Committed: http://github.com/openstack/python-quantumclient/commit/6f7e76ec3b4777816e0a5d7eaeef0026d75b60e6
Submitter: Jenkins
Branch: master

commit 6f7e76ec3b4777816e0a5d7eaeef0026d75b60e6
Author: Oleg Bondarev <email address hidden>
Date: Tue Mar 12 16:13:02 2013 +0400

    Add public api to get authentication info from client

    auth info (in particular token and endpoint_url) can be reused
    in different quantum client instances to reduce roundtrips with keystone

    fixes bug 1150051

    Change-Id: I3b2f23f364099bdb08992130d5edb87222e8d387

Changed in python-quantumclient:
status: In Progress → Fix Committed
Akihiro Motoki (amotoki)
Changed in python-neutronclient:
milestone: none → 2.2.1-2.2.6
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.