Follow these instructions to upgrade your IVLE installation. In the case of a multi-node installation, follow each instruction on every node unless otherwise specified.
Before commencing the main upgrade process, ensure that the slave web servers are inaccessible – stopping Apache is a good way to be sure.
sudo /etc/init.d/apache2 stop
You should then check for and kill any python-console process on the slaves. These are the console backend processes, and may hold resources open across the upgrade – that could end badly.
An upgrade is a good opportunity to purge obsolete jail mounts on each slave. Unmounting the jails will also reduce the likelihood of problems during the later jail rebuilds. Take heed of any Device busy errors – that normally indicates that a python-console process is still running.
sudo ivle-mountallusers -u
The next stage of the IVLE upgrade process depends on the installation mode.
To upgrade a source installation, update your checkout or extract a new release tarball.
Then build and install the updated code:
./setup.py build
sudo ./setup.py install
To upgrade an installation from the Ubuntu package, a normal apt upgrade is sufficient.
sudo apt-get update
sudo apt-get upgrade
If the new version has additional database patches, apply each in order on the master with something like this:
sudo -u postgres psql -d ivle -f userdb/migrations/YYYYMMDD-XX.sql
The code inside the jail will normally need to be kept in sync with that on the master and slaves. On the upgraded master:
sudo ivle-buildjail -u
To ensure that any configuration or structural updates are pushed into the jails, rebuild them all on the master.
sudo ivle-remakeuser -a
This will preserve the user files (in /home/USERNAME), but rebuild the external configuration files and filesystem structure.
If you’ve set a media version (in ivle.conf, the media section’s version value), you’ll need to update it on each slave. Set it to a value that hasn’t been used before – the IVLE version number, for example. Ensure that it is the same on all slaves.
The master’s user management server should be restarted after each upgrade.
sudo /etc/init.d/ivle-usrmgt-server restart
Now that the upgrade is done, Apache can be restarted on the slaves. This should bring IVLE back into service.
sudo /etc/init.d/apache2 start