Replace the scale.yaml workbook with a non-Mistral solution and deprecate workflows
Bug #1835244 reported by
Dougal Matthews
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Without the tripleo-ui, there is little advantage to Mistral in tripleo. We can simplify the architecture by deprecating and removing it.
Revision history for this message
| Dougal Matthews (d0ugal) wrote | #1 |
| Changed in tripleo: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
On the face of it, this looks like it will be easy. The workflow is small.
However there is lots of code in the ScaleDownAction that is very bound to the Mistral context (and it creates and calls other Mistral actions and passes the context).