The Director aims to be your new favourite Icinga config deployment tool. Director is designed for those who want to automate their configuration deployment and those who want to grant their “point & click” users easy access to the configuration.
Go to file
Thomas Gelf 6c8213f4db DbObject: do not insert id=NULL, fails on pgsql 2015-06-23 13:05:02 +02:00
application GeneratedConfigTable: commit missing table 2015-06-18 11:03:18 +02:00
doc doc: add TODO list 2015-06-17 11:11:59 +02:00
library/Director DbObject: do not insert id=NULL, fails on pgsql 2015-06-23 13:05:02 +02:00
public/css show/activitylog: first simple visualization 2015-06-01 14:33:07 +02:00
schema Add PostgreSQL Schema that is fitting the MySQL Schema 2015-06-23 09:56:48 +02:00
.gitignore Add .gitignore file to the project 2015-04-24 16:57:54 +02:00
README.md README.md: code styling, once again 2015-06-01 17:05:15 +02:00
configuration.php GeneratedConfig: add simple "show" support 2015-06-18 10:54:44 +02:00
module.info module.info: fix typo 2015-04-21 14:29:11 +02:00

README.md

Icinga Director

This is going to be the new Icinga 2 config tool. Not for productional use. YET.

Installation

Create Icinga Director database

mysql -e "CREATE DATABASE director2;
   GRANT SELECT, INSERT, UPDATE, DELETE ON director.* TO director@localhost
   IDENTIFIED BY 'some-password';"

mysql director < schema/mysql.sql

Configure Icinga Web 2

In your web frontend please go to System / Configuration / Resources and create a new database resource pointing to your newly created database. Last but not least you have to tell the director module to use this newly created database resource.

Given that you named your resource directordb the config.ini for the module could look as follows:

[db]
resource = directordb

This file is to be found in <ICINGAWEB_CONFIGDIR>/modules/director/, where ICINGAWEB_CONFIGDIR usually means /etc/icingaweb2.