Use auth_token_info to initialize solum_keystoneclient sessions
Now we have the token info available in the request context, we can
avoid always re-requesting another token every time a client is
created.
This should be better for performance as it avoids one extra request to
keystone, and it also enables trust-scoped tokens to be more easily
used, since these cannot be used to request another token, thus
authentication will fail with the current scheme.
This is needed for the builder to be used from a mistral task.
Reviewed: https:/ /review. openstack. org/99338 /git.openstack. org/cgit/ stackforge/ solum/commit/ ?id=286bf3a2b3a b5f0934729320be f0fa2c99003115
Committed: https:/
Submitter: Jenkins
Branch: master
commit 286bf3a2b3ab5f0 934729320bef0fa 2c99003115
Author: Angus Salkeld <email address hidden>
Date: Thu Jun 12 13:49:30 2014 +1000
Use auth_token_info to initialize solum_keystonec lient sessions
Now we have the token info available in the request context, we can
avoid always re-requesting another token every time a client is
created.
This should be better for performance as it avoids one extra request to
keystone, and it also enables trust-scoped tokens to be more easily
used, since these cannot be used to request another token, thus
authentication will fail with the current scheme.
This is needed for the builder to be used from a mistral task.
Change-Id: Ic03e315a7a7fb2 9bd8a499032b61b efea260ab7e
Partial-Bug: #1317293