fix typos
Change-Id: Ic354dc0f96996e0bb17c47541a7a21bc7bc9256f
This commit is contained in:
parent
2a9586b525
commit
96cacf6c37
@ -4,9 +4,9 @@
|
|||||||
|
|
||||||
http://creativecommons.org/licenses/by/3.0/legalcode
|
http://creativecommons.org/licenses/by/3.0/legalcode
|
||||||
|
|
||||||
================================
|
===================================
|
||||||
Vitrage System Health Visualization
|
Vitrage System Health Visualization
|
||||||
================================
|
===================================
|
||||||
|
|
||||||
https://blueprints.launchpad.net/vitrage-dashboard/+spec/ui-system-health-sunburst
|
https://blueprints.launchpad.net/vitrage-dashboard/+spec/ui-system-health-sunburst
|
||||||
|
|
||||||
|
@ -10,7 +10,7 @@ Evaluator Engine
|
|||||||
|
|
||||||
Launchpad blueprint:
|
Launchpad blueprint:
|
||||||
|
|
||||||
https://blueprints.launchpad.net/vitrage/+spec/evalutor-engine
|
https://blueprints.launchpad.net/vitrage/+spec/evaluator-engine
|
||||||
|
|
||||||
Vitrage Evaluator serves as workflow manager controlling the analysis and activation of templates and execution of template actions.
|
Vitrage Evaluator serves as workflow manager controlling the analysis and activation of templates and execution of template actions.
|
||||||
|
|
||||||
@ -40,7 +40,7 @@ Evaluator engine is the main core of Vitrage evaluator which responsible for man
|
|||||||
|
|
||||||
|
|
||||||
Problem description
|
Problem description
|
||||||
====================
|
===================
|
||||||
|
|
||||||
Vitrage requires a component that is responsible for managing and executing templates, which are the basis for the different algorithms used in Vitrage, such as RCA.
|
Vitrage requires a component that is responsible for managing and executing templates, which are the basis for the different algorithms used in Vitrage, such as RCA.
|
||||||
|
|
||||||
@ -68,7 +68,7 @@ None
|
|||||||
|
|
||||||
Data model impact
|
Data model impact
|
||||||
-----------------
|
-----------------
|
||||||
The templates are saved in NetworkX graph-base in memeory DB.
|
The templates are saved in NetworkX graph-base in memory DB.
|
||||||
|
|
||||||
REST API impact
|
REST API impact
|
||||||
---------------
|
---------------
|
||||||
|
@ -113,7 +113,13 @@ Collector plugin
|
|||||||
- samples OS services, Nagios, etc.
|
- samples OS services, Nagios, etc.
|
||||||
- via each OS service REST API
|
- via each OS service REST API
|
||||||
- method of collection:
|
- method of collection:
|
||||||
retrieve OS service elements list. For the purposes of:change notifications - as part of the periodic collection of the latest snapshotwe'd use this method of collection against OS services which doesn't propagates change notification.run on its own collection subprocesses how to discover a changeonce a snapshot is collected, we'd like to know which entity was changed from the latest time a snapshot was takenin order to enable this, we'd keep a baseline - a data structure which contains for each OS service entity (such as a vm instance), its ID + it latest collection timestamp or a hash which represents its latests state.by comparing the latest snapshot of elements against the baseline, we'd know for which entity we'd like to propagate a notification for.collect deltas for services which reveals this functionalityfor the purposes of change notificationsthis is the easy case, where change notifications are simply passed on to whoever registered for them
|
retrieve OS service elements list. For the purposes of:change
|
||||||
|
notifications - as part of the periodic collection of the latest snapshot
|
||||||
|
we'd use this method of collection against OS services which doesn't
|
||||||
|
propagates change notification.run on its own collection subprocesses
|
||||||
|
how to discover a change once a snapshot is collected, we'd like to know
|
||||||
|
which entity was changed from the latest time a snapshot was taken in order
|
||||||
|
to enable this, we'd keep a baseline - a data structure which contains for each OS service entity (such as a vm instance), its ID + it latest collection timestamp or a hash which represents its latest state.by comparing the latest snapshot of elements against the baseline, we'd know for which entity we'd like to propagate a notification for.collect deltas for services which reveals this functionality for the purposes of change notifications this is the easy case, where change notifications are simply passed on to whoever registered for them
|
||||||
- deployment - as a library
|
- deployment - as a library
|
||||||
|
|
||||||
consumer flow
|
consumer flow
|
||||||
|
@ -18,14 +18,14 @@ Template Validator ensures that a new template is correct. Meaning, it conforms
|
|||||||
|
|
||||||
|
|
||||||
Problem description
|
Problem description
|
||||||
====================
|
===================
|
||||||
|
|
||||||
Templates do not always meet the Vitrage Template Standard. For example, unsupported action, invalid alarm name, incorrect graph template and etc.
|
Templates do not always meet the Vitrage Template Standard. For example, unsupported action, invalid alarm name, incorrect graph template and etc.
|
||||||
|
|
||||||
Proposed change
|
Proposed change
|
||||||
===============
|
===============
|
||||||
|
|
||||||
Tamplate validator is a part of Vitrage Evaluator. It receives a template, runs over it and checks its correctness.
|
Template validator is a part of Vitrage Evaluator. It receives a template, runs over it and checks its correctness.
|
||||||
If the template is valid, it notify the Evaluator Engine which inserts the template into the template DB. Otherwise, insertion is failed.
|
If the template is valid, it notify the Evaluator Engine which inserts the template into the template DB. Otherwise, insertion is failed.
|
||||||
|
|
||||||
Alternatives
|
Alternatives
|
||||||
|
Loading…
Reference in New Issue
Block a user