Generic Event Backend

Registered by Qiming Teng on 2016-11-08

This spec is about a generic event backend abstraction.

Currently senlin has a DB backend to log events that might be interested to users/operators. However, we will also need to send out event notifications for integration with 3rd party software/services. Users/operators may want to dump the events into a file or a time series database for processing.

The blueprint proposes a generic interface for dumping events/notifications.

Details will be found at the specs file: http://git.openstack.org/cgit/openstack/senlin/tree/doc/specs/approved/generic-event.rst

Blueprint information

Status:
Complete
Approver:
Yanyan Hu
Priority:
Medium
Drafter:
Qiming Teng
Direction:
Approved
Assignee:
Qiming Teng
Definition:
Approved
Series goal:
Accepted for ocata
Implementation:
Implemented
Milestone target:
milestone icon ocata-2
Started by
Qiming Teng on 2016-11-18
Completed by
Qiming Teng on 2017-01-11

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/generic-event,n,z

Addressed by: https://review.openstack.org/398105
    Move event database driver out of engine

Addressed by: https://review.openstack.org/398225
    Revise the DB event dumper

Addressed by: https://review.openstack.org/399413
    Revise event dump to use the DB driver

Addressed by: https://review.openstack.org/400024
    Move notifications object down one level

Addressed by: https://review.openstack.org/400266
    Remove NotificationPayloadBase class

Addressed by: https://review.openstack.org/400267
    New fields for versioned notification

Addressed by: https://review.openstack.org/400649
    Exception payload for error notification

Addressed by: https://review.openstack.org/401104
    Tweak base objects/fields for notification

Addressed by: https://review.openstack.org/401951
    Allow None to be passed for Exception payload

Addressed by: https://review.openstack.org/401952
    Trivial: remove some redundant comment

Addressed by: https://review.openstack.org/401953
    Notification for cluster actions

Addressed by: https://review.openstack.org/402258
    Merge all notification objects/payloads

Addressed by: https://review.openstack.org/402261
    Versioned notifications for node actions

Addressed by: https://review.openstack.org/402277
    Message driver for event notification

Addressed by: https://review.openstack.org/403485
    Minor tweak to Database event driver

Addressed by: https://review.openstack.org/403494
    Remove event logging for action signal

Addressed by: https://review.openstack.org/403515
    Tweak 'cluster' and 'node' member of actions

Addressed by: https://review.openstack.org/403532
    Fix event calls from action base

Addressed by: https://review.openstack.org/403979
    Simplify database driver for notification/events

Addressed by: https://review.openstack.org/403993
    Extract common logic into base class

Addressed by: https://review.openstack.org/406446
    Add event dispatcher pluggin infrastructure

Addressed by: https://review.openstack.org/406574
    Further simplify event dispatch interface

Addressed by: https://review.openstack.org/406583
    Further simplify event module

Addressed by: https://review.openstack.org/406584
    Remove redundant parameters from event interface

Addressed by: https://review.openstack.org/406589
    Rename 'status' parameter to 'phase' in db driver

Addressed by: https://review.openstack.org/406595
    Get both event drivers into action

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.