Ensure heat works when only an auth_token is specified
To flush out any remaining issues, I propose the following:
- by default, python-heatclient should aquire an auth token and only pass the token, not the password (able to be overridden)
- in heat/engine/
This should have some performance improvements in reducing keystone token generation round-trips. Upstream fixes should be provided for any openstack clients which still don't handle this case properly
Blueprint information
- Status:
- Complete
- Approver:
- Steven Hardy
- Priority:
- Medium
- Drafter:
- Steve Baker
- Direction:
- Approved
- Assignee:
- Steve Baker
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
- Implemented
- Milestone target:
- 2013.2
- Started by
- Steve Baker
- Completed by
- Steve Baker
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Fix swift client token authentication
Addressed by: https:/
Allow cinder operations with only auth_token
Addressed by: https:/
Pass in endpoint url for swift auth_token auth
Addressed by: https:/
Allow nova operations with only auth_token
Addressed by: https:/
Pass in endpoint url for quantum auth_token auth
Addressed by: https:/
No longer pass no_cache=True to novaclient create
Addressed by: https:/
Test utils dummy_context for tests that need one.
Addressed by: https:/
Move url_for into heat_keystonecl
Addressed by: https:/
Migrate all tests to use dummy_context.
Addressed by: https:/
Only use a token for openstack client operations.