2. Thomas Gelf
Module prototyping machine
Icinga Lead Architect
Principal Consultant @netways
Based in Nuremberg, Germany
Grown up in South Tyrol, Italian Alps
Apple-Fanboy. Real apples ;-)
15. Our kickstart wizard:
• Created our DB schema
• Connected to the Icinga 2 API
• Fetched Commands, Endpoints & Zones
16.
17. Manually, we:
• Created a first host template
• Created a host based on this template
• Deployed it with a single click
18. Internally, Director:
• Rendered the whole configuration
• Versioned and stored it to it‘s DB
• Shipped it to Icinga through the API
• Icinga validated the config & reloaded
• Director fetched it‘s startup log
28. Protocol
• Uses the Icinga 2 API (TLS, REST)
• Ships whole config, not single objects
• This is ways faster with lots of objects
• Could still ship partial changes
29. Communication Paths
• Director talks to your master node(s)
• Deploys always to the very same node
• Knows agents / satellites
• Controls them via config distribution
61. Director offers a REST API
• Simple and powerful
• Easy and intuitive to use
• Assists you with the trickiest part of the
job: detect and handle changes
66. Director is highly modular
Current Hooks:
DataType, ImportSource,
PropertyModifier, ShipConfigFiles
Even Directors own implementations extend and use them to
provide you nice real-world examples
69. Roadmap
https://dev.icinga.org
→ Projects Director Roadmap→ →
Releases
First release: 1.0 (released 03/24/2016)
Current stable: 1.1 (released 06/30/2016)
Next release: 1.2.0 (scheduled for 11/03/2016)
Fancy new things: don‘t fear the GIT master!