opscode-monitoring Omnibus project

This project creates full-stack platform-specific packages for opscode-monitoring!

It contains estatsd and graphite (currently only the carbon collector) already configured to gather data from either an Enterprise Chef or Open Source Chef Server.

Configuration

All configuration should be done in /etc/opscode-monitoring/opscode-monitoring.rb. By default, both estatsd and carbon are started.

estatsd

To disable estatsd, set

    estatsd['enable'] = false

If you wish to use a graphite server on a different host, you can set the graphite_host and graphite_port` attributes:

    estatsd['graphite_host'] = 'graphite.example.com'
    estatsd['graphite_port'] = 12003

carbon

To disable carbon, set

    carbon['enable'] = false

Installation

You must have a sane Ruby 1.9+ environment with Bundler installed. Ensure all the required gems are installed:

$ bundle install --binstubs

Usage

Build

You create a platform-specific package using the build project command:

$ bin/omnibus build opscode-monitoring

The platform/architecture type of the package created will match the platform where the build project command is invoked. For example, running this command on a MacBook Pro will generate a Mac OS X package. After the build completes packages will be available in the pkg/ folder.

Clean

You can clean up all temporary files generated during the build process with the clean command:

$ bin/omnibus clean opscode-monitoring

Adding the --purge purge option removes ALL files generated during the build including the project install directory (/opt/opscode-monitoring) and the package cache directory (/var/cache/omnibus/pkg):

$ bin/omnibus clean opscode-monitoring --purge

Help

Full help for the Omnibus command line interface can be accessed with the help command:

$ bin/omnibus help

Kitchen-based Build Environment

Every Omnibus project ships will a project-specific Berksfile that will allow you to build your omnibus projects on all of the projects listed in the .kitchen.yml. You can add/remove additional platforms as needed by changing the list found in the .kitchen.yml platforms YAML stanza.

This build environment is designed to get you up-and-running quickly. However, there is nothing that restricts you to building on other platforms. Simply use the omnibus cookbook to setup your desired platform and execute the build steps listed above.

The default build environment requires Test Kitchen and VirtualBox for local development. Test Kitchen also exposes the ability to provision instances using various cloud providers like AWS, DigitalOcean, or OpenStack. For more information, please see the Test Kitchen documentation.

Once you have tweaked your .kitchen.yml (or .kitchen.local.yml) to your liking, you can bring up an individual build environment using the kitchen command.

$ bin/kitchen converge ubuntu-12.04

Then login to the instance and build the project as described in the Usage section:

$ bundle exec kitchen login ubuntu-12.04
[vagrant@ubuntu...] $ cd opscode-monitoring
[vagrant@ubuntu...] $ bundle install
[vagrant@ubuntu...] $ ...
[vagrant@ubuntu...] $ bin/omnibus build opscode-monitoring

For a complete list of all commands and platforms, run kitchen list or kitchen help.