doc | ||
manifests | ||
templates | ||
.gitignore | ||
.mailmap | ||
AUTHORS | ||
CHANGELOG.md | ||
COPYING | ||
metadata.json | ||
README.md |
puppet-icinga2
Table of Contents
- Overview - What is the Icinga 2 module?
- Module Description - What does the module do?
- Setup - The basics of getting started with the Icinga 2 module
- Usage - How to use the module for various tasks
- Reference - The classes and defined types available in this module
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - List of module contributors
Overview
This module installs and configures the Icinga 2 monitoring system. It can also install and configure NRPE on client systems that are being monitored by an Icinga 2 server.
Module Description
Coming soon...
Setup
This module should be used with Puppet 3.6 or later. It may work with earlier versions of Puppet 3 but it has not been tested.
This module requires Facter 2.2 or later, specifically because it uses the operatingsystemmajrelease
fact.
This module requires the Puppet Labs stdlib module.
For Ubuntu systems, this module requires the Puppet Labs apt module.
On EL-based systems (CentOS, Red Hat Enterprise Linux, Fedora, etc.), the EPEL package repository is required.
If you would like to use the icinga2::object
defined types as exported resources, you'll need to have your Puppet master set up with PuppetDB. See the Puppet Labs documentation for more info: Docs: PuppetDB
###Server requirements
Icinga 2 requires either a MySQL or a Postgres database.
Currently, this module does not set up any databases. You'll have to create one before installing Icinga 2 via the module.
If you would like to set up your own database, either of the Puppet Labs MySQL or Postgres modules can be used.
The example below shows the Puppet Labs Postgres module being used to install Postgres and create a database and database user for Icinga 2:
class { 'postgresql::server': } postgresql::server::db { 'icinga2_data': user => 'icinga2', password => postgresql_password('icinga2', 'password'), }
For production use, you'll probably want to get the database password via a Hiera lookup so the password isn't sitting in your site manifests in plain text.
Usage
Coming soon...
Reference
Classes:
Coming soon...
Defined types:
Coming soon...
Limitations
Coming soon...
Development
Coming soon...
Contributors
Coming soon...