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.
This is a continuation of I1665ae56a88557bdb8459651021185cfb9fd1a8f.
Some old-style messaging was added after the refactor and some redundant
lines were not removed.
Reviewed: https:/ /review. openstack. org/576196 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=388665361d2 829424c640e5073 ee4137d67f1502
Committed: https:/
Submitter: Zuul
Branch: master
commit 388665361d28294 24c640e5073ee41 37d67f1502
Author: Dougal Matthews <email address hidden>
Date: Mon Jun 18 17:01:01 2018 +0100
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>
This is a continuation of I1665ae56a88557 bdb845965102118 5cfb9fd1a8f.
Some old-style messaging was added after the refactor and some redundant
lines were not removed.
Change-Id: Ieeabe23ffe134c f19634b4b052805 ae7165f34e6
Related-Bug: #1757372