Workflow changes for UI to support for config-download
See https:/
The Mistral workflows in tripleo-common have some required changes for the config-download blueprints to be possible.
Currently config-download is implemented in tripleoclient. This needs to be moved to the deploy workflow so it can be used by the CLI and the UI
Blueprint information
- Status:
- Complete
- Approver:
- Dougal Matthews
- Priority:
- High
- Drafter:
- Dougal Matthews
- Direction:
- Approved
- Assignee:
- Dougal Matthews
- Definition:
- Approved
- Series goal:
- Proposed for rocky
- Implementation:
-
Implemented
- Milestone target:
-
rocky-2
- Started by
- Dougal Matthews
- Completed by
- Dougal Matthews
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Standardise Workflow messaging and optionally persist messages
Addressed by: https:/
Optionally run config download at the end of stack create/update
Gerrit topic: https:/
Addressed by: https:/
Don't exit on a RUNNING message for deploy workflow
Gerrit topic: https:/
Addressed by: https:/
WIP Optionally run config download at the end of stack create/update
Addressed by: https:/
Verify the Swift container exists with a small utility workflow
Addressed by: https:/
Send a message every time we get the stack
Gerrit topic: https:/
Addressed by: https:/
Add type and plan_name to message sent from ansible-playbook action
Addressed by: https:/
Add new undeploy_plan workflow
Addressed by: https:/
Delete messages container on plan deletion
Gerrit topic: https:/
Addressed by: https:/
Add recover_deployment workflow
Gerrit topic: https:/
Addressed by: https:/
Don't exit on a RUNNING message for deploy workflow
Addressed by: https:/
Standardise Workflow messaging and optionally persist messages
Work Items
Dependency tree
* Blueprints in grey have been implemented.
