Icinga Director v1.6.0 Dashboard
Icinga Director v1.6.0 has been released with Multi-Instance Support, Configuration Baskets and improved Health Checks. We’re excited to announce new features that will help you to work more efficiently.
Work with multiple Director- and Icinga Instances
Many Icinga Users operate distinct instances for various reasons. Most of them do so to have distinct environments for testing and production. With v1.6.0 it is now possible to switch between them from a single Web frontend. You can also grant User Roles access do different Director Databases.
Multiple Director Instances
We are pleased to announce the first open source release of our X.509 module for Icinga.
The X.509 module for Icinga keeps track of certificates as they are deployed in a network environment.
It does this by scanning networks for TLS services and collects whatever certificates it finds along the way.
The certificates are verified using its own trust store. (more…)
We are happy to announce a new bugfix release for Icinga Web 2.
Official packages are available on packages.icinga.com. Community repositories might need a while to catch up.
Version 2.6.2 addresses the following topics:
- Database connections to MySQL 8 no longer fail
- LDAP connections now have a timeout configuration which defaults to 5 seconds
- User groups are now correctly loaded for externally authenticated users
- Filters are respected for all links in the host and service group overviews
- Fixed permission problems where host and service actions provided by modules were missing
- Fixed an SQL error in the contact list view when filtering for host groups
- Fixed time zone (DST) detection
- Fixed the contact details view if restrictions are active
- Doc parser and documentation fixes
You can find all issues and features related to this release on our Roadmap.
With the TLS connection improvements there was also another bug with hanging TLS connections unveiled. Turns out, this has been sitting there since 2.8.2 and not only affects JSON-RPC cluster connections but also HTTP request sessions, as being used inside the Director kickstart wizard for example. Tom is working on a fix for Director 1.6 in order to support older Icinga 2 versions too.
2.10.2 also fixes a programming mistake with the minimum version parameter for the “icinga” check, thanks for the patch, Max! The path constant changes in 2.10 introduced a regression with the cache file for
icinga2 object list being overridden with the legacy 1.x objects cache content. You’re safe when you have disabled the
statusdata feature before 2.10.2. SELinux would throw an error with package related changes, this has been fixed too. The documentation has been updated for removed/updated packages too.
Check the full changelog prior to upgrading packages from the official repositories.
It’s been a while since the last Vagrant box update and release, so here are the highlights of the past months combined into a new shiny 2.0 release 🙂
New provider: OpenStack
In the past week I’ve been playing with OpenStack. Johan was so kind to send a PR nearly 2 years ago, now the NETWAYS NWS cloud is ready for OpenStack and my tests. Small things were needed to adopt the box provisioning with floating IPs. If you are an experienced OpenStack user, you’ll know how to source everything into your environment. Everyone else just can follow the newly written docs 🙂
Huge shout-out to Johan from CSC for his contribution!
The namespace support in 2.10 caused a regression with the registered global scope being evaluated for API permissions with filters. This release fixes the problem, next to a problem with Windows packages not fully starting up. There’s also a fixed oversight with not setting a default environment constant. This affects setups checking the SNI header in external load balancers.
v2.10.1 also fixes a problem with application reload and missing event states in large scale environments.