tripleo

  1. Bug #1757372
  2. Comment #24

Comment 24 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/576190
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=6c32361cfd5067f4d620a685a47291abe4f4a2f8
Submitter: Zuul
Branch: master

commit 6c32361cfd5067f4d620a685a47291abe4f4a2f8
Author: Dougal Matthews <email address hidden>
Date: Mon Jun 18 16:57:13 2018 +0100

    Use the standard messaging in the stack workbook

    Update the stack 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: I2bf3b0eea591969892d8c98937f62719c4e02361
    Related-Bug: #1757372