8b92b0fc18
Depends-On: https://review.opendev.org/#/c/740601/ Change-Id: If26b4030ae363fbf24ac74fd519670b67e42d6ca
2.7 KiB
Team and repository tags
watcher
Table of Contents
- Overview - What is the watcher module?
- Module Description - What does the module do?
- Setup - The basics of getting started with watcher
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - Those with commits
- Release Notes - Release notes for the project
- Repository - The project source code repository
Overview
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.
Module Description
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.
Setup
What the watcher module affects
- Watcher, the Watcher service for OpenStack.
Installing watcher
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
Beginning with watcher
To utilize the watcher module's functionality you will need to declare multiple resources.
Implementation
watcher
watcher is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
- All the watcher types use the CLI tools and so need to be ran on the watcher node.
Development
Developer documentation for the entire puppet-openstack project.