OpenStack Gnocchi Puppet Module
Go to file
Doug Hellmann 3d9dd7ec22 import zuul job settings from project-config
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: I04646ead8e19d3b0da9a89e261123b2c4c7fb83d
Story: #2002586
Task: #24325
2018-08-31 08:17:58 -04:00
doc Follow the new PTI for document build 2018-02-28 14:42:11 +08:00
examples Merge "Remove deprecated parameters" 2018-06-13 14:19:47 +00:00
lib/puppet Make providers use auth_url for authentication 2018-08-03 11:52:06 +02:00
manifests Add CORS config support 2018-06-15 15:39:09 -04:00
releasenotes Update reno for stable/rocky 2018-08-20 18:35:49 +00:00
spec modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:18:06 +02:00
.gitignore Update .gitignore 2018-04-11 08:55:18 +08:00
.gitreview Update .gitreview file for project rename 2015-06-12 23:12:30 +00:00
.zuul.yaml import zuul job settings from project-config 2018-08-31 08:17:58 -04:00
CHANGELOG.md Update and replace http with https for doc links 2017-09-20 19:00:52 -07:00
Gemfile Load puppet-openstack_spec_helper locally during tests 2018-02-12 10:53:35 +08:00
LICENSE First commit with basic structure 2014-12-29 13:46:13 +01:00
README.md Remove the unnecessay _ 2018-07-25 11:14:31 +08:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-28 04:08:48 +00:00
bindep.txt Add Puppet package to bindep, for module build 2017-10-27 13:12:41 -07:00
metadata.json Remove PE requirement from metadata.json 2018-08-16 23:18:18 +02:00
setup.cfg Update URLs in documents according to document migration 2017-07-14 11:51:22 +08:00
setup.py Add basic structure for ReNo 2016-03-14 08:28:29 -04:00
tox.ini fix tox python3 overrides 2018-06-08 14:23:32 +08:00

README.md

Team and repository tags

Team and repository tags

puppet-gnocchi

Table of Contents

  1. Overview - What is the gnocchi module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with gnocchi
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. 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).

Installing gnocchi

puppet module install openstack/gnocchi

Implementation

gnocchi

gnocchi is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.

Types

gnocchi_config

The gnocchi_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/gnocchi/gnocchi.conf file.

gnocchi_config { 'DEFAULT/debug' :
  value => true,
}

This will write debug=true in the [DEFAULT] section.

name

Section/setting name to manage from gnocchi.conf

value

The value of the setting to be defined.

secret

Whether to hide the value from Puppet logs. Defaults to false.

ensure_absent_val

If value is equal to ensure_absent_val then the resource will behave as if ensure => absent was specified. Defaults to <SERVICE DEFAULT>

Limitations

Load balancing Gnocchi MySQL with HAProxy

Issue

MySQL client/server interaction causes an issue where the HAProxy server will keep a connection in TIME_WAIT. When Gnocchi is processing data it will generate a lot of connections to MySQL and exhaust all available tcp ports for a given IP address. If the HAProxy VIP is shared with other components, this can cause them to be unavailable too. Tuning of HAProxy instance is essential when using Gnocchi with a MySQL behind an HAProxy.

The sysctl parameters need tuning.

  • net.ipv4.tcp_tw_reuse = 1
  • net.core.somaxconn = 4096
  • net.ipv4.tcp_max_syn_backlog = 60000

Additionally, HAProxy can be configured to use different source IP addresses on each backend to help further mitigate the issue.

Development

Developer documentation for the entire puppet-openstack project.

Contributors

The github contributor graph.

Release Notes

Repository