91ca44fe36
There's references to the auth_token middleware in keystoncelient. The auth_token middleware has been moved to keystonemiddleware and the version in keystoneclient shouldn't be used anymore. If these references aren't updated, then when options are changed in keystonemiddleware.auth_token the heat-api will fail to start because there's duplicate options in keystoneclient.middleware.auth_token. Change-Id: I04573aa5ff967afe3e00329f797fcc71b779e7b3 Closes-Bug: #1379082 |
||
---|---|---|
.. | ||
heat_keystoneclient_v2 | ||
README.md | ||
setup.cfg | ||
setup.py |
Heat Keystone V2
This plugin is a Keystone V2 compatible client. It can be used to replace the default client for clouds running older versions of Keystone.
Some forward compatibility decisions had to be made:
- Stack domain users are created as users on the stack owner's tenant rather than the stack's domain
- Trusts are not supported
Installation
-
From this directory run: sudo python ./setup.py install
-
Set the
keystone_backend
option toheat.engine.plugins.heat_keystoneclient_v2.client.KeystoneClientV2
How it works
By setting the keystone_backend
option, the KeystoneBackend class in
heat/common/heat_keystoneclient.py
will instantiate the plugin
KeystoneClientV2 class and use that instead of the default client in
heat/common/heat_keystoneclient.py
.