From bfa849acc224978a0791926d47c22dc8be6a9daf Mon Sep 17 00:00:00 2001 From: Sylvain Date: Tue, 24 Jul 2018 14:44:14 +0200 Subject: [PATCH] Version 2.6.5 --- .fabmanager-version | 2 +- CHANGELOG.md | 2 +- doc/elastic_upgrade.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.fabmanager-version b/.fabmanager-version index c0e593c23..68167133b 100644 --- a/.fabmanager-version +++ b/.fabmanager-version @@ -1 +1 @@ -2.6.5-dev +2.6.5 \ No newline at end of file diff --git a/CHANGELOG.md b/CHANGELOG.md index b2315d8fd..6db6dc8b5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,6 @@ # Changelog Fab Manager -## next release +## v2.6.5 2018 July 24 - Upgraded ElasticSearch from 1.7 to 5.6 - Ability to display the name of the user who booked a machine slot to other members diff --git a/doc/elastic_upgrade.md b/doc/elastic_upgrade.md index 81950705f..a4cc4517d 100644 --- a/doc/elastic_upgrade.md +++ b/doc/elastic_upgrade.md @@ -12,7 +12,7 @@ We've wrote a script to automate the process while keeping your data integrity, Please ensure that you'll have enough space, considering the point above. The script won't run otherwise. - This script will run on any Linux or Macintoch systems if you installed ElasticSearch using docker or docker-compose. Otherwise, only Debian compatible OS (like Ubuntu) and MacOS X are supported for classical installations. On any other cases you'll need to perform the upgrade yourself manually. -- If your ElasticSearch instance uses replicas shards, you can't use this script and you must perform a manual upgrade (you're not concerned if you have a standard installation). +- If your ElasticSearch instance uses replicas shards, you can't use this script and you must perform a manual upgrade (if you have a standard fab-manager installation and you don't understand what this mean, you're probably not concerned). Once you've understood all the points above, you can run the migration script with the following: