From 82ed9efd917c4efea435507c58fc9b93511f1cfc Mon Sep 17 00:00:00 2001 From: Johannes Meyer Date: Thu, 18 Jun 2015 15:48:23 +0200 Subject: [PATCH] Add instructions on how to upgrade to rc1 --- doc/installation.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/doc/installation.md b/doc/installation.md index 133f6cb98..9f021624e 100644 --- a/doc/installation.md +++ b/doc/installation.md @@ -252,3 +252,21 @@ affects environments that opted for not storing preferences, your new backend is Because Icinga Web 2 Beta 3 does not introduce any backward incompatible change you don't have to change your configuration files after upgrading to Icinga Web 2 Beta 3. + +## Upgrading to Icinga Web 2 Release Candidate 1 + +The first release candidate of Icinga Web 2 introduces the following non-backward compatible changes: + +* The database schema has been adjusted and the tables `icingaweb_group` and + `icingaweb_group_membership` were altered to ensure referential integrity. + Please use the update script located in **etc/schema/upgrade** to update your + database schema +* Users who are using PostgreSQL < v9.1 are required to upgrade their + environment to v9.1+ as this is the new minimum required version + for utilizing PostgreSQL as database backend +* The restrictions `monitoring/hosts/filter` and `monitoring/services/filter` + provided by the monitoring module were merged together. The new + restriction is called `monitoring/filter/objects` and supports only a + predefined subset of filter columns. Please see the module's security + related documentation for more details. +