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

« Previous Version 15 Next »

Work in progress. Don't do this!! Avalon v.4.0 Hasn't been released yet.

Preparing for the Upgrade 

Before doing anything to prepare for the upgrade, backup your Avalon 3.3 installation.


In avalon.yml, under streaming, change "url_handler:" to "server:". 

Add under streaming: "content_path:" and then the path to your rtmp stream folder.

It should look something like this:

    server: :adobe
    content_path: /var/avalon/rtmp_streams
    stream_token_ttl: 20
    rtmp_base: rtmp://


Additional controlled vocabularies are required for Avalon 4. Merge the new version of config/controlled_vocabulary.yml.example with your customizations in config/controlled_vocabulary.yml. See Managing Controlled Vocabularies.



See What's New in Avalon 4.0 for more details.


The following instructions will work for any Avalon 3.3 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.

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:

Upgrade Avalon
# 1. if starting from Portable VM image, download the installer package, unpack, and link it
$ wget -O flat.tar.gz 
$ tar xzf flat.tar.gz
$ export INSTALL_DIR=`pwd`
$ ln -s $INSTALL_DIR/avalon-installer-flat/files /etc/puppet/avalon_files

# 2. navigate to the installer
$ cd avalon-installer-flat

# 3. remove the Avalon deploy tag
$ rm -f /var/www/avalon/bare-deploy
$ rm -rf /opt/staging/avalon/avalon-bare-deploy.tar.gz /opt/staging/avalon/avalon-bare-deploy
# 4. pin mysql to version in new Gemfile.local
$ cp modules/avalon/files/shared/Gemfile.local /var/www/avalon/shared/Gemfile.local

# 5. apply the puppet manifest
$ puppet apply --fileserverconfig=fileserver.conf --modulepath=modules \
	--hiera_config=hiera/hiera.yaml --templatedir=templates manifests/init.pp

# 6. reindex
$ su - avalon -c "cd /var/www/avalon/current; RAILS_ENV='production' bundle exec rake avalon:reindex"
Upgrade Matterhorn
# 1. Switch to matterhorn user
$ su - matterhorn
$ cd /usr/local/matterhorn
# 2. Install updated encoding profiles
$ cd etc/encoding
$ wget --no-check-certificate -O

# 3. Remove avalon workflow notifier bundle
$ rm lib/matterhorn/matterhorn-workflow-notifier-avalon-1.4-SNAPSHOT.jar
# 4. Restart Matterhorn
$ exit
$ service matterhorn stop
$ service matterhorn start
Upgrade Red5
# 1. Stop Red5
$ service red5 stop
# 1. Switch to red5 directory
$ cd /usr/local/red5
# 2. Install updated avalon webapp
$ cd webapps/avalon
$ wget --no-check-certificate -O WEB-INF/lib/red5-avalon.jar
$ wget --no-check-certificate -O WEB-INF/
$ wget --no-check-certificate -O WEB-INF/red5-web.xml
$ wget --no-check-certificate -O META-INF/MANIFEST.MF
$ chmod -R a+x META-INF WEB-INF

# 3. Restart Red5
$ service red5 start

If you didn't load the sample content before, try it out to test your avalon 4.0 upgrade.

  • No labels