This feature was broken and not stable enough for production deployment.
Related-bug: #1606831
Related-bug: #1643542
Change-Id: I0ce52ec01838d891c43d6e797617d3044a02d10f
This use case is not really supported because Nagios configuration is
too dependent on the LMA Collector plugin and in practice, no one
chooses this option.
DocImpact
Change-Id: Ia09efb40f476c1daec51530e2c0fb16bc6f99393
This allows to support several deployment scenarii where backends are not
deployed initialy, for instance when using the 'virt' nodes to deploy
LMA backends.
The patch factorizes manifests by moving all the configuration data of
InfluxDB and Elasticsearch into hiera.
DocImpact
Fixes-bug: #1570386
Change-Id: I8688bbd10d88bc8ef68b5d31e9edd62a764dc23d
The LMA collector uses by default the "infrastructure alerting" plugin
to send statuses if it is deployed within the environnement.
Previously, the user had to select explicitly the good option but
in practice the user forgot to select this option which leads to UNKNOWN
status for all service in the Nagios UI
Change-Id: Ia08f7e7f6763aeb3710ba26f88bfce6130a218bd
Fixes-bug: #1541462
This change removes all code which supports InfluxDB 0.8.
Change-Id: Ic136094f37b2f6ebfa1fe383460c4622676e2bfd
Implements: blueprint upgrade-influxdb-grafana
4 options:
- disable alerting (default)
- use a local node provided by the LMA Infrastructure Plugin
- use a remote Nagios server
- use the "standalone" SMTP support
implements blueprint alerting-lma-collector
Change-Id: If84275428b3d4b1b4b70177b8f87ec8b5bf6ee80
This change introduces the influxdb_legacy flag to the plugin's
configuration. This flag is hidden and defaults to true. Developers
will use it to introduce gradually the modifications needed to support
InfluxDB v0.9.
Change-Id: I3b93153c43dc013464519de656e26ed45b8653ee
Implements: blueprint upgrade-influxdb-grafana
The user doesn't need any more to specify the node name when using a
local deployment of influxdb-grafana and elasticsearch-kibana plugins.
Change-Id: I6d3512bb182a70aa05269825b77c30f16a25b066
This change also enables the collection of logs and notifications even
if the events indexation is disabled. The reason is that useful metrics
are extracted from this data such as HTTP response times, resource
creation time and so on.
The term 'event' is used to reference both logs and OpenStack notifcations.
Change-Id: I28814129f745a8ef3ee44d3d3cf1cc267337b840
This change disables the InfluxDB parameters when the 'local node' mode
is selected. In that case, all the required parameters are already
provided by the InfluxDB-Grafana plugin so the LMA collector gets them
from Hiera directly.
Change-Id: I627e8b5ae202783b24e31acb827915d91a3f8de5
This change adds collectd packages for CentOS. In addition, a few fixes
are needed to ensure successful deployment of the LMA collector on
CentOS platforms:
- Install collectd-dbi package on controller nodes.
- Modify Python scripts using subprocess to workaround issues with
Python 2.6.
- configure a valid database name for the MySQL plugin.
- set hasstatus and hasrestart parameters to true for all OpenStack
services otherwise Puppet fails to restart them.
Change-Id: I06891b069ba6047dfa40bcef7937b52964bda268
The collectd service collects metrics from many sources:
- System (like CPU, RAM, disk, network and so on)
- MySQL
- RabbitMQ
- OpenStack services
It sends the data to the LMA collector using its HTTP JSON output. The
LMA collector then decodes this input and injects it into the Heka
pipeline. Eventually the metrics will be sent to InfluxDB.
Note: until we have the InfluxDB-Grafana plugin ready, the InfluxDB parameters
are hidden in the Fuel UI.
Change-Id: I59577fcdc014be8d0f1d4824ef416afda3604506
This change enables the LMA collector to receive OpenStack notifications
and store them into ElasticSearch. Note that we configure an additional
notification topic ('lma_notifications') instead of high-jacking the
topic used by Ceilometer ('notifications').
This adds a new checkbox option in the UI to enable/disable the
notification collection (default value: disabled).
Change-Id: Ie934c244e7cf58f58487ed903aeb94af2e2e0495
The regular expression for validating the ElasticSearch address was
invalid which breaks the Settings page in the Fuel UI.
Change-Id: Icee075193cd3ee5b1a50b06d6f90c0a522147eb4
- Rename 'Environment name' to 'Environment label' to avoid confusion
with the Fuel environment's name.
- The ElasticSearch server is either specified by its node's name (when
deployed with the EK plugin in the same environment) or by its network
address.
Change-Id: Ie5c2b1d6522477324aebb4b36cd9fe0df36c5355
This is an import of the initial LMA PoC code. For now, it only covers
the collection of logs (notifications will be added in a subsequent
commit).
There's been a bit of rewrite to:
- decouple the Heka configuration from the LMA collector.
- run the Heka service as non-root when possible (Ubuntu only for now
due to file permission issues on CentOS [1]).
- adapt to version 0.9 of Heka.
[1] https://bugs.launchpad.net/fuel/+bug/1425954
Change-Id: I4472b49a25e18e06984b5b29bdce18f917137bc8