3. Motivation for a config tool
• Make config easy for the end user
• Offer interfaces to other tools
• Avoid writing config files
• Import config from everywhere
4. The hard parts
• Support for a config DSL
• Enable anyone to use it
• Keep it simple
• Don’t restrict the user too much
33. • Keep track of changes
• Render Icinga 2 configuration
• Store configuration history
• Push configuration to the Icinga 2 API
• Verify deployment status
51. Integrations
• REST API for object management
• Icingacli as command line tool
• Schedule imports, sync jobs,
deployment tasks
52. Custom Integrations and Hooks
• Import sources
Implement your own data source
• Property modifiers
Resolve / mangle data
• Data types
Your custom meta data