Changes between Version 3 and Version 4 of Tutorial/DeployingVMApplications

Timestamp:

Aug 18, 2011, 3:55:47 PM (13 years ago)

Author:

romw

Comment:

checkpoint

Tutorial/DeployingVMApplications

@@ -1 +1 @@
 = Deploying VM Applications =
-
 == Introduction ==
-Using virtual machine technology with the BOINC client presents an interesting challenge to projects.  Projects not only have to follow the rules BOINC requires projects to follow but they also have to follow the rules that the virtual machine technology requires as well.  With this document we hope to provide a general outline of how to utilize the VirtualBox virtual machine technology within a BOINC based project.
-
-For the purposes of this document we are going to assume that a task instance only requires the use of a single CPU and no network communication is required during the execution of the task instance.
-
-
-=== Configuring  Application Version ===
+Using virtual machine technology with the BOINC client presents an interesting challenge to projects.  Projects not only have to follow the rules BOINC requires projects to follow but they also have to follow the rules that the virtual machine technology requires as well.  With this document we hope to provide a general outline of how to utilize the !VirtualBox virtual machine technology within a BOINC-based project.
+== Usage Scenarios ==
+There are basically two usage scenarios supported by the stock BOINC !VboxWrapper:
+
+* Network-focused VM
+
+* Task-focused VM
+
+=== Network-Focused VM === 
+A network- focused VM usually launches its own task agent which downloads work to be processed and eventually shuts down when completed.
+
+Requirements: !VboxWrapper, VM job description file, and VM Image.
+
+NOTES: Network communication can be hampered if the host machine is sitting behind a restrictive firewall or proxy server.
+
+=== Task-Focused VM ===
+A task-focused VM launches a single job downloaded by the BOINC client software and then shuts down.
+
+Requirements: !VboxWrapper, VM job description file, and VM Image, startup script, worker application
+
+NOTES: All network communication is disabled for the VM.
+
+== Configuring the BOINC Server ==
+Using !VirtualBox requires the use of two plan classes:
+
+* '''vbox32''': Is the application version assigned to 32-bit machines.
+
+* '''vbox64''': Is the application version assigned to 64-bit machines.
+
+NOTES:  The bitness of the !VboxWrapper and VM image should match which plan class they are assigned too.  A 32-bit wrapper cannot properly detect or use Virtual Box on a 64-bit machine.
+
+A typical installation would look like this:
+{{{
+apps/uppercase/
+    6.18
+        windows_intelx86__vbox32
+            version.xml
+            ...
+        windows_x86_64__vbox64
+            version.xml
+            ...
+}}}
+
+=== Application Version Record ===
 Version.xml:
 {{{
@@ -41 +78 @@
 </version>
 }}}
-
-=== Configuring Virtual Machine Description ===
+Configuration options for version.xml can be found [AppVersionNew here].
+=== Virtual Machine Description ===
 vbox_job.xml:
 {{{
@@ -51 +88 @@
 </vbox_job>
 }}}
-
-=== Configuring Startup Script ===
+Configuration options for VboxWrapper can be found [VboxApps here].
+=== Startup Script ===
 boinc_start.sh:
 {{{
@@ -65 +102 @@
 shutdown -hP 0
 }}}
-
+NOTES: Make sure the linefeeds conform to the UNIX standard otherwise bash will complain.
 == Appendix ==
 
 === Premade BOINC VM Wrapper ===
-
-Configuration Options for vboxwrapper can be found [VboxApps here].
-
 ==== Windows ====
-
+x86: [http://boinc.berkeley.edu/dl/vboxwrapper_6.20_windows_intelx86.exe.gz vboxwrapper_6.20_windows_intelx86.exe.gz]
+
+x64: [http://boinc.berkeley.edu/dl/vboxwrapper_6.20_windows_x86_64.exe.gz vboxwrapper_6.20_windows_x86_64.exe.gz]
+
+==== Mac ====
+TBD
 ==== Linux ====
-
-
-=== Premade Linux Images ===
-
+TBD
+=== Premade Linux VM Images ===
 x86: [http://boinc.berkeley.edu/dl/vmimagex86.vdi.gz vmimagex86.vdi.gz]
 
@@ -89 +126 @@
 Main advantages:
  * Small install size
- * VirtualBox guest additions installed by default
-
-The VirtualBox guest extensions are required in order to use the shared directory feature to communicate between the guest and host operating systems.
+ * !VirtualBox guest additions installed by default
+
+The !VirtualBox guest extensions are required in order to use the shared directory feature to communicate between the guest and host operating systems.
 
 ==== Role Selection ====
@@ -165 +202 @@
 
 The 'boinc_start.sh' script should contain whatever is needed to execute your job from within the VM.
-