tripleo-common/workbooks/scale.yaml
Emilien Macchi 5a7081ea8c Remove duplications of tasks in scale workbook
Since we refactored the deployment workbook, we can easily re-use the
tasks from it in the scale workbook.

A patch in tripleoclient will change the way we call workbooks to re-use
what was done in deployment workbook instead of scale.

Needed-By: Ie8e15589197e9725a1cae2d29137f05fefa427c1
Change-Id: Ibc980e9162bf109de7e7ef338c9bd602174c8448
2019-05-09 20:17:54 +00:00

63 lines
1.8 KiB
YAML

---
version: '2.0'
name: tripleo.scale.v1
description: TripleO Overcloud Deployment Workflows v1
workflows:
delete_node:
description: deletes given overcloud nodes and updates the stack
input:
- plan_name
- nodes
- timeout: 240
- queue_name: tripleo
tags:
- tripleo-common-managed
tasks:
delete_node:
action: tripleo.scale.delete_node nodes=<% $.nodes %> timeout=<% $.timeout %> container=<% $.plan_name %>
on-success: wait_for_stack_in_progress
on-error: set_delete_node_failed
set_delete_node_failed:
on-success: send_message
publish:
status: FAILED
message: <% task(delete_node).result %>
wait_for_stack_in_progress:
workflow: tripleo.stack.v1.wait_for_stack_in_progress stack=<% $.plan_name %>
on-success: wait_for_stack_complete
on-error: wait_for_stack_in_progress_failed
wait_for_stack_in_progress_failed:
on-success: send_message
publish:
status: FAILED
message: <% task(wait_for_stack_in_progress).result %>
wait_for_stack_complete:
workflow: tripleo.stack.v1.wait_for_stack_complete_or_failed stack=<% $.plan_name %>
on-success: send_message
on-error: wait_for_stack_complete_failed
wait_for_stack_complete_failed:
on-success: send_message
publish:
status: FAILED
message: <% task(wait_for_stack_complete).result %>
send_message:
workflow: tripleo.messaging.v1.send
input:
queue_name: <% $.queue_name %>
type: <% execution().name %>
status: <% $.get('status', 'SUCCESS') %>
execution: <% execution() %>
message: <% $.get('message', '') %>