*: (E4) Support for multiple network interfaces. These mutliple network interfaces may use different types of networking. Also a network interface may be present but disabled ( virtualization equivalent of no cable plugged in ).
+*: (E5) Support for running multiple virtual machines from a single execute node.
+
{subsection: Functional/Behavioral Requirements}
{subsubsection: Initialization}
*: (TBD) shall support the following networking capabilities
@@ -77,6 +79,14 @@
{endblockquote}
{section: Use Case Senarios (Tie views together) }
+*: Libvirt submission & Run
+
+*: Script submission & Run
+
+*: Pause & Resume
+
+*: Terminating a Job
+
*: Libvirt is a hypervisor abstraction layer. This means, libvirt can manage virtual machines intended for differnet hypervisors while giving a uniform, hypervisor independent interface to the interacting user/application. While condor interfaces with libvirt, this interface as of now is not hypervisor independent. Ideally, condor should be able to use libvirt to manage virtual machines intended for any hypervisor that libvirt supports, even if it is one that was not previously supported by libvirt while the condor installation was being coded.
*: Libvirt being a hypervisor abstraction layer, can also be viewed as a hypervisor. Libvirt has it's virtual machine description format which is a libvirt xml file. Condor users must therefore be given an option where they may submit a libvirt xml virtual machine description to condor. Condor must be capable of accepting this input and running the virtual machine on behalf of the user using libvirt.
@@ -86,7 +96,5 @@
*: The case of the user not caring about the choice of hypervisor: many hypervisors these days support the vmware standard vmdk disk images. Likewise, another incarnation of virtualization that is gaining popularity is virtual appliances which may be run on several different hypervisors. The user may be allowed to submit such hypervisor independent virtual machines in which case condor should pick the hypervisor for the jobs.
-*: The case of the user not caring about the choice of hypervisor: many hypervisors these days support the vmware standard vmdk disk images. Likewise, another incarnation of virtualization that is gaining popularity is virtual appliances which may be run on several different hypervisors. The user may be allowed to submit such hypervisor independent virtual machines in which case condor should pick the hypervisor for the jobs.
-
{section: Links }
http://libvirt.org/
