From fac47e0c9185c244650418d342f6d0a98168b835 Mon Sep 17 00:00:00 2001 From: Pavel Senchanka Date: Tue, 12 Jun 2018 10:52:18 +0200 Subject: [PATCH] Bumped version to 2.1.1. (#69) --- MIGRATING.md | 5 +++++ setup.py | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/MIGRATING.md b/MIGRATING.md index c2ecc93..1092661 100644 --- a/MIGRATING.md +++ b/MIGRATING.md @@ -4,6 +4,9 @@ The storage format of the filetracker server is very different in the new server so non-trivial migration is required if you want to preserve your users' files (submitted sources, problem packages, etc.). +After migration is complete, you may expect total filetracker storage size to decrease +by ~70% for a typical OIOIOI instance. + There are two migration options, but for both of them, you first need to make sure OIOIOI uses `remote_storage_factory` as `FILETRACKER_CLIENT_FACTORY` and `FILETRACKER_CACHE_ROOT` is configured in your `settings.py`. If you have a recent config version (23+), this is the default behaviour. @@ -33,6 +36,8 @@ Navigate to `ft_root` and execute the following command: CAUTION: if you have a lot of files (>100 GiB), this command may take a few days to complete, so doing this in a usual SSH session may not be the best idea. +Consider using `tmux` or `screen`. Average migration speed for our servers was +10 GiB/h. After the command above is completed you can safely remove the original `./files` directory (it's not used by the new server). Your previous server config should still work, diff --git a/setup.py b/setup.py index 8ffdecf..1151a38 100644 --- a/setup.py +++ b/setup.py @@ -1,7 +1,7 @@ from setuptools import setup, find_packages setup( name = 'filetracker', - version = '2.1', + version = '2.1.1', author = 'SIO2 Project Team', author_email = 'sio2@sio2project.mimuw.edu.pl', description = 'Filetracker caching file storage',