Move to opendev
|2 days ago|
|doc||1 year ago|
|examples||9 months ago|
|lib/puppet||1 year ago|
|manifests||1 month ago|
|releasenotes||1 month ago|
|spec||1 month ago|
|.gitignore||6 months ago|
|.gitreview||3 days ago|
|.zuul.yaml||7 months ago|
|Gemfile||2 days ago|
|LICENSE||1 year ago|
|README.md||2 days ago|
|Rakefile||3 years ago|
|bindep.txt||9 months ago|
|metadata.json||4 weeks ago|
|setup.cfg||4 months ago|
|setup.py||2 years ago|
|tox.ini||2 days ago|
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.
The vitrage puppet module is a thorough attempt to make Puppet capable of managing the entirety of vitrage.
What the vitrage module affects
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
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.
vitrage is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
This module has beaker-rspec tests
To run the tests on the default vagrant node:
bundle install bundle exec rake acceptance
Developer documentation for the entire puppet-openstack project.