Use the standard messaging in the baremetal workbook
Update the baremetal 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/552460 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=3b28b87e49c f633e1aa9b6c55c 7d2784c2cb0217
Committed: https:/
Submitter: Zuul
Branch: master
commit 3b28b87e49cf633 e1aa9b6c55c7d27 84c2cb0217
Author: Dougal Matthews <email address hidden>
Date: Tue Mar 13 09:17:43 2018 +0000
Use the standard messaging in the baremetal workbook
Update the baremetal 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>
Related-Bug: #1757372 bdb845965102118 5cfb9fd1a8f
Change-Id: I1665ae56a88557