Post-deployment config for UI
Bug #1634505 reported by
Ana Krivokapić
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
Critical
|
Ana Krivokapić |
Bug Description
TripleO UI is lacking the post-deployment config[1]. We need to either re-implement the config in the UI, or (preferably) to refactor it to a mistral workflow which will then be called from both the CLI and the UI.
Changed in tripleo: | |
assignee: | nobody → Ana Krivokapić (akrivoka) |
tags: | added: newton-backport-potential |
Changed in tripleo: | |
milestone: | ocata-1 → none |
To post a comment you must log in.
What remains in the postconfig that we actually need?
Most of the logic should now be in puppet, so it'd be good to understand which pieces aren't so we can decide if it's better to just fix those and remove that from the client.
Historically os-cloud-config has done a bunch of stuff like endpoint creation, but it's been a big headache because it's decoupled from the heat logic, so if possible I'd like to take this opportunity to kill that old model completely vs perpetuating it in mistral.