Use the standard messaging in the plan_management workbook
Update the plan_management 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/554595 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=dca8418e78e c50a8dd3a6584e2 9b68b67ce5bd69
Committed: https:/
Submitter: Zuul
Branch: master
commit dca8418e78ec50a 8dd3a6584e29b68 b67ce5bd69
Author: Dougal Matthews <email address hidden>
Date: Tue Mar 20 15:35:26 2018 +0000
Use the standard messaging in the plan_management workbook
Update the plan_management 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 d83fe98e20445a4 f13b4ea0686
Change-Id: I9755eaa6621ec1