Changes between Version 4 and Version 5 of VmApps

Timestamp:

Jan 20, 2009, 11:30:39 AM (16 years ago)

Author:

dweir

Comment:

--

VmApps

@@ -23 +23 @@
 > 3. For a given workunit, the wrapper XML standard is then used to send a package containing a non-BOINCified program and dependencies (suppose a RPM for the CernVM). This is installed using a call to RunProgramInGuest() by the VMWare-aware wrapper. This is then also used to start the program running.
 
-> 4. (main loop). The wrapper polls the process handle returned by RunProgramInGuest() to see if the workunit has finished. It also calls boinc_time_to_checkpoint(); then runs VixVM_CreateSnapshot() to create a snapshot as a checkpoint, if necessary.
+> 4. (main loop). The wrapper polls the process handle returned by !RunProgramInGuest() to see if the workunit has finished. It also calls boinc_time_to_checkpoint(); then runs !VixVM_CreateSnapshot() to create a snapshot as a checkpoint, if necessary.
 
 > 5. Upon successful completion of the inner job, we must copy out the results, uninstall the workunit package in the VM and move the checkpointed snapshot. The results are then sent back to the BOINC server. We can get the CPU time easily inside the virtual machine by calling the executable through time(1), say, but it may turn out to be more reasonable to use the cputime estimate made by the core client itself.
@@ -35 +35 @@
  * If we specialise to VMWare Server 1, we do not gain access to all the API calls suggested in "David's proposal" above. The snapshot calls are not available until VMWare Server 2, which unfortunately does not allow anonymous logins to the local machine.
 
- * Much as we would like to use the latest possible release of VMWare server, if we require the user's login details we would not be able to BOINCify the VMWare calls because the user would have to provide the correct username and password for the VMWare server. This would (at least) require interactive input to the wrapper (user provides login to VMWare server), and (most probably) changes to the BOINC infrastructure. The latest [http://www.vmware.com/support/developer/vix-api/vix16_reference/ VIX reference] page for VixHost_Connect() mentions logging in anonymously as the current user on the current host, so it is possible that this is simply an oversight in the current release of VMWare Server.
+ * Much as we would like to use the latest possible release of VMWare server, if we require the user's login details we would not be able to BOINCify the VMWare calls because the user would have to provide the correct username and password for the VMWare server. This would (at least) require interactive input to the wrapper (user provides login to VMWare server), and (most probably) changes to the BOINC infrastructure. The latest [http://www.vmware.com/support/developer/vix-api/vix16_reference/ VIX reference] page for !VixHost_Connect() mentions logging in anonymously as the current user on the current host, so it is possible that this is simply an oversight in the current release of VMWare Server.
 
 == Outstanding issues ==