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
Alexander Fuhr f1c3f9025b Add imports support for UserGroup 2015-06-29 11:02:30 +02:00
application Add imports support for UserGroup 2015-06-29 11:02:30 +02:00
doc doc: add TODO list 2015-06-17 11:11:59 +02:00
library/Director Add imports support for UserGroup 2015-06-29 11:02:30 +02:00
public/css show/activitylog: first simple visualization 2015-06-01 14:33:07 +02:00
schema Add imports support for UserGroup 2015-06-29 11:02:30 +02:00
.gitignore Add .gitignore file to the project 2015-04-24 16:57:54 +02:00
README.md Test commit overload 2015-06-26 14:30:57 +02:00
configuration.php config: add tabs, less menu items 2015-06-29 10:13:39 +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:

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

mysql director < schema/mysql.sql

PostgreSQL:

CREATE DATABASE director WITH ENCODING 'UTF8';
CREATE USER director WITH PASSWORD 'some-password';
GRANT ALL PRIVILEGES ON DATABASE director TO director;

psql director < schema/pgsql.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.