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 | |
|---|---|---|---|---|---|
| tuskar |
Invalid
|
High
|
Rohan | ||
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
| Changed in tuskar-ui: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| affects: | tuskar-ui → tuskar |
| Changed in tuskar: | |
| assignee: | nobody → Rohan (kanaderohan) |
Revision history for this message
| Rohan (kanaderohan) wrote | #1 |
Revision history for this message
| Ladislav Smola (lsmola) wrote | #2 |
| Changed in tuskar: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
I think this should be implemented via a blueprint (https:/
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.