Since [1], monasca-notification supports the standard oslo.config
based configuration style (ini file instead of yaml). The old
notification.yaml file still works but is deprecated.
So switching to use the new oslo.config based file is the way to go
forward.
Also adjust the zuul job to copy /var/log/monasca/notification and
/etc/monasca/notification.conf so debugging will be a bit easier.
[1] https://review.openstack.org/#/c/464768/
Story: 2004862
Task: 35646
Depends-On: https://review.opendev.org/668508
Depends-On: https://review.opendev.org/663960
Change-Id: I489d66d623c3e27ca28ba87ebde32264b13ac0f3
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 commit will update devstack plugin to add required parameters to
notification.yaml for keystone authentication.
Change-Id: I61b3b437a06f5e62b41c567d361e1d73a4e55d0e
Partially-Implements: blueprint add-monasca-push-driver
Story: 2003105
Task: 23221
Included a field 'grafana_url' in notification.yaml
for email notifications and replaced it with the
respective grafana host in plugin.sh.
Change-Id: I581b2e9d12632cc7509d24525cc225b60514a8c3
Story: 2001052
Task: 4653
Adjust monasca-notification installation with changes:
- start/stop of monasca-notification proces handles through run_process
and stop_process and no service files
- setting up environment with devstack function
- use USE_VENV for monasca-notification
- installing monasca-notification dependencies from git
- remove service file from devstack/files/monasca-notification
Also added code from Idbe5bdf56fb280412c34f04de8f2e2f301a7a432
Depends-On: Idbe5bdf56fb280412c34f04de8f2e2f301a7a432
Change-Id: Ic581fbdd2db57c9a2f13f1646eb9485c5dd0f62b
Following commits simplifies devstack setup
by relying on $DATABASE_USER (as provided by devstack)
instead of creating custom users.
Also removed methods that were creating users
for different databases which reduced amount of
code
Change-Id: Ida5308bb6945813b5b52035dab93ff4e5c82c45f
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
Thomas Bechtold