P4: 36. VM Testing

[saloynton]

36. Virtual Machine Testing

NB. Documentation for working with the Virtual Appliance is to be found here: ​https://www.openmicroscopy.org.uk/site/support/omero432/getting-started/demo/virtual_appliance
This is especially useful for instructions on setting up port forwarding after appliance install

Appliance Import Testing

• If you do not have VirtualBox? installed then download it from ​http://www.virtualbox.org/wiki/Downloads & follow the installation instructions.
• Download the last QA virtual appliance which should be named omero-vm.ova from ​http://hudson.openmicroscopy.org.uk/job/OMERO-trunk-virtualbox/lastSuccessfulBuild/artifact/src/docs/install/VM/omero-vm.ova
• Start VirtualBox? and select File >> Import Appliance
• Accept the defaults offered by VirtualBox? and follow the on screen prompts until your appliance is imported. At this point there should be a new virtual machine located in your virtual machine library.
• Select the omero-vm virtual machine then click the start button from the menu bar.
• NB. Check port forwarding. If no port forwarding is sset up then use the script (from here: ​http://www.openmicroscopy.org.uk/site/support/omero432/getting-started/demo/scripts/setup_port_forwarding.sh) to set up port forwarding, e.g.

$ bash setup_port_forwarding.sh omero-vm

• Your VM should now boot. This completes the first phase of the VM testing.

The following two scenarios assume that the appliance import phase has completed successfully.

Virtualised OMERO.server Testing (A) Using an OMERO.client

• Start your omero VM
• Connect to your VM using OMERO.insight in your host environment [SERVER ADDRESS=localhost SERVER PORT=4064, USERNAME=root, PASSWORD=omero]
• Import a couple of test images into your virtual OMERO.server using insight importer as usual.

Virtualised OMERO.server Testing (B) Using the CLI

• Log into your Omero VM using SSH. In a shell run:

$ ssh -p 2222 omero@localhost

• & use the password omero
• This should give you a shell on the VM
• Run the Omero diagnostics command. Assuming that OMERO.server is correctly installed this should work as expected for a native install

$ omero admin diagnostics