Deployment using Mistral workflow

Registered by Jason E. Rist on 2016-09-01

Use Mistral action to trigger deployment https://review.openstack.org/#/c/357125/

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 on 2016-09-19
Completed by
Florian Fuchs on 2016-12-06

Related branches

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://review.openstack.org/#q,topic:bp/deployment-using-mistral-workflow,n,z

Addressed by: https://review.openstack.org/357125
    Migrate Deploy action to Mistral

(?)

Work Items

Work items:
* Use TripleO workflow to start the deployment: DONE
* Poll Heat /v1/​{tenant_id}​/stacks/​{stack_name} for deployment status: DONE
* Poll Heat /v1/​{tenant_id}​/stacks/​{stack_name}/resources to update the progress bar: DONE

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.