Support Zaqar for Heat stack events

Bug #1639283 reported by Thomas Herve
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Heat supports zaqar as a transport for events: http://docs.openstack.org/developer/heat/template_guide/environment.html#retrieving-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.

Tags: spec-lite ui
Thomas Herve (therve)
Changed in tripleo:
assignee: nobody → Thomas Herve (therve)
Changed in tripleo:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tripleoclient (master)

Reviewed: https://review.openstack.org/394420
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=f4f0e92d75e635f08bdcbe14327a2956ad647f22
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)
Changed in tripleo:
status: Fix Released → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tripleoclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/450886

Revision history for this message
Thomas Herve (therve) wrote :

Patch was reverted.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 7.0.0

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
Revision history for this message
Alex Schultz (alex-schultz) wrote :

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

Revision history for this message
Thomas Herve (therve) wrote :

A new patch has been sitting there for a bit: https://review.openstack.org/450886

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 :).

Revision history for this message
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on python-tripleoclient (master)

Change abandoned by Thomas Herve (<email address hidden>) on branch: master
Review: https://review.openstack.org/450886
Reason: Not doing it for now.

Thomas Herve (therve)
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
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
assignee: Thomas Herve (therve) → nobody
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers