The change introduces the possibility to run the persister with the new
confluent-kafka client. It has to be enabled in the configuration file.
Story: 2003705
Task: 35858
Depends-On: https://review.opendev.org/675297
Change-Id: I8d9e173e9a252712fb285c0676c26334e1f677a7
Change upgrades the monasca-notification to leverage
the capabilities of both oslo.log and oslo.conf:
- configuration of logging separated from application settings
- ability to enforce data types for application settings
- ability to use oslo.config-generator capabilities
- automatic configuration parsing done by oslo.cfg
That change will bring it closer to the rest of monasca
components where such transition has happened already.
However, in the rest of monasca, oslo.cfg was partially
or fully implemented whereas monasca-notification has
been relying on YAML based configuration file.
Therefore backward compatybility for such format will
be kept for now.
Story: 2000959
Task: 4093
Task: 4092
Change-Id: Ia75c3b60d0fada854178f21ca5ccb9e6a880f37f
Absolute paths are required for importing modules.
Python3 cannot find modules if absolute paths are not used.
Change-Id: Id060f269bfb1d17ccad844451678359e664386fa
Add new section to config file with configuration for statsd
host and port. Add modification in notification engines.
According to the monasca-agent change:
https://review.openstack.org/#/c/381417
Change-Id: I6e99bae5e50f3670ae8b4a0c7ac5af3c747bcd68
This patch set modifies lines which are importing objects
instead of modules. As per openstack import guide lines, user should
import modules in a file not objects.
http://docs.openstack.org/developer/hacking/#imports
Change-Id: I3c5c7368fb006f3691d07cef9557c20a42cc5b76
This patch
1. Supports for loading new notification types as plugins.
2) Adds new plugins for HipChat and Slack
3) Insert Notification types during startup
Partially-implements: blueprint notification-engine-plugin
Change-Id: I246ced3fe22a9797a3c8384f7bda166797cfac3a
New periodic notification engine that will take a notification send it, and then
place it back onto the periodic notification topic. Once the alarm associated
with the notification has transitioned to a state that is different from the
original state the notification is removed from the queue.
Change-Id: Ie3103a0ec30abcd8dfc53869b1c3135953aabf3a
The retry engine did not convert a notification object into json before
attempting to send it to Kafka and the Kafka publisher raised an exception.
This causes the notification system to restart before committing that offset to
Kafka. At that point the notification system is stuck because there's no way
to move past the notification that's causing the restart.
Change-Id: I473a0fa14f28b945702d879f5b17c5807f89e887
Closes-Bug:#1566057
Witek Bedyk