As of Release 5, Avalon no longer supports installation via Vagrant. For releases up to 4.0, these instructions will still be applicable. For Release 5 installation instructions, click here.
This documentation is for Release 4.0. For documentation on previous releases, please select from the options below.
These instructions will walk you through the process of building and running a VirtualBox virtual machine containing CentOS, Avalon, Fedora, and Opencast Matterhorn. The process is automated end-to-end using Vagrant and Puppet. The virtual machine is configured to use network port forwarding, so Avalon's web interface will be accessible via a specific port number (10080) on the host machine. The virtual machine created using this process does not contain sample content.
avalon-installer-flatdirectory you just extracted
Be patient. The script needs to download and launch a bare-bones Linux VM, then download, install and configure a whole lot of dependencies and servers. This could take 30 minutes or more even with a fast connection.
NOTE: The installer needs to download dozens of system packages, software distributions, source files, and other information, largely from trusted third party repositories. Sometimes, one or more repositories might be offline, unresponsive, or otherwise unavailable, causing the Puppet provisioning software to display a series of errors about failed dependencies. Don't Panic. Fortunately, Puppet can usually figure out how to make things right. Simply type
vagrant provision to try to repair the install. If it doesn't seem to work, you can always
vagrant destroy and
vagrant up again to start over.
|In order to...||Type...|
|...put the Avalon VM into "sleep state"|
|...resume a suspended VM|
|...shut down the Avalon VM, but keep it around|
|...terminate the VM and delete it from the host machine|
|...restart a halted VM, or recreate a destroyed one|
The Avalon Media System requires several ports to be open to client browsers. The Vagrant install handles all the port forwarding for local access automatically:
You can find specific information about using the system in the Collection Manager's Guide. Sample content is available for your convenience. Upload new items individually or by batch directly via SFTP using the following settings:
|username/password||whatever you entered in step 6 above|
Configure additional features
Known Issues - a list of bugs, workarounds, and cautions.