Bug 1041189 - [RFE][nova]: Reduce the number of token checks made during networking calls
Summary: [RFE][nova]: Reduce the number of token checks made during networking calls
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 13:53 UTC by RHOS Integration
Modified: 2015-11-26 17:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:31:52 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 13:53:10 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/fewer-networking-token-checks.

Description:

Due to the current implementation of get_client() for quantum calls, not only does each quantum connection require a new token check, but also quantum clients are created every time, even if they use the same credentials and checks the credentials separately on each call.

Caching the client would allow making fewer token checks and reduce the access time in general.

For example, currently each request for instance metadata will result in 4 token checks in a row. Another request needs anoter 4, etc.

This could be reduced to only 1 request per lifetime of a token, so subsequent requests become keystone-free.

One new issue of this scheme would be that changing endpoints may result in failed requests until the token is invalidated. On the other hand, this is not a problem specific to this scenario, as the endpoint may change between the get_token call and another request - {quantum,glance,keystone}client should handle that situation internally anyway.

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.