tripleoclient checks and validations should be mistral actions
Bug #1638697 reported by
James Slagle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Brad P. Crochet |
Bug Description
The checks and validations in tripleoclient prior to a deployment stack-create or stack-update should probably live in tripleo-common so they can be executed by the UI.
Unless all of that has already been reimplemented in tripleo-
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → ocata-2 |
tags: | added: tripleoclient workflows |
tags: | added: validations |
Changed in tripleo: | |
assignee: | nobody → Dougal Matthews (d0ugal) |
Changed in tripleo: | |
assignee: | Dougal Matthews (d0ugal) → nobody |
Changed in tripleo: | |
assignee: | nobody → Brad P. Crochet (brad-9) |
Changed in tripleo: | |
status: | Triaged → Incomplete |
Changed in tripleo: | |
status: | Incomplete → Confirmed |
Changed in tripleo: | |
milestone: | ocata-2 → ocata-3 |
Changed in tripleo: | |
status: | Confirmed → Triaged |
Changed in tripleo: | |
milestone: | ocata-3 → ocata-rc1 |
milestone: | ocata-rc1 → pike-1 |
tags: | added: ocata-backport-potential |
Changed in tripleo: | |
assignee: | Brad P. Crochet (brad-9) → Emilien Macchi (emilienm) |
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
To post a comment you must log in.
It does not appear that the pre-deploy validations have been implemented in tripleo-validations yet. Since tripleo-validations is currently opt-in, we do not want to lose the functionality of the existing validations in the client, so a move to tripleo-common and mistral actions makes sense as an interim step.