We’ve found Vagrant pretty useful for our demo cases – the first draft of the Icinga 2 Cluster happened to be a NETWAYS CeBit demo and evolved ever since. icinga-vagrant was added is official Icinga project similar to what we have with our Docker demos and gained more attraction by testers and developers.
The good thing about Vagrant using different providers is – you can even run these demos on Windows. You’ll need some prerequisites to make it work on Windows though – Git with SSH and Ruby. On Linux the Vagrant packages already requires them. Additionally you’ll need at least the following versions:
- Vagrant >= 1.6.5
- VirtualBox >= 4.2.16
Our default provider is VirtualBox where these boxes are regularly tested on. The underlying provisioner is using Puppet modules to setup the Vagrant environment. This installs for example Apache, MySQL, Plugins, Icinga 2 and Icinga Web 2 in the icinga2x box. The Icinga packages are pulled from our snapshot repositories allowing developers and testers fetching the latest and greatest – and also help finding bugs soon enough :-)
Currently there are four different Vagrant environments available for testing:
- icinga2x: Standalone Icinga 2 box with user interfaces: Icinga Web 2, Icinga Web 1.x and Classic UI 1.x
- icinga2x-cluster: Icinga 2 Cluster as Master-Checker setup. Includes Icinga Web 2 as user interface.
- icinga2x-graylog2: Special Graylog demo environment with standalone Icinga 2
- icinga1x: Standalone Icinga 1.x Core with Icinga Web 1.x and Classic UI 1.x. Includes Jasper-Reporting.
Note that icinga1x will stick with CentOS6 due to the Reporting integration (unless someone sends a patch). The other boxes have been upgraded recently to use CentOS 7.1 as base box.
There were several changes in the past months, refactoring the required git modules from submodules to subtree and also updating the demo configuration. All icinga2x boxes also share common host-only IP addresses for easier access. Once puppet-icinga2 and puppet-icingaweb2 become ready, they’ll be included inside the provisioning mechanism replacing our own local modules. In order to keep it simple, you may just download the latest release tarball instead of cloning the git repository.
Start away with the Icinga 2 box:
$ git clone https://github.com/Icinga/icinga-vagrant.git
$ cd icinga-vagrant
$ cd icinga2x
$ vagrant up
Open your browser and navigate to the host-only ip addresses (Login: icingaadmin/icinga)
If you encounter problems, please open an issue at https://dev.icinga.org/projects/icinga-tools/issues – meanwhile enjoy the Vagrant show! :-)
2.3.7 last week introduced a problem with DB IDO PostgreSQL when fixing a separate issue. Next to that we’ve also backported some more fixes from our development tree for 2.4 into v2.3.8.
Check the Changelog below while preparing your update.
What’s New in Version 2.3.8
- Bug 9554: Don’t allow “ignore where” for groups when there’s no “assign where”
- Bug 9634: DB IDO: Do not update endpointstatus table on config updates
- Bug 9637: Wrong parameter for CheckCommand “ping-common-windows”
- Bug 9665: Escaping does not work for OpenTSDB perfdata plugin
- Bug 9666: checkcommand disk does not check free inode – check_disk
This time we’ll release two Icinga Core bugfix releases – Icinga 2 v2.3.7 and Icinga v1.13.3.
Package updates are available soon, meanwhile check the Changelog below.
What’s New in Version 2.3.7
- Feature 9610: Enhance troubleshooting ssl errors & cluster replay log
- Bug 9406: Selective cluster reconnecting breaks client communication
- Bug 9535: Config parser ignores “ignore” in template definition
- Bug 9584: Incorrect return value for the macro() function
- Bug 9585: Wrong formatting in DB IDO extensions docs
- Bug 9586: DB IDO: endpoint* tables are cleared on reload causing constraint violations
- Bug 9621: Assertion failed in icinga::ScriptUtils::Intersection
- Bug 9622: Missing lock in ScriptUtils::Union
What’s New in Version 1.13.3
- Bug 7337: Only use SCHEDULE_HOST_DOWNTIME command for Icinga 2.x
- Bug 8130: Wrong values for percent_* when using hostgroup in availability report
- Bug 9020: Solaris package behaves badly upon uninstall
- Bug 9106: Icinga no longer sending acknowledgement notifications
- Bug 9240: invalid JSON for flapping threshold configuration
While updating the documentation and Icinga Template Library definitions, we’ve also tackled a more severe problem with OpenSSL on SLES11 SP3 with this bugfix release v2.3.6.
SLES11 uses the old 0.9.8j release causing trouble when verifying the SSL certificates generated from ‘node wizard’ commands (see #9549 for a detailed analysis). The problem became even more weird when debugging it, so we decided to go for the only safe solution – link against openssl1 from the Security Module repository.
The package update for SLES11 requires openssl1, please ensure enabling the repository beforehand. You can use this small check script “check_icinga2_openssl” (shown in the screenshot).
Other than that, we’ve also fixed some bugs found inside the Windows plugins and NSClient++ integration. Whilst backporting a stability fix for the cluster from our 2.4 development tree there’s also more verbose logging for unauthenticated clients and cluster troubleshooting available.
Package updates should be around soon, meanwhile keep cool and check the Changelog below!
What’s New in Version 2.3.6
- Require openssl1 on sles11sp3 from Security Module repository
- Bug in SLES 11’s OpenSSL version 0.9.8j preventing verification of generated certificates.
- Re-create these certificates with 2.3.6 linking against openssl1 (cli command or CSR auto-signing).
- ITL: Add ldap, ntp_peer, mongodb and elasticsearch CheckCommand definitions
- Feature 6714: add pagerduty notification documentation
- Feature 9172: Add “ldap” CheckCommand for “check_ldap” plugin
- Feature 9191: Add “mongodb” CheckCommand definition
- Feature 9415: Add elasticsearch checkcommand to itl
- Feature 9416: snmpv3 CheckCommand: Add possibility to set securityLevel
- Feature 9451: Merge documentation fixes from GitHub
- Feature 9523: Add ntp_peer CheckCommand
- Feature 9562: Add new options for ntp_time CheckCommand
- Feature 9578: new options for smtp CheckCommand
- Bug 9205: port empty when using icinga2 node wizard
- Bug 9253: Incorrect variable name in the ITL
- Bug 9303: Missing ‘snmp_is_cisco’ in Manubulon snmp-memory command definition
- Bug 9436: Functions can’t be specified as command arguments
- Bug 9450: node setup: indent accept_config and accept_commands
- Bug 9452: Wrong file reference in README.md
- Bug 9456: Windows client w/ command_endpoint broken with $nscp_path$ and NscpPath detection
- Bug 9463: Incorrect check_ping.exe parameter in the ITL
- Bug 9476: Documentation for checks in an HA zone is wrong
- Bug 9481: Fix stability issues in the TlsStream/Stream classes
- Bug 9489: Add log message for discarded cluster events (e.g. from unauthenticated clients)
- Bug 9490: Missing openssl verify in cluster troubleshooting docs
- Bug 9513: itl/plugins-contrib.d/*.conf should point to PluginContribDir
- Bug 9522: wrong default port documentated for nrpe
- Bug 9549: Generated certificates cannot be verified w/ openssl 0.9.8j on SLES 11
- Bug 9558: mysql-devel is not available in sles11sp3
- Bug 9563: Update getting started for Debian Jessie
It’s an untold rumor that team Icinga is joining each year‘s Open Source Monitoring Conference (OSMC) from the very beginning in late 2009. Now OSMC is celebrating their 10th year of glory from 16.-19.11.2015. The 3rd day was announced to be a hackathon where some of team Icinga will join to work on cool stuff in Icinga 2, Icinga Web 2 and modules – more time to connect and discuss, awesome :)
The call for papers is still running, and as we know that our community loves Icinga 2 and most recently Icinga Web 2, are you ready to share your story on Icinga at OSMC?
- Be it a whole new setup, its challenges in installation, configuration and alerting …
- or a difficult brainf*ck to sort the migration from Nagios/Icinga 1 – that should certainly make it into an one hour talk :)
- Any chance you are using the Puppet, Ansible, Chef modules for automated deployment with Icinga 2, and want to shed some light into practical examples?
- Are you using a clustered environment with Graphite, Logstash, InfluxDB or are you already going the Docker containerized way?
- Going strong with plugin development best practices, sharing them all the way through Icinga Exchange?
- Any different visualization challenges, e.g. Dashing integration and your NOC dashboards by example?
- … your very own experience :)
Go for it – we love to see how our community uses Icinga and catch up with you: OSMC Call for Papers.
As for ourselves, we will join you with news and updates on Icinga 2 v2.4 – or, like Bernd says: Apification. More on Icinga Web 2 and its steps towards a final release, more on Icinga Web 2 modules and keep your fingers crossed for an all new configuration UI for Icinga 2. Well, and certainly more stuff we always come up with.
See you in Nuremberg! Or – any time sooner, submit your talk for Icinga Camp Portland at Puppetlabs :)