- Added missing documentation of Nova notifier
- Moved osprofiler doc under contributor folder
- Marked the static-physical datasource as obsolete
- Removed a link to Aodh notifier (the document was deleted, as it was just a POC)
Depends-On: Ifcde995130486c859e6a9ce23e47a89910187732
Change-Id: Ib2b7880d65d4c6edd7cfd1f831da9da7af5e114c
Two new validations are added:
1. A condition can not be only "negative". For example, instead of: "not alarm_on_instance" one should use "instance and not_alarm_on_instance"
2. There should be an entity that is common to all parts of an "or" condition. For example, this is illegal: "alarm1_on_host or alarm2_on_instance"
Change-Id: I209155ade48ba740642670891c11aeef0868197c
Implements: blueprint support-external-actions
The following will be done in the *next* patches:
* Implementation of the ExternalExecute step
* Implementation of the Mistral notifier
* Documentation of the new action
Change-Id: I571861149e51bca85cb024969b8595ae85655b25
Implements: blueprint integration-with-mistral
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>
I wrote it here and not as a blueprint, since it is a very wide scope and several blueprints can be created in the future for supporting this vision.
Change-Id: I9d32d7e2a45a146c5923604b0591f8a7d609f616
Rename vitrage properties to start with the vitrage prefix
so it will be easier work with and to recognize.
Change-Id: Ia8afaa1a13897927984a9c8d8d9b85343ef69c01
Fix a broken link for 'Vitrage-dashboard manual installation'
in the vitrage installation doc.
Change-Id: I5aa224db7c0e2adae51708fcac464ea82942a4c7
Closes-Bug: #1696055
TemplateData is refactored to make it possible
- split SubGraph and ScenarioData from TemplateData
- build entity index and relationship index in TemplateData
- delay variable extraction to subgraph build
- simplify the process of adding scenario to repository
Implement: blueprint entity-equivalence
Change-Id: I7192e3a82880dc3c3995000c029af4e0aabd8d6c
- add strict tests in template data verification to help understand
- add traceback in scenario evaluator design document
- rename example templates with a more meaningful name
Change-Id: Ie5a9c34fcd6fdac3bf9d4552a0c92fb569c075fc
- Beautify, re-indent, format code in a lot of doc files
- Use relative URLs instead of absolute github URLs
- Some absolute github urls are not corrected yet:
+ URL for enabling vitrage in devstack
+ URL for enabling vitrage in horizon
- Update year number in doc/source/config.py from 2013 to 2016
My thought: We should have a blueprint
to create more concise and easy to access like other project
(nova: http://docs.openstack.org/developer/nova/).
Currently, that site for vitrage has not existed yet.
Notes: Change github URLs to relative URLs
(or absolute URLs in docs.openstack.org/developers)
will not work correctly
if we do not have official documentation site.
Hence, other people cannot follow the link to html page
if they read vitrage documentation in github mirror.
Change-Id: Ifff8355c7e5291f68a7592d1617644053d790d5e
Install devstack with vitrage before install nagios via omd
to avoid apache2 pid issue.
Reason:
- omd manages apache2 by itself
- horizon and keystone are sites of apache2
- stop apache2 via service will fail beacause of omd
When using devstack, remember to stop omd apache2's sites
Change-Id: If8c1dd9dfcb5ff7819db10c1cfa3d67c021a2feb
Closes-Bug: #1629811
- Add notice about docker image
- Add notice to install oslo.messaging, oslo.config
- Hint about default devstack rabbitmq username and password
- Correct the order of zabbix configure action
- Add url to create triggers in zabbix
- Add vitrage configuration section for zabbix
+ Data sources in vitrage.conf
+ Zabbix section in vitrage.conf
+ Mapping resource name and resource type in zabbix_conf.yaml
Change-Id: I1d1ffcdf1f8cbdd9c57e0f92eb08c866533e1517