HTCondorWiki: Vm Universe

 
 {subsubsection: Submission}
 
-*: (F2) Submit side processing of different hypervisor specific vm formates need to be defined. This should be capable of building the VM's requirements and populating the classad. {Consensus still needed on what all goes into the classad. ?? }
+*: (F2) Submit side processing of different hypervisor specific vm formats need to be defined. This should be capable of building the VM's requirements and populating the classad. {Consensus still needed on what all goes into the classad. ?? }
 *::  Shall support submission of libvirt compatible .xml files
 *::: Can this be a frontend (e.g. condor_libvirt_submit) that generates the appropriate job submission file for Condor? Similar front ends could be developed for other formats (e.g. condor_ovf_submit).
 *::  VM_TYPE=script-managed, libvirt-managed (support multiple ones?)
@@ -121,5 +121,7 @@
 *:: Should these status codes be returned to the user?
 *:: If a classad is modified, should the user be notified? Should the user receive indications of what was modified? What are the security implications of providing that information?
 *: An interesting side effect of script managed virtual machine is that it is relatively straight forward to override and fill in attributes in any arbitrary way. For example, it would be possible for a script implementation to call out to a MAC address and IP address management system to assign MAC and IP addresses to machines. Some care is needed to recover if the script is unable to gather all the information necessary to launch a virtual machine.
+*:: That would be very useful. The problem of brokering and assigning MAC addresses would be simple. However, that of IP address management needs more pondering since the only fathomable way to do it is to have some kind of a daemon which speaks the DHCP language.
 *: Also note, "scripts" is a fairly loose term. It is entirely possible to implement scripts in compiled languages like C or C++, Java, or traditional scripting languages.
 *: Do VM universe jobs interact with job hooks or job wrappers? If so, how?
+*:: Within the current code, there's only two hooks that I can think of as pertinent: the job router hooks and the starter hooks. For both, there's no functionality support required from th part of the script / libvirt.