Updating the policies for this project should only refresh the services that reads it. Change-Id: I7dc9f4a9849043624359eb97775af20d1885103a (cherry picked from commit
Team and repository tags
Table of Contents
- Overview - What is the AODH module?
- Module Description - What does the module do?
- Setup - The basics of getting started with AODH
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Repository - The project source code repository
- Contributors - Those with commits
- Release Notes - Release notes for the project
The AODH 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 its self is used to flexibly configure and manage the Alarming service for OpenStack.
The AODH module is a thorough attempt to make Puppet capable of managing the entirety of AODH. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the AODH module to assist in manipulation of configuration files.
What the AODH module affects
- AODH, the Alarming service for OpenStack.
puppet module install openstack/aodh
Beginning with AODH
To utilize the AODH module's functionality you will need to declare multiple resources. This is not an exhaustive list of all the components needed, we recommend you consult and understand the core OpenStack documentation.
AODH is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
- All the AODH types use the CLI tools and so need to be ran on the AODH node.
Developer documentation for the entire puppet-openstack project.