openstack/puppet-vitrage
Code Issues Proposed changes
OpenStack Vitrage Puppet Module
384 Commits 9 Branches 74 Tags 3.2 MiB
Ruby 50.4%
Puppet 43.2%
Python 6.4%
acb97eff1e
Go to file
Takashi Kajinami acb97eff1e Avoid hard-coding OS user/group in each manifest 
and replace hard-codes by definition in params.pp .

Change-Id: I718e97030f67ab257295de6db04696726efd4f5f
2022-02-21 01:51:16 +09:00
doc Update openstackdocstheme to the latest version 2021-09-29 16:06:51 +08:00
examples Convert all class usage to relative names 2019-12-08 23:24:49 +01:00
lib/puppet Merge "Add support for MultiStrOpt" 2022-02-15 10:19:52 +00:00
manifests Avoid hard-coding OS user/group in each manifest 2022-02-21 01:51:16 +09:00
releasenotes Allow customizing separator for api-paste.ini 2022-02-13 01:39:04 +09:00
spec Merge "Do not define service resource when service management is disabled" 2022-02-15 10:29:41 +00:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:25 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:34:07 +00:00
.zuul.yaml Add Puppet Litmus 2020-08-31 22:02:52 +02:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:20:33 +02:00
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:54:56 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-30 23:07:38 +02:00
LICENSE Update LICENSE 2018-04-06 20:15:16 +08:00
metadata.json Prepare Yoga M2 2022-01-07 14:23:38 +00:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:35 -05:00
README.md Add Puppet Litmus 2020-08-31 22:02:52 +02:00
setup.cfg Add information technology in the setup.cfg 2021-10-01 06:54:50 +08:00
setup.py Delete useless code for setup.py 2021-09-30 13:38:33 +08:00
tox.ini Stop configuring install_command in tox. 2021-09-29 18:21:46 +09: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.

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

Repository