garethr / garethr-graphite

Puppet module for the Graphite monitoring tool

A Puppet module for managing the installation of Graphite.

Usage

Nice and simple, mainly because it's not yet very configurable.

include graphite

Configuration

If you want to run the web interface on a port other than 80 you can pass this in like so:

class { 'graphite':
  port => 9000,
}

This modules will install Python and the ensure the relevant python dependencies are available. If you would rather not have this module manage python then you can disable this feature like so:

class { 'graphite':
  manage_python = false,
}

Another Graphite module?

Graphite can be painfull to install and many blog posts and gists are dedicated to that fact. However it appears to have got easier with most of the components now available in the Python Package repository. All the other puppet modules I found either lacked support for Ubuntu/Debian, relied on an undocumented package or did a lot of wgetting.

Although I've only tested this module on Ubuntu it should work on other distros too, maybe with minor tweaks.

garethr-graphite's Issues

Invalid parameter template at config.pp:72

ubuntu server 12.04 x64, puppet 3.2.3
puppetlabs/apache module 2013-07-16 Release 0.8.0

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter template at /etc/puppet/modules/graphite/manifests/config.pp:72 on node ubuntu.localdomain

config.pp:72

  apache::vhost { 'graphite':
    priority => '10',
    port     => $port,
    template => 'graphite/virtualhost.conf',
    docroot  => '/opt/graphite/webapp',
    logroot  => '/opt/graphite/storage/log/webapp/',
  }

Install problems with 0.1.0, puppet 3.0.2, and Ubuntu 12.04.1

Installation fails with two problems:
execs require absolute paths to executables. install.pp needs /usr/bin/pip rather than 'pip', and config.pp needs /usr/bin/python.

Python.h missing, needed to add 'python-dev' to the package list in install.pp

Dependency on module to manage python

This module depends on footballradar/python, which makes it difficult to drop into a setup where a module to manage python already exists. Could this dependency be made optional? IMO the preferred way to go for interpreter/shared dependencies is to let the user bring it in on his/her own rather than bundling it.