Jump to: navigation, search

Difference between revisions of "Vitrage/Blueprints/entitygraph"

(Example)
(Example)
Line 20: Line 20:
 
==Example==
 
==Example==
 
The following demonstrate several possible entity graphs that might be maintained by Vitrage:
 
The following demonstrate several possible entity graphs that might be maintained by Vitrage:
[[File:EntityGraphExample.png|1000px|frameless]]
+
[[File:EntityGraph.png|1000px|frameless]]

Revision as of 13:51, 12 October 2015

Introduction

Vitrage will maintain an entity graph representing relationships between entities, as well as relationships between entities and their alarms. Relationship types can include physical relationships (such as the connection of a host to a physical switch), virtual relationships (such as the relationship of a host to it's hosted VMs), and logical/analytical relationships (such as a "alarm A causes alarm B" relationship).

Motivation & Design Goals

In order to provide a flexible model for dependency analysis and processing, we maintain a graph representing (a portion of) the system state. With such a graph in place, we can search for patterns in the graph as part of many features, such as Root Cause Analysis and generating Deduced Alerts.

Supported Entity Types

  • Cloud Node
  • Cloud Node Zone
  • Host
  • Stack
  • Machine
  • Storage
  • Network
  • Switch
  • Ephemeral Storage
  • Container
  • Service

Example

The following demonstrate several possible entity graphs that might be maintained by Vitrage: EntityGraph.png