Avoid forks when starting hekad
We must avoid to fork process when starting the Heka daemon because if we kill the wrapper, the Heka daemon is detached and re-attach to the init process. This can create several Heka daemon. To avoid this we need to use exec and avoid the usage of sudo. Fixes-bug: #1561109 (cherry picked from commit
|3 years ago|
|contrib||4 years ago|
|deployment_scripts/puppet||3 years ago|
|doc||3 years ago|
|repositories||3 years ago|
|specs||4 years ago|
|.gitignore||3 years ago|
|.gitreview||3 years ago|
|LICENSE||4 years ago|
|README.md||3 years ago|
|deployment_tasks.yaml||3 years ago|
|environment_config.yaml||3 years ago|
|functions.sh||3 years ago|
|metadata.yaml||3 years ago|
|pre_build_hook||3 years ago|
|tasks.yaml||3 years ago|
|test-requirements.txt||3 years ago|
|tox.ini||3 years ago|
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.
The release notes of the LMA Collector Plugin are provided in the Release Notes section of the plugin documentation.
The LMA Collector Plugin requirements are defined in the Requirements section of the plugin documentation.
The LMA Toolchain’s related issues are listed on Launchpad.
The LMA Collector Plugin limitations are described in the Limitations section of the plugin documentation.
The installation instructions of the LMA Collector Plugin are provided in the Installation section of the plugin documentation.
The OpenStack Development Mailing List is the preferred way to communicate
with the members of the project.
Emails should be sent to
firstname.lastname@example.org with the subject
Bugs should be filed against the LMA Toolchain project on Launchpad (not Github!).
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.