OpenStack Vitrage Puppet Module
Go to file
ZhongShengping 433ca06749 Add 'openstack-db' tag to db-sync Exec resource
In order to make easy orchestration on all OpenStack db-sync, add this
tag so people can use this tag in composition layer.
A use case it to set some orchestration to make sure MySQL Galera is
ready before running any Exec with this tag.

Change-Id: I86811c7e3c38106eb9ed45180970344e060ed7e7
Closes-Bug: #1755102
(cherry picked from commit ca291e7ee9)
2018-10-12 01:40:13 +00:00
examples update example file with endpoint creation 2016-07-24 16:02:42 +03:00
lib/puppet Fix filename of api-paste.ini 2017-07-26 09:31:51 +08:00
manifests Add 'openstack-db' tag to db-sync Exec resource 2018-10-12 01:40:13 +00:00
releasenotes Add 'openstack-db' tag to db-sync Exec resource 2018-10-12 01:40:13 +00:00
spec Add 'openstack-db' tag to db-sync Exec resource 2018-10-12 01:40:13 +00:00
tests puppet-vitrage: Initial commit 2015-12-17 07:53:19 +02:00
.gitignore Add basic structure for ReNo 2016-10-07 14:58:43 +00:00
.gitreview Update .gitreview for stable/pike 2017-10-22 14:50:09 +00:00
.zuul.yaml import zuul job settings from project-config 2018-08-31 08:35:55 -04:00
Gemfile Update tox configuration 2017-05-17 09:50:26 -06:00
LICENSE puppet-vitrage: Initial commit 2015-12-17 07:53:19 +02:00
README.md Update to the latest address in README 2017-09-21 12:35:27 +08:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:35 -05:00
bindep.txt [pike] Add Puppet package to bindep, for module build 2017-12-18 21:35:30 +00:00
metadata.json Prepare for Pike post release 2018-01-18 00:41:17 +00:00
setup.cfg Update URLs in documents according to document migration 2017-07-14 08:54:58 +08:00
setup.py Add basic structure for ReNo 2016-10-07 14:58:43 +00:00
test-requirements.txt Update openstackdocstheme to latest version 2017-09-20 11:09:24 +08:00
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/pike 2017-10-24 04:27:38 +00:00

README.md

Team and repository tags

Team and repository tags

vitrage

Table of Contents

  1. Overview - What is the vitrage module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with vitrage
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Contributors - Those with commits

Overview

Vitrage module is an engine for organizing, analyzing and expanding OpenStack alarms & events, yielding insights regarding the Root Cause of problems and deducing the existence of problems before they are directly detected.

Module Description

The vitrage puppet module is a thorough attempt to make Puppet capable of managing the entirety of vitrage.

Setup

What the vitrage module affects

  • Vitrage, the Root Cause Analysis engine for organizing, analyzing and expanding OpenStack alarms & events for Openstack.

Installing vitrage

vitrage is not currently in Puppet Forge, but is anticipated to be added soon.  Once that happens, you'll be able to install vitrage with:
puppet module install openstack/vitrage

Beginning with vitrage

To utilize the vitrage module's functionality you will need to declare multiple resources. The following is a modified excerpt from the openstack module. This is not an exhaustive list of all the components needed, we recommend you consult and understand the openstack module and the core openstack documentation.

Implementation

vitrage

vitrage is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.

Limitations

  • None.

Beaker-Rspec

This module has beaker-rspec tests

To run the tests on the default vagrant node:

bundle install
bundle exec rake acceptance

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

0.0.1

  • Initial