Salt Stack Formula to set up and configure the Open Monitoring Distribution (OMD)
- This formula aims to follow the conventions and recommendations described at http://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html#conventions-formula and http://docs.saltstack.com/en/latest/topics/best_practices.html
- This formula isn't considered to be ready for production yet, at the moment I don't plan to spend more time into this formula since I'm going to setup another monitoring solution based on Salt and ElasticSearch!
- define parents when applicable (e.g. VMs)
- provide CMK config examples (
contrib/) - Bug: simultaneous execution of omd.cmkagent can prevent Salt from reloading the OMD site (because OMD prevents simultaneous reloads at the same time)
- setup and configure inventory plugins/ local checks
- config xinetd for livestatus
- Add this repository as a GitFS backend in your Salt master config.
- Configure your Pillar top file (
/srv/pillar/top.sls) and your pillars, see pillar.example.sls - Include this Formula within another Formula or simply define your needed states within the Salt top file (
/srv/salt/top.sls).
Installs a repo containing OMD packages (optionally)
Sets a Check_MK agent up
Manages an OMD instance with all its versions and sites
Apache httpd vhosts
If you don't want to truncate zzz_omd.conf which includes the default Apache httpd vhost config, overwrite config.manage in your pillars. But if you want to manage the vhost(s) manually use a httpd formula to manage httpd's vhosts.
Check_MK Configuration
This formula doesn't make use of Check_MK's Web Administration Tool (WATO ). The reason for this is that WATO has a confusing way (at least for me) of saving MK configuration files. Settings (like global settings in global.mk) aren't ordered in a specific order so it's often hard to generate WATO-like MK files.
This means to you that you A) should disable WATO in Multisite and B) configure all OMD/ Check_MK components manually including user DB, contacts, roles and more. Most of these will be possible with this formula.
Some states/ commands may refer to templates which aren't included in the files folder (omd/files). Take a look at contrib/ (if present) for e.g. template examples and place them in separate file roots (e.g. Git repository, refer to GitFS) in your Salt master config.
None
Contributions are always welcome. All development guidelines you have to know are
- write clean code (proper YAML+Jinja syntax, no trailing whitespaces, no empty lines with whitespaces, LF only)
- set sane default settings
- test your code
- update README.rst doc
Tested with:
- 2014.1.x
- 2014.7.x
Tested with:
- GNU/ Linux Debian Wheezy
- CentOS 6 (client side)