openstack/vitrage-specs
Code Issues Proposed changes

misc typos

Browse Source 
spelling mistakes
rephrasing

Change-Id: Ia5ead2cb74aa26943f052c93e8201443b9ac353b
This commit is contained in:
Eyal Bar-Ilan 2015-11-10 14:21:11 +02:00 committed by Eyal
parent ab3d39ab0b
commit eb2af28e91
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/mitaka/vitrage-cli.rst
View File

@ -35,7 +35,7 @@ on the Vitrage API.
Problem description
===================
As a user I would like to be able to see the root cause of any alerts or events in my system.
As a user I would like to be able to see the root cause of any alerts or events in the system.
A command line utility will be used to communicate with Vitrage API service.
The CLI will 3 types of commands:

4
specs/mitaka/vitrage-resource-processor.rst
View File

@ -15,14 +15,14 @@ When Vitrage initializes we need to create the Entity Graph on which the Vitrage
Problem description
===================
Vitrage doesn’t have a full Entity Graph of the resources and their state when it initializes.
Vitrage does not have a full Entity Graph of the resources and their state when it initializes.
Vitrage needs to be consistent with the updated and new resources.
Proposed change
===============
When Vitrage initializes we need to build the up to date entity graph, so we can run the different algorithms on it and perform the required actions. To perform we require the full resources list from the synchronizer.
In order for the Entity Graph to be constructed, it will need updates on changes in the cloud (e.g., machine creation/termination), and guidance on how resources should be linked to each other (e.g., a virual machine resides on a physical host, which in turn belongs to an availability zone, etc.). For this purpose, each synchronizer will also update a configuration file - the entity graph template - which specifies for each resource what and how to locate the specific resources to link to.
In order for the Entity Graph to be constructed, it will need updates on changes in the cloud (e.g., machine creation/termination), and guidance on how resources should be linked to each other (e.g., a virtual machine resides on a physical host, which in turn belongs to an availability zone, etc.). For this purpose, each synchronizer will also update a configuration file - the entity graph template - which specifies for each resource what and how to locate the specific resources to link to.
Alternatives
------------