Deployment using Mistral workflow
Use Mistral action to trigger deployment https:/
Poll for Heat stack list and resources to retrieve deployment status and calculate progress
Post deployment: Run Post-deployment validations ( + setup overcloud nodes ssh key validations workflow)
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Jason E. Rist
- Direction:
- Needs approval
- Assignee:
- Florian Fuchs
- Definition:
- New
- Series goal:
- Accepted for newton
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Florian Fuchs
- Completed by
- Florian Fuchs
Related branches
Related bugs
Sprints
Whiteboard
* Deployment start:
The deployment is started using a tripleo-common workflow (Mistral-based), the result of the trigger is retrieved through the Zaqar websocket.
* Deployment result:
During deployment, heat is polled for to get the result of the deployment. This is already implemented.
* Deployment progress
During deployment, heat if polled for all resources of the current stack. The number of resources with status CREATE_COMPLETE against ones with other stati is used to calculate the progress percentage value.
Gerrit topic: https:/
Addressed by: https:/
Migrate Deploy action to Mistral
Work Items
Work items:
* Use TripleO workflow to start the deployment: DONE
* Poll Heat /v1/{tenant_
* Poll Heat /v1/{tenant_
