tripleo

  1. Bug #1757372
  2. Comment #10

Comment 10 for bug 1757372

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/572343
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=1adc25c9b269fe087a563fb57c3b6092137c3e42
Submitter: Zuul
Branch: master

commit 1adc25c9b269fe087a563fb57c3b6092137c3e42
Author: Dougal Matthews <email address hidden>
Date: Tue Jun 5 12:10:11 2018 +0100

    Use the standard messaging in the swift_rings_backup workbook

    Update the swift_rings_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.

    Change-Id: Iad199545d0093ccdedf082a945345ad4863ed4d0
    Related-Bug: #1757372