Fix a cycle in graph of tasks
This patch removes a dependency that causes a cycle in the graph of tasks in MOS 8. The cycle was <custom>-netconfig -> hosts -> cluster -> virtual_ips -> <custom>-netconfig Change-Id: I80f88ebec732c2e95bfa5c271ffb9c35ad0a1827
|2 years ago|
|deployment_scripts/puppet||2 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||2 years ago|
|environment_config.yaml||2 years ago|
|functions.sh||3 years ago|
|metadata.yaml||3 years ago|
|network_roles.yaml||3 years ago|
|node_roles.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|
|uninstall.sh||3 years ago|
|volumes.yaml||3 years ago|
The StackLight Elasticsearch-Kibana Plugin for Fuel is used to install and configure Elasticsearch and Kibana which collectively provide access to the logs and notifications analytics of Mirantis OpenStack. The logs and the notifications of Mirantis OpenStack are collected and processed by the StackLight Collector.
Please go to the Elasticsearch-Kibana Plugin Overview to getting started.
A summary description of the new features are provided in the Release Notes section of the plugin documentation.
The requirements are defined in the Requirements section of the plugin documentation.
All known issues are listed on Launchpad.
All known limitations are described in the Limitations section of the plugin documentation.
The installation instructions are provided in the Installation section of the plugin documentation.
Instructions for how to configure and use the Elasticsearch-Kibana Plugin are provided in the User Guide 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
email@example.com 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 within OpenStack Gerrit system.