Workbook name: | tripleo.messaging.v1 |
---|
TripleO Zaqar Workflows
Workflows in the Messaging Workbook
tripleo.messaging.v1.send
Send a message to a Zaqar queue and optionally persist it to Swift This workflow sends a standard message to Zaqar (taking care of the error handling and retry logic) and optionally persists the message to Swift. The output of the workflow directly matches the input, this means it can be used to send a message and set the output of the parent calling workflow. If plan_name is provided the message will be persisted to Swift. In a container named “{plan_name}-messages”. The swift objects will be named:
{TYPE}/{TIMESTAMP}.yaml
If a deployment_status is provided, the top-level deployment_status.yaml will also be updated, which will contain the deployment_status and the related message. The standard message format will be:
body: {
type: 'tripleo.workflow.name', # Matches the workflow name
payload: {
status: 'STATUS', # One of RUNNING, SUCCESS, FAILED
root_execution_id: 'UUID of the root execution',
execution_id: 'UUID',
message: "Human readable description",
< Arbitrary data. This should match the workflow output data >
}
}
Workflow inputs:
Input queue_name: | |
---|---|
Required. | |
Input type: | Required. |
Input execution: | |
Required. | |
Input {‘status’: | |
‘SUCCESS’}: Required. | |
Input {‘message’: | |
None}: Required. | |
Input {‘payload’: | |
{}}: Required. | |
Input {‘plan_name’: | |
None}: Required. | |
Input {‘deployment_status’: | |
None}: Required. |
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.