Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Preparing for the Upgrade

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, 

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.

The one important piece of information you will need from the previous install is the name of the avalon dropbox user. The default is "avalondrop" (and the portable VM image uses this value), but it may have been changed during Step 6 of the Vagrant installation or Step 8 of the Puppet installation.

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.

  • Portable VM image:
    Open a terminal window from within the VM console, and type su root to become the root user. This will require the root password you provided the first time the system was booted.
  • Vagrant virtual machine:
    From within the original installer directory (from step 4 of the Vagrant Virtual Machine Image Installation Instructions), type vagrant ssh to log in as the vagrant user, then type sudo -i to become the root user.
  • Manual Puppet installed machine:
    Log in and become root as you did in steps 1 and 2 of the Manual Puppet Install instructions.

Once you have a root prompt, proceed with the upgrade as follows:

Download the new installer
# 1. download and extract the installer with all dependencies included
$ wget
$ unzip
$ cd avalon-installer-flat

# 2. upgrade RVM
$ rvm get stable
# 3. set the installation directory to the R3 avalon installer
$ ln -sf $(pwd)/files /etc/puppet/avalon_files

# 4. fix the dropbox chroot in the ssh configuration
$ perl -pi.bak -e 's/Group dropbox/User avalondrop/' /etc/ssh/sshd_config
$ service sshd restart

# 5. remove the Avalon deploy tag
$ rm -f /var/www/avalon/bare-deploy
# 7. collect facts to feed to puppet about your installation
$ ruby -r './fact_gatherer.rb' -e 'FactGatherer.gather_facts'

# 8. apply the puppet manifest
$ puppet apply --fileserverconfig=fileserver.conf --modulepath=modules \
	--hiera_config=hiera/hiera.yaml --templatedir=templates manifests/init.pp
# 9. 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.

  • No labels