Go to file
Steven Fitzpatrick 4fdcff593c Fix incorrect prometheus alert names in nagios
I noticed a some nagios service checks were checking prometheus
alerts which did not exist in our default prometheus configuration.
In one case a prometheus alert did not match the naming convention
of similar alerts.

One nagios service check, ceph_monitor_clock_skew_high, does not
have a corresponding alert  at all, so I've changed it to check the

node_ntmp_clock_skew_high

alert, where a node has the label ceph-mon="enabled".

Change-Id: I2ebf9a4954190b8e2caefc8a61270e28bf24d9fa
2020-01-03 10:30:08 -06:00
2019-12-17 18:47:24 +00:00
2019-11-11 09:42:14 +00:00
2019-12-17 18:47:24 +00:00
2019-10-23 19:16:28 +00:00
2019-11-12 11:28:22 -06:00
2019-12-12 10:51:19 +01:00
2019-04-19 19:34:11 +00:00
2019-02-27 15:02:06 +08:00
2018-05-15 13:04:28 -05:00
2019-09-24 15:51:54 +08:00

Openstack-Helm-Infra

Mission

The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.

For more information, please refer to the OpenStack-Helm repository.

Communication

  • Join us on Slack - #openstack-helm
  • Join us on IRC: #openstack-helm on freenode
  • Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
  • Meeting Agenda Items: Agenda

Launchpad

Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.

Description
Helm charts for deploying OpenStack on Kubernetes
Readme 129 MiB
Languages
Smarty 81.2%
Shell 16.9%
Python 1.4%
Jinja 0.3%
Makefile 0.2%