|Zuul f20f701048||4 months ago|
|doc||5 months ago|
|examples||8 months ago|
|lib/puppet||4 years ago|
|manifests||4 months ago|
|releasenotes||4 months ago|
|spec||4 months ago|
|.gitignore||1 year ago|
|.gitreview||1 year ago|
|.zuul.yaml||1 year ago|
|Gemfile||1 year ago|
|LICENSE||2 years ago|
|README.md||1 year ago|
|Rakefile||4 years ago|
|bindep.txt||2 years ago|
|metadata.json||4 months ago|
|setup.cfg||1 year ago|
|setup.py||3 years ago|
|tox.ini||5 months ago|
The watcher module is a part of OpenStack, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack and OpenStack community projects not part of the core software. The module itself is used to flexibly configure and manage the Watcher service for OpenStack.
The watcher module is a thorough attempt to make Puppet capable of managing the entirety of watcher. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the watcher module to assist in manipulation of configuration files.
What the watcher module affects
watcher is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install watcher with: puppet module install openstack/watcher
To utilize the watcher module’s functionality you will need to declare multiple resources.
watcher 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
For more information on writing and running beaker-rspec tests visit the documentation:
Developer documentation for the entire puppet-openstack project.