This documentation is for Release 2.0.0. For previous versions of Avalon look in the page history at version v.28.
These instructions will walk you through the process of building and running a VirtualBox virtual machine containing CentOS, Avalon 2.0, 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.
- Download and install VirtualBox (v4.2.8 or higher) for your host machine
- Download and install Vagrant (v1.1.5 or higher) for your host machine
- Download and extract the Avalon install script (as a zip or tar.gz)
- In a terminal window,
avalon-installer-flatdirectory you just extracted
- If this is the first time the script has been run, you will be asked for some information with which to initialize the Avalon installation:
- A username for the Avalon dropbox user (default is avalondrop, to accept press enter)
- A password for the Avalon dropbox user (set your own)
- The email address of the initial Avalon collection/group manager account (Default is email@example.com, to accept press enter. Use this address to log in after step 9 where you will set the password for this account.)
- The Rails environment to run Avalon under (default is production, to accept press enter)
- 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.
- When the script finishes, open a web browser and connect to http://localhost:10080/
- Click login and then select "Create an Identity"
- Use firstname.lastname@example.org to log in and set a password.
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:
Using the System
You can find specific information about using the system in the Collection Manager's Guide. Upload items individually or via batch. Batch demo content is available for your convenience, which includes the media files and an excel document necessary to run a batch. You can submit a batch directly via SFTP using the following settings:
|username/password||whatever you entered in step 6 above|
Known Issues - a list of bugs, workarounds, and cautions.