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 50 Next »

Getting a Virtualization Product

The Avalon VM is distributed as an Open Virtualization Appliance which should be compatible with these Virtual machine products:

Other virtualization products may be used but they will require manually converting the OVA file into something useful.

Getting the Avalon Virtual Machine Image

The Avalon VM file is located at http://avalonmediasystem.org/downloads/avalon-vm.ova and is roughly 5G.  Due to the size, it may take some time to download.

Importing the Avalon VM Image

Each virtualization product has different methods for using a VM appliance.  The tested methods are below.  If you use a product which is not listed, please contact us with usage instructions and we will add them here.

VirtualBox

  • Start the VirtualBox Manager
  • Select the "File/Import Appliance..." menu item
    • Click the "Open Appliance..." button and select the Avalon VM image you downloaded
    • Press "Next >"
    • Check the "Reinitialize the MAC address of all network cards" box
    • Press "Import"
  • The VM should now be visible in the list.
    • Select the Avalon VM 
    • Press the "Settings" icon
      • Select the "Network" tab
      • Make sure the "Attached to" field is set to "Bridged Adapter"
      • Press "OK"
    • Press "Start" icon to boot the VM

Generic VM Product

A generic VM product may be set up using these settings:

  • Unpack the .ova file – it is just a tarball containing a .vmdk file and a configuration file
  • Use these settings for the VM:
    • 64-bit guest
    • At least 2G of RAM (the shipped settings use 3G)
    • At least 1 core
    • Graphical Display
    • System disk the the .vmdk from the .ova package
    • The network interface must be bridged and have a unique MAC address
  • Start the VM as appropriate for this VM software

Notes for ALL Virtualization Products

Disk Usage

The disk image in the OVA package is dynamically-allocated with a maximum size of 500G.  While the disk image may only use a few gigabytes when it is first used, it will grow as more data is placed into the VM.  Most VMs behave unpredictably when the host system doesn't have enough disk space to satisfy guest OS requests.  Monitor the disk usage closely.

Firewall

If there is a firewall on the network, these ports must be accessible to the clients:

PortPurpose
tcp/22SSH and SFTP Access
tcp/80Web Access
tcp/1935Streaming Media Access for Red5 (RTMP)
tcp/18080Matterhorn

First Boot of Avalon VM

The VM will take while to boot.  This is normal since some of the system services are slow to start.

When the VM is booted for the first time you will be taken through a series of steps to configure the virtual machine for use.  Many of the screens are the same as a standard CentOS or RedHat Enterprise Linux post-installation first boot.  For reference, the RedHat documentation for this process is at https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-firstboot.html.  Only pages which are specific to Avalon or differ from their RHEL counterparts are detailed below.

License Information

The Avalon and CentOS End User License Agreements are displayed.  Agree to the licensing terms and press Forward to continue.

Update Networking

The default networking configuration uses DHCP.  To change the networking configuration, press the Network Settings button to start the standard NetworkManager connection editor.  When the network configuration is correct, press Forward to continue. 

Build FFMPEG

FFMPEG is an open source tool used to convert multimedia formats into other formats.  While it is open source, there are some configurations that cannot be distributed as a binary package.  Avalon uses such a configuration, so to adhere to the licensing restrictions, the end-user (you) have to build FFMPEG.  To make the process easy, this screen offers a push button which will begin the process of building and installing a FFMPEG binary which will be used by avalon.  The installation will not continue until FFMPEG is built.

The build can take 15 minutes or more to finish.  Wait until the terminal screen shows a completion message before pressing Forward.

Once FFMPEG is built, the terminal window will display a message informing you to press the Forward button to continue the installation. 

If the build fails or otherwise has trouble, the installation will allow you to continue, but Avalon will not be fully functional.  Contact the developers for assistance.  The build log can be found in /root/ffmpeg-build.log.

Avalon Email

Avalon will send email in response to different events or at the request of the users:

User CommentsThis is the destination email address for comments sent in by users
Avalon NotificationsIf there are issues with processing or other outstanding requests, they are sent to this address
Support Requests

Support questions from the end users are sent to this address

In addition to the email addresses, the setup also requires an SMTP relay host to use to send email.  The port for the relay will usually be 587.

Avalon Configuration

There are two more pieces of information required for the Avalon set up to complete.

  • Access Hostname - this is the host name the users will use to connect to avalon.  The default is the name returned by DNS for the IP of the machine.  If a DNS alias is used then the name should be set to the alias.
  • Initial User - Avalon requires an initial user to be set up at install.  This user has the ability to manage other users.  The username should look like an email address and the password cannot be blank.

Reboot

Now that all of the changes have been made the Avalon is nearly ready to use.  The access URL is displayed on this screen.  Press Finish to reboot the machine and apply all of the changes.

Using the Avalon VM

Once the VM has rebooted and the login screen has appeared, the Avalon system is ready to use.  To use Avalon, go to the access URL that was displayed and log in as the user that was created during the first boot.

If the URL that was displayed on the reboot screen doesn't work, the IP of the VM may have changed during the reboot.  There are a couple of ways to determine the access URL:

  • If a hostname is displayed on the login screen then CentOS was able to determine a name from the IP that was assigned to it and that name should be used.  If this hostname doesn't work, try the next method.
  • If the login window displays a generic CentOS version string, then it was unable to find a DNS entry for the address it was given.  Log in to the machine and run

    /etc/init.d/avalon_host_config hostname

    and the name displayed will be the access hostname.  This is the value that is inserted into the Avalon configuration files on boot, so it should work.

  • If your organization requires DHCP clients to register their MAC address, a web browser is available on the VM to register.  The machine will need to be rebooted to get the new networking information.

Troubleshooting the Avalon VM

Discovering Configuration

Besides the hostname (which is covered above), all of the settings and passwords that were set by the install process are stored in /root/avalon-setup.log.

SFTP dropbox password

The SFTP dropbox user is "avalondrop" and the random password generated user can be discovered by running this as root:

grep avalondrop /root/avalon-setup.log

Matterhorn admin password

Matterhorn runs on http://<access host>:18080 and has an administrative user called "admin".  The password can be determined by running this as root:

grep security.admin.pass /root/avalon-setup.log

Fedora admin password

The username for the fedora instance on http://localhost:8983/fedora is "fedoraAdmin".  The password can be determined by running this as root:

grep fedoraAdmin /root/avalon-setup.log

Reconfiguring Avalon VM

All of the avalon configuration scripts below leave a log of changes in /root/avalon-setup.log.  Since this file may contain passwords, make sure the file permissions are set appropriately.

Email Addresses

The avalon email addresses can be reconfigured by running (as root):

/usr/share/avalon/avalon_config_email <comments_email> <notifications_email> <support_email> <smtp_server_address> <smtp_port>

To use the existing value for any of the above arguments, use '-'.  The Avalon application stack will need to be restarted for the changes to take effect.

Randomize Passwords

To randomize the passwords used by Avalon, the command

/usr/share/avalon/avalon_randomize_passwords

can be used.  The changes will appear in /root/avalon-setup.log and Avalon will need to be restarted to make sure the passwords work correctly.

Accessible Hostname Configuration

Reconfiguring the accessible network address is more complicated.  On each reboot the accessible name is reconfigured during startup when

/etc/init.d/avalon_host_config

is run.  If the file /etc/sysconfig/avalon_host_config contains a name, that is used for the accessible name, otherwise the DNS name for the host is used.  If this script is run during normal operations, the avalon services will need to be restarted to be updated with the new configuration.

Known Issues

These are issues which are known or may be future todo items.

  • (question) should there be instructions for a NAT'd VM?
  • (question) If VirtualBox doesn't have focus the screen may stop updating after a while for the build FFMPEG step.  Giving VirtualBox focus updates the screen. This is probably related to the screensaver since it stops updating about 10 minutes in.
  • (question) Matterhorn has a service that is named after the original DHCP hostname from install time.  It seems to be harmless but looks confusing.
  • (warning) Sometimes when using the dropbox a duplicate processing job appears in matterhorn and the first one will fail during distribute-hls.  The second one processes normally.
(question) oddity, potential todo item(plus) todo item(minus) issue w/o workaround(warning) issue with workaround

 

 

 

 

 

  • No labels