Installing from WW2.15 Ubuntu20.04 Server Virtual Machine Image

These instructions cover the installation of the Ubuntu Server 20.04 LTS 64 bit operating system and WeBWorK 2.15 using the WeBWorK Virtual Machine Image.

The WeBWorK Virtual Machine Image is an .ova file which is an "open, secure, portable, efficient and extensible format for the packaging and distribution of software to be run in virtual machines" (see http://en.wikipedia.org/wiki/Open_Virtualization_Format) and is supported by VMware, VirtualBox, AWS, Google Cloud, etc. This image file has been tested on VMware Workstation 15 Player and VirtualBox 6.

This "server" version contains everything you need to run a WeBWorK server (e.g. WeBWorK, Apache2, MySQL, R server, lighttpd, log rotation, etc.) installed and configured.

Installing from WW2.15 Ubuntu20.04 Server Virtual Machine Image

Overview

After installing from the WeBWorK Virtual Machine Image, you will have a full fledged Ubuntu Server 20.04 LTS system with WeBWorK, Apache2, MySQL, R server, lighttpd, log rotation, etc. installed and configured. If your network uses DHCP, networking will be automatically configured for your system. If it uses static IP addresses, you will have to configure networking. Also it is imperative that you CHANGE THE PASSWORDS for the OS user wwadmin (who has sudo privileges), for the MySQL user webworkWrite, and for the WeBWorK user admin who has professor privileges (see below). Finally you will have to install OpenSSH (since this has to be done locally) to gain SSL access to your server and you should set up SSL (https) access to WeBWorK.

There are more detailed instructions for Ubuntu Server 20.04 and WeBWorK 2.15 at Installation_Manual_for_2.13_on_Ubuntu_16.04

Download the ova image

There is only a 64 bit distribution. The 64 bit distribution should work with most modern cpu's. Download the md5 check sum and .ova file from either of the sites below. Download WW2.13_Ubuntu16.04_Vanilla.ova.md5 and WW2.13_Ubuntu16.04_Vanilla.ova . The ova is a 3.6 GB file.

• Rochester

1. http://hosted2.webwork.rochester.edu/ww-downloads/WW2.13_Ubuntu16.04_Vanilla.ova.md5
2. http://hosted2.webwork.rochester.edu/ww-downloads/WW2.13_Ubuntu16.04_Vanilla.ova

• MAA

1. http://webwork.maa.org/ww-downloads/WW2.13_Ubuntu16.04_Vanilla.ova.md5
2. http://webwork.maa.org/ww-downloads/WW2.13_Ubuntu16.04_Vanilla.ova

• Verify the MD5 checksum of your downloaded file agrees with the above. For information on how to verify the MD5 checksum, see e.g. https://help.ubuntu.com/community/HowToMD5SUM

Installing the WeBWorK Virtual Machine Image

Import the file WW2.13_Ubuntu16.04_Vanilla.ova into your virtualization software package (e.g. VMware, VirtualBox). The ova file was created on VirtualBox and has been tested on VirtualBox and VMware Player. Note on VMware Player you will get a warning message but on retry it will work. After importing, your virtual WeBWorK server will be identical to a system created from the WW2.13 Ubuntu16.04 Vanilla LiveDVD.

Note that on other virtual environments, you may need to take additional actions. See the section Other Virtual Environments below.

Continue the installation

You are exactly at the stage in the installation described in Installing_from_WW2.13_Ubuntu16.04_Vanilla_LiveDVD#Boot_your_server. Follow the instructions there. Note that if your server will be accessible from the internet, it is imperative that you follow the instructions for changing passwords.

Other Virtual Environments

Below you will find additional information about installing the ova on other virtual environments.

VMware's ESXi 5.5 Server

Jay A. Hightman <jhightman@mbc.edu>, Systems Administrator at Mary Baldwin College, reports that it is not possible to directly import the "WW2.9_Ubuntu14.04_Vanilla.ova" virtual machine directly in to VMware's ESXi 5.5 Server. There may be a similar problem with "WW2.13_Ubuntu16.04_Vanilla.ova". He sent us the following work around. Thanks Jay.

One gets the following error:

There are three offending sections in the OVA file, which I have highlighted
in red:
     <System>
       <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>
       <vssd:InstanceID>0</vssd:InstanceID>
<vssd:VirtualSystemIdentifier>WW2.9_Ubuntu14.04_Vanilla</vssd:VirtualSystemI dentifier>
       <vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
     </System>

     <Item>
       <rasd:Address>0</rasd:Address>
       <rasd:Caption>sataController0</rasd:Caption>
       <rasd:Description>SATA Controller</rasd:Description>
       <rasd:ElementName>sataController0</rasd:ElementName>
       <rasd:InstanceID>5</rasd:InstanceID>
       <rasd:ResourceSubType>AHCI</rasd:ResourceSubType>
       <rasd:ResourceType>20</rasd:ResourceType>
     </Item>

     <Item>
       <rasd:AddressOnParent>3</rasd:AddressOnParent>
       <rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>
       <rasd:Caption>sound</rasd:Caption>
       <rasd:Description>Sound Card</rasd:Description>
       <rasd:ElementName>sound</rasd:ElementName>
       <rasd:InstanceID>7</rasd:InstanceID>
       <rasd:ResourceSubType>ensoniq1371</rasd:ResourceSubType>
       <rasd:ResourceType>35</rasd:ResourceType>
     </Item>

A work around is to use the VMware OVF tool to convert the OVA to an VMX image.

Download VMware Open Virtualization Format Tool 3.5.2

https://my.vmware.com/web/vmware/details?downloadGroup=OVFTOOL352 <https://my.vmware.com/web/vmware/details?downloadGroup=OVFTOOL352&productId =353#product_downloads> &productId=353#product_downloads

C:\Program Files\VMware\VMware OVF Tool>ovftool.exe --lax "C:\Setup\MAA WeBWorK 2.9\WW2.9_Ubuntu14.04_Vanilla.ova" "C:\Setup\MAA WeBWorK 2.10\WW2.10_Ubuntu14.04_Vanilla.vmx"

Opening OVA source: C:\Setup\MAA WeBWorK 2.9\WW2.9_Ubuntu14.04_Vanilla.ova
Opening VMX target: C:\Setup\MAA WeBWorK 2.9\WW2.9_Ubuntu14.04_Vanilla.vmx

Warning:
- Line 25: Unsupported hardware family 'virtualbox-2.2'.
- Line 66: OVF hardware element 'ResourceType' with instance ID '5': No support
for the virtual hardware device type '20'.
- Line 83: OVF hardware element 'ResourceType' with instance ID '7': No support
for the virtual hardware device type '35'

Writing VMX file: C:\Setup\MAA WeBWorK 2.0\WW2.9_Ubuntu14.04_Vanilla.vmx

Transfer Completed

Warning:
- No manifest entry found for: 'WW2.9_Ubuntu14.04_Vanilla-disk1.vmdk'.
- No manifest file found.

Completed successfully

After doing this, I was able to upload the VMX and VMDK files which were
created to storage on a VMware ESXi 5.5 Server, import the system, and
continue the configuration of Ubantu as well as other installed applications
used by WeBWorK.

My hope is this information will be useful to you as well as other users of
WeBWorK virtual machine.

-- Main.ArnoldPizer - 27 August 2017