tripleo

  1. Bug #1757372
  2. Comment #22

Comment 22 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/576188
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=4c24a04977e99d5fcd069ebfc85954d0bb083bc1
Submitter: Zuul
Branch: master

commit 4c24a04977e99d5fcd069ebfc85954d0bb083bc1
Author: Dougal Matthews <email address hidden>
Date: Mon Jun 18 16:54:01 2018 +0100

    Use the standard messaging in the scale workbook

    Update the scale 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: I906e0ae92bcd084f4bf6ec669d6be0f71dc7a29b
    Related-Bug: #1757372