b3e503c3e0
In order to be able to take an action after all the packages of the module have been installed/updated or all the services have been started/restarted, we set a 'gnocchi-package' and 'gnocchi-service' tag for each package and service of this module. At the moment, there is a generic openstack tag that is not specific enough if one wants to take action upon a single module change. Use case : If an action needs to be taken after all the packages have been installed or updated : Package <| tag == 'gnocchi-package' |> -> X Change-Id: I90902e01bd095e1b0f6a2944ceedfc53de6f7b01 |
||
---|---|---|
examples | ||
lib/puppet | ||
manifests | ||
spec | ||
.fixtures.yml | ||
.gitignore | ||
.gitreview | ||
Gemfile | ||
LICENSE | ||
README.md | ||
Rakefile | ||
metadata.json |
README.md
puppet-gnocchi
Table of Contents
- Overview - What is the gnocchi module?
- Module Description - What does the module do?
- Setup - The basics of getting started with gnocchi
- 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
Overview
The gnocchi 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 as part of the core software. The module itself is used to flexibly configure and manage the management service for Openstack.
Module Description
Setup
What the gnocchi module affects:
- gnocchi, the HTTP API to store metrics and index resources for OpenStack (OpenStack Datapoint Service).
Implementation
gnocchi
gnocchi is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
Development
Developer documentation for the entire puppet-openstack project.
Contributors
The github contributor graph.