Use the standard messaging in the undercloud_backup workbook
Update the undercloud_backup workbook to use the standard message sending
workflow. This workflow reduces the boilerplate that is copied between
workflows by defining the message structure, providing the retry logic
and ensuring the task on a "FAILED" message.
The workflow also offers optional persistence in Swift. If the plan name
is given to the workflow it will store the messages in a Swift container
named <plan_name>-messages.
Reviewed: https:/ /review. openstack. org/576189 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=9ca3346709b 17aef09abb2e34c 6b64f51d6e9aae
Committed: https:/
Submitter: Zuul
Branch: master
commit 9ca3346709b17ae f09abb2e34c6b64 f51d6e9aae
Author: Dougal Matthews <email address hidden>
Date: Mon Jun 18 16:55:52 2018 +0100
Use the standard messaging in the undercloud_backup workbook
Update the undercloud_backup workbook to use the standard message sending
workflow. This workflow reduces the boilerplate that is copied between
workflows by defining the message structure, providing the retry logic
and ensuring the task on a "FAILED" message.
The workflow also offers optional persistence in Swift. If the plan name -messages.
is given to the workflow it will store the messages in a Swift container
named <plan_name>
Change-Id: I71e761c1295ae0 d0ca2773c7521b6 a57cabd6227
Related-Bug: #1757372