openstack/puppet-vitrage
Code Issues Proposed changes
OpenStack Vitrage Puppet Module
227 Commits 9 Branches 74 Tags 3.2 MiB
Ruby 50.4%
Puppet 43.2%
Python 6.4%
89ca7a041c
Go to file
ZhongShengping 89ca7a041c Service_token_roles_required missing in the server config file 
Service_token_roles_required missing in the server config file which
allows backwards compatibility to ensure that the service tokens are
compared against a list of possible roles for validity.

Change-Id: Ie750c55189323d0cc1c50d00141e35a5a43aa8d0
Closes-Bug: 1778198
2019-03-04 06:29:10 +00:00
doc Follow the new PTI for document build 2018-02-28 14:46:18 +08:00
examples Replace port 35357 with 5000 2018-07-18 10:31:43 +02:00
lib/puppet Fix filename of api-paste.ini 2017-07-26 09:31:51 +08:00
manifests Service_token_roles_required missing in the server config file 2019-03-04 06:29:10 +00:00
releasenotes Service_token_roles_required missing in the server config file 2019-03-04 06:29:10 +00:00
spec Service_token_roles_required missing in the server config file 2019-03-04 06:29:10 +00:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:25 +08:00
.gitreview Added .gitreview 2015-12-09 10:12:41 +00:00
.zuul.yaml switch documentation job to new PTI 2018-08-31 08:24:47 -04:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:20:33 +02:00
Gemfile Load puppet-openstack_spec_helper locally during tests 2018-02-12 10:53:40 +08:00
LICENSE Update LICENSE 2018-04-06 20:15:16 +08:00
metadata.json Merge "Use puppet 4 compatible mysql functions" 2019-02-11 21:45:43 +00:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:35 -05:00
README.md Change wiki to docs 2019-02-13 10:31:10 +08:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-02 20:14:28 +01:00
setup.py Add basic structure for ReNo 2016-10-07 14:58:43 +00:00
tox.ini Update min tox version to 2.0 2018-10-16 11:40:19 +08: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
  8. Release Notes - Release notes for the project
  9. Repository - The project source code repository

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

Repository