This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I4596e5c35143c0e7757cdf2acabdd6eac98159ea
Added devstack support to install and run below masakari-monitors
services:
1. instancemonitor
2. processmonitor
3. introspectiveinstancemonitor
Change-Id: If4c793e316f98f14748300fc0d9003faffefeea3
In patch [1], a new config option `connection` is introduced
in a new section `taskflow` to save the recovery workflow
details of the notification.
This patch configures this new config option during creation
of config files in devstack setup.
[1] : https://review.openstack.org/#/c/640798/
Change-Id: I2383aaefaeb522e1783e2769e78438410b8033f3
During uninstalling masakari using devstack, it fails to remove
policy.json.
This patch fixes this issue by pointing to the correct path of
the policy.json file.
Change-Id: I1b9c009fe4d4305f9b7992c0c46a65ba0bac61a8
masakari-dashboard will be installed/uninstalled only when
masakari and horizon services are enabled.
Change-Id: I46d33b7fe1f2f4100e1403cf3f6a4ea63990147e
As per community goal [1], this patch allows deploying
masakari-api with uwsgi.
NOTE:
This patch takes reference from the nova implementation of deploying
nova-api with uwsgi.
[1] https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html
Change-Id: I469d4b6df49ad3489722feae0b795c20a6a3913b
TEMPEST_SERVICES global variable is not supported
by devstack since long back.
- I380dd20e5ed716a0bdf92aa02c3730359b8136e4
- I9c24705e494689f09a885eb0a640efd50db33fcf
Service availability of tempest known services will be
set by devstack with local check.
- I02be777bf93143d946ccbb8e9eff637bfd1928d4
masakari does not have tempest plugin so it does
not need to have service register in tempest.
This commit removes the TEMPEST_SERVICES setting.
Change-Id: I30673a3d739e013caec2b8d4a2295d71ab40e491
Related-Bug: #1743688
Recently a commit: 188173a8072b143a28779b875af617ac7f35a92d got
merged into masakari which replaces a rpc method 'get_transport'
with 'get_rpc_transport'. The 'get_rpc_transport' expects the
oslo.messaging config option 'transport_url' [1] to be present in
the [DEFAULT] section of masakari.conf. The current masakari devstack
script doesn't add 'transport_url' in masakari.conf which results
into failure of devstack installation of masakari.
This patch fixes this issue by using an inbuilt devstack function
'iniset_rpc_backend' to add the 'transport_url' config option in
masakari.conf.
[1] * https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/transport.py#L44
* https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/transport.py#L201
Closes-Bug: #1728544
Change-Id: I75da054c6669aa90dd96c3ede3ae98de74275de2
To enable ssl support for masakari using devstack just
mention 'ENABLED_SERVICES+=,tls-proxy' in local.conf
file.
Change-Id: Ia65d20083c8740d7dbbc38600ffd7de06cf08010
Remove the use of identity admin endpoint.
The following patch removed the use of identity admin endpoint from devstack.
Try to remove /identity_admin
https://review.openstack.org/#/c/458226/
So this patch removes the use of identity admin endpoint from masakari
in accordance with the above patch.
Change-Id: I809c6323b68a97095dc904c65627535083ad08cc
Fixed os_privileged_user_auth_url "PROTOCOL://HOST/identity_admin"
to "PROTOCOL://HOST/identity".
Current devstack keystone service endpoint url is "PROTOCOL://HOST/identity".
So this patch fixes it.
Change-Id: I2700d541b8c72806e814d10d229032fabde2b38e
Added _process_unfinished_notifications to process notifications
which are in error or new state. This periodic task will execute at
regular interval defined by new config option
'process_unfinished_notifications_interval' defaults to 120 seconds.
The notifications which are in ‘new’ status will be picked up based
on a new config option ‘retry_notification_new_status_interval’ defaults
to 60 seconds.
Implements: bp add-periodic-tasks
Change-Id: I6e607d83f04618ad695a9614f84ad690b8804848
Recent devstack commit [1] broke masakari devstack plugin compatibility.
So, fix it by removing dependency on deleted env var in the same way
as it is done in devstack [2].
[1] I7c66e1d8d65f562596543ed8ca402dba8c8ea271
[2] I4e5c7e86aefe72fc21c77d423033e9b169318fec
Change-Id: Ibd4d8531fb9ac2cb3e9b0854bdd44011fc589070
Closes-Bug: #1644194
Masakari API's are allowed to be execute by admin only. So when external
service like masakari-instancemonitor calls masakari-api using masakari
user it does not have admin role associated with it's tenant. So it
returns HTTPForbidden 403 response to masakari-instancemonitor.
Added admin role to service tenant which has masakari user associated
with.
Change-Id: I505ea56bc022aad086f1090ff25b59ec85b70c41