- Simple scenarios
- Complex scenarios
- Bridging scenarios
This image realises the basic setup. The image consists of a single VM which has a BOINC server installed based on the SZTAKI-BOINC software package. It is hosting a BOINC project called “edgitest”. There is a 3G Bridge component configured against the BOINC project. The WSSubmitter service is also configured to enable the SOAP based WS submission of jobs. There is also a BOINC client running on this VM for testing purposes and configured to check for work units frequently. Finally, a simple application called “dsp” is deployed under the BOINC project and 3G Bridge in order let the admin have a testing application right after the VM is operational.
The operating system is Debian 6.0 (amd64, 64-bit architecture).
The VM hard disk images come in the qcow2 format which is the native format of QEMU. We have chosen this format because it is compressed and there is a tool called qemu-img which can covert these files to all widely used virtual machine monitor formats. Although some VM monitors (such as kvm) might be able to use qcow2 files directly it is suggested to first convert these images to another format (e.g. raw) for performance. More information about qemu-img can be found at http://wiki.qemu.org/download/qemu-doc.html#qemu_005fimg_005finvocation
The VM image has its stock kernel as well as a kernel compatible with Xen installed. Since this VM image require a 64-bit OS the VM host must be able to accomodate to x86_64 type VMs.
Important! If the VM is started manually (not in a cloud), the openvpn config should be modified and started manually (details in /etc/rc.local)!
The 3G Bridge related configuration files can be found at
On the VM, log files of the BOINC project are located at
In particular, the logs of the 3G Bridge components are called app_3g-bridge_3g-bridge_1.log, while the logs of the WSSubmitter is app_3g-bridge_wssubmitter_2.log. The logs of the BOINC client is at
The root password for the image is