SQL schema scripts are replaced with Alembic command line tool.
Notification plugins are enabled in notification engine configuration
file.
The change also fixes the `sub_alarm` table schema. The foreign key must
refer to the field with the same data type, charset and collation.
Otherwise the schema migration fails occasionally with Python 3 with the
IntegrityError[1]:
oslo_db.exception.DBError: (pymysql.err.IntegrityError) (1215, 'Cannot add foreign key constraint')
[1] http://logs.openstack.org/61/622361/8/gate/monasca-tempest-python3-influxdb/26104a3/controller/logs/devstacklog.txt.gz#_2019-01-30_15_52_45_455
Change-Id: I95d7e91e62ff13e84f963fdbb3bca6b7dfd7c310
Story: 2001654
Task: 14421
This reverts commit 8781a256f0.
Since this only implements part of the silence / group / inhibit
feature, reverting until the rest is ready to go
Change-Id: Ied34507feb5d3580960c918254f905ab90d9691e
The new silence and inhibit rules will include tags on the alarm
that can be queried via the api. For more information and
documentation see: https://review.openstack.org/#/c/466403
Change-Id: I85b8bfc9338ee17709ec30aeb4b807b3bc12404e
Following commit provides:
- possibility of using postgres as database backend
- possibility of using ORM mapping in monasca:
- API
- Thresh
- Notification
Additionally:
- different approach of providing configuration settings
- removed unused winchester schema
- reworked execution phases of the plugin:
-- installing dependencies in the beginning
Implements: blueprint postgres-cli-support
Change-Id: Iae561b0c7e6b90cc7c9f5b122c0e4b37bc5ef843
Witold Bedyk