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
When `action_type` is `mark down`, the target only can be a nova.host,
not instance
Change-Id: I8fdd6eca07b7bff9ed329c020ff6107635a43358
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
use `name` not `id` in template metadate section
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
Change-Id: I717a0ae790a2d23f2df21d6d3a8e89be98646d1a
1. Removed redundant method from drivers -
get_update_method as it is accessible via
configuration and there's no need for adding
such a function.
2. Fixed zabbix get_all bug, zabbix alarms key is
now comprised of the alarm's host name, raw text
description and the trigger id.
Change-Id: I2f885a1f4e12f69db15a819b62359b3290054364
Each datasource had a configurable field
update_method in the vitrage configuration file
where you can set it to update via:
none: don't update i.e. update only via the
periodic changes
pull: updates via polling the datasource every
configurable [changes_interval] seconds
push: updates via the datasource's push notifications
Change-Id: Iab884a357ae7235e137600c95b0a23052cdee064
Closes-Bug: #1606834