RETIRED, Fuel plugin to collect Logging Monitoring and Alerting metrics
Go to file
Éric Lemoine ccdba23158 Move Pacemaker/Corosync code out of lma_collector
This commit moves the Pacemaker/Corosync Puppet code from the
lma_collector module to the Fuel-specific base.pp manifest.

This involves the following changes:

* Fuel's "pacemaker_wrappers::service" define is now used in base.pp
  to configure the LMA service resource to using the "pacemaker"
  provider.

* To configure "pacemaker_wrappers::service" we need to know the Heka
  user. So to avoid hacks where we'd use private variables from the
  lma_collector and heka modules to determine the Heka user the
  lma_collector and heka modules are changed to make the Heka user
  configurable. For this the "heka" class "run_as_root" parameter is
  removed in favor of a "user" parameter.

* In other manifests we use a resource collector to make sure that
  the LMA service resource is not re-configured with the default
  provider. This part is a bit hackish, but we haven't been able to
  come up with a better way to address the issue.

Change-Id: I0ed0bddb245dc3a65b034e5caec14a65cfa908cb
Implements: blueprint lma-without-fuel
2016-01-29 12:50:57 +01:00
contrib Remove deployment_mode tag 2015-12-23 09:28:25 +01:00
deployment_scripts/puppet Move Pacemaker/Corosync code out of lma_collector 2016-01-29 12:50:57 +01:00
doc Merge "Set a default environment label if empty" 2016-01-28 15:16:54 +00:00
repositories Add a tox environment to build the plugin 2015-09-08 18:28:28 +02:00
specs s/ElasticSearch/Elasticsearch/ where appropriate 2015-04-23 15:50:06 +02:00
.gitignore Add a tox environment to build the plugin 2015-09-08 18:28:28 +02:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:24:08 +00:00
LICENSE Add appendix to LICENSE 2015-06-19 18:45:30 +02:00
README.md Remove readme info duplicates with the documentation 2015-11-16 17:42:30 +01:00
deployment_tasks.yaml Upgrade package_version to v3.0.0 2016-01-05 12:08:02 +01:00
environment_config.yaml Set a default environment label if empty 2016-01-28 11:27:24 +01:00
functions.sh Add Pacemaker Puppet modules 2015-08-14 17:07:04 +02:00
metadata.yaml Support liberty-8.0 version for Fuel 2016-01-18 14:13:32 +00:00
pre_build_hook Move Pacemaker/Corosync code out of lma_collector 2016-01-29 12:50:57 +01:00
tasks.yaml Monitor Elasticsearch cluster 2016-01-11 12:49:17 +00:00
test-requirements.txt Add a tox environment to build the plugin 2015-09-08 18:28:28 +02:00
tox.ini Add test plan to the project 2015-11-12 11:11:30 +01:00

README.md

The Logging, Monitoring and Alerting (LMA) Collector Plugin for Fuel

The LMA Collector Plugin for Fuel is used to install and configure the LMA Collector in OpenStack environments deployed by Fuel.

The LMA Collector is an advanced monitoring agent solution that should be installed on each of the OpenStack nodes you want to monitor.

Please check the LMA Collector Plugin Overview section of the plugin's documentation for additional details.

Release Notes

The release notes of the LMA Collector Plugin are provided in the Release Notes section of the plugin documentation.

Requirements

The LMA Collector Plugin requirements are defined in the Requirements section of the plugin documentation.

Known issues

The LMA Toolchain's related issues are listed on Launchpad.

Limitations

The LMA Collector Plugin limitations are described in the Limitations section of the plugin documentation.

Installation

The installation instructions of the LMA Collector Plugin are provided in the Installation section of the plugin documentation.

User Guide

Instructions for how to configure the plugin and the alarms are provided in the Configuration Guide and Alarms Configuration Guide of the plugin documentation.

Communication

The OpenStack Development Mailing List is the preferred way to communicate with the members of the project. Emails should be sent to openstack-dev@lists.openstack.org with the subject prefixed by [fuel][plugins][lma].

Reporting Bugs

Bugs should be filed against the LMA Toolchain project on Launchpad (not Github!).

Contributing

If you would like to contribute to the development of this plugin, you must follow the OpenStack development workflow instructions.

Patch reviews take place on the OpenStack Gerrit system.

Contributors