There are some steps you can take to make the upgrade and transition to Avalon 3.1 smoother. Before doing anything to prepare for the upgrade, backup your Avalon 3.0 installation.
LDAP groups can now be used to grant access to items. See Configuring LDAP Access Control for how to set this up.
See the release notes for more details.
The following instructions will work for any Avalon 3.0 installation that used Puppet as its source. This includes the portable VM Image Installation, the Vagrant Virtual Machine Installation, and the Manual Puppet Install.
Upgrading is fairly simple, and must be run as the root user from a bash prompt on the Avalon system. The process for this depends on which kind of installation you have.
su rootto become the root user. This will require the root password you provided the first time the system was booted.
vagrant sshto log in as the vagrant user, then type
sudo -ito become the root user.
Once you have a root prompt, proceed with the upgrade as follows:
# 1. download and extract the installer with all dependencies included $ wget http://www.avalonmediasystem.org/downloads/avalon-installer-flat.zip $ unzip avalon-installer-flat.zip $ cd avalon-installer-flat # 2. set the installation directory to the R3 avalon installer $ ln -sf $(pwd)/files /etc/puppet/avalon_files # 3. remove the Avalon deploy tag $ rm -f /var/www/avalon/bare-deploy # 4. apply the puppet manifest $ puppet apply --fileserverconfig=fileserver.conf --modulepath=modules \ --hiera_config=hiera/hiera.yaml --templatedir=templates manifests/init.pp # 5. reindex $ su - avalon -c "cd /var/www/avalon/current; rake avalon:reindex"
If you didn't load the sample content before, try it out to test your avalon 3.1 upgrade.