Support Zaqar for Heat stack events

Bug #1639283 reported by Thomas Herve on 2016-11-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Thomas Herve

Bug Description

Heat supports zaqar as a transport for events: . Currently tripleo uses polling on the event API, it'd be nice to provide an alternative using Zaqar, which is already used for mistral statuses.

We need to:
 * Provide a similar API to poll_for_events in heatclient
 * Add an event sink in the environment to push to a queue
 * Use the API consuming from the queue instead of poll_for_events.

It has benefits for the CLI case (more responsive, less resource consume from Heat), and it should provide a nice integration point for triple-ui as well.

Thomas Herve (therve) on 2016-11-04
Changed in tripleo:
assignee: nobody → Thomas Herve (therve)
Changed in tripleo:
status: New → In Progress

Submitter: Jenkins
Branch: master

commit f4f0e92d75e635f08bdcbe14327a2956ad647f22
Author: Thomas Herve <email address hidden>
Date: Thu Nov 3 10:51:04 2016 +0100

    Use a Zaqar queue to get stack events

    This adds the ability to use Zaqar to retrieve Heat events instead of
    polling the API.

    Change-Id: I3b836637d4e72aaf7183dbabf0b0e32c2caa8270
    Closes-Bug: #1639283

Changed in tripleo:
status: In Progress → Fix Released
Changed in tripleo:
importance: Undecided → Medium
milestone: none → pike-1
Thomas Herve (therve) on 2017-03-28
Changed in tripleo:
status: Fix Released → In Progress
Thomas Herve (therve) wrote :

Patch was reverted.

This issue was fixed in the openstack/python-tripleoclient 7.0.0 release.

Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Alex Schultz (alex-schultz) wrote :

Given that this was reverted, are we still going to proceed with this?

Thomas Herve (therve) wrote :

A new patch has been sitting there for a bit:

But it doesn't look like it gets much traction, so I can abandon if none is interested. I thought UI people would be, but it doesn't seem to be the case :).

Julie Pichon (jpichon) wrote :

I think many in the UI squad mainly follow the 'ui' bug tag and may have missed this, adding the tag for visibility.

tags: added: ui
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3

Change abandoned by Thomas Herve (<email address hidden>) on branch: master
Reason: Not doing it for now.

Thomas Herve (therve) on 2018-01-11
Changed in tripleo:
status: In Progress → New
Changed in tripleo:
status: New → Triaged
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers