Talking to heat via keystone, not via hardcoded credentials in tuskar.conf

Bug #1299013 reported by Ladislav Smola
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

We should be able to talk to heat, by setting a Trust in keystone.

Not sure about the details, but Heat is doing the same talking to Nova. So we should do the same.

Hardcoding credentials for heat into tuskar.conf is bad

Ladislav Smola (lsmola)
Changed in tuskar-ui:
importance: Undecided → High
status: New → Triaged
affects: tuskar-ui → tuskar
Rohan (kanaderohan)
Changed in tuskar:
assignee: nobody → Rohan (kanaderohan)
Revision history for this message
Rohan (kanaderohan) wrote :

I think this should be implemented via a blueprint (

There is lots of changes required for this like

- DB model for storing user credentials
- Modified keystoneclient like in Heat to use these user credentials
- Create and delete trusts during Create and delete of overcloud from tuskar api.

Revision history for this message
Ladislav Smola (lsmola) wrote :

Seems reasonable. Thanks for picking this up.

Changed in tuskar:
status: Triaged → Invalid
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.