c9ea8ea4a1
In Pike OpenStack documentation is changed in a way that the project repos contain most of the documentation material [1]. This affcects how the doc folder shall be strucutred inside the project repo. With this change I align the install guide to the new structure and correct the warnings during the document generation. The overall work is tracked in [2]. [1]: http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html [2]: https://etherpad.openstack.org/p/doc-migration-tracking Change-Id: Ib5400247d2ba5f8dac80ef68a43d06868bd42f1c Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454 Signed-off-by: csatari <gergely.csatari@nokia.com>
86 lines
2.6 KiB
ReStructuredText
86 lines
2.6 KiB
ReStructuredText
.. vitrage documentation master file, created by
|
|
sphinx-quickstart on Tue Jul 9 22:26:36 2013.
|
|
You can adapt this file completely to your liking, but it should at least
|
|
contain the root `toctree` directive.
|
|
|
|
Welcome to Vitrage documentation!
|
|
=================================
|
|
|
|
Vitrage is the OpenStack RCA (Root Cause Analysis) service for organizing,
|
|
analyzing and expanding OpenStack alarms & events, yielding insights regarding
|
|
the root cause of problems and deducing their existence before they are
|
|
directly detected.
|
|
|
|
|
|
High Level Functionality
|
|
------------------------
|
|
|
|
* Physical-to-Virtual entities mapping
|
|
|
|
* Deduced alarms and states (i.e., raising an alarm or modifying a state based on analysis of the system, instead of direct monitoring)
|
|
|
|
* Root Cause Analysis (RCA) for alarms/events
|
|
|
|
* Horizon plugin for the above features
|
|
|
|
High Level Architecture
|
|
-----------------------
|
|
|
|
.. image:: ./images/vitrage_graph_architecture.png
|
|
:width: 100%
|
|
:align: center
|
|
|
|
**Vitrage Data Sources** are responsible for importing information from
|
|
different sources, regarding the state of the system. This includes information
|
|
regarding resources (physical, virtual, and applications) and alarms.
|
|
The information is then processed into the Vitrage Graph.
|
|
Currently Vitrage supports OpenStack datasources like Nova, Cinder, Neutron,
|
|
Heat and Aodh, as well as external monitors like Nagios, Zabbix and collectd.
|
|
|
|
**Vitrage Graph** holds the information collected by the Data Sources, as well
|
|
as their inter-relations. Additionally, it implements a collection of basic
|
|
graph algorithms that are used by the Vitrage Evaluator (e.g., sub-matching,
|
|
BFS, DFS etc).
|
|
|
|
**Vitrage Evaluator** coordinates the analysis of (changes to) the Vitrage
|
|
Graph and processes the results of this analysis. It is responsible for
|
|
executing different kind of template-based actions in Vitrage, such as to add
|
|
an RCA (Root Cause Analysis) relationship between alarms, raise a deduced alarm
|
|
or set a deduced state.
|
|
|
|
**Vitrage Notifiers** can be used to notify external systems of Vitrage alarms
|
|
and states. Currently Vitrage has an Aodh notifier for raising Vitrage alarms
|
|
in Aodh, and a Nova notifier for marking that the host is down.
|
|
|
|
Installation Guide
|
|
------------------
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
install/index
|
|
|
|
Developer Guide
|
|
---------------
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
vitrage-first_steps
|
|
vitrage-api
|
|
vitrage-template-format
|
|
installation-and-configuration
|
|
|
|
Design Documents
|
|
----------------
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
vitrage-graph-design
|
|
scenario-evaluator
|
|
vitrage-use-cases
|
|
add-new-datasource
|
|
not_operator_support
|
|
templates-loading
|
|
vitrage-ha-and-history-vision
|