{section: Related Tickets}
Ticket #883: VM universe refactor {linebreak}
-Ticket #1090: Initial header proto for vm-gahp 2.0
{section: Goals and Objectives }
The vm-universe gives condor the ability to run virtual machines as a "job", these vm's can either run a dedicated task, spin up extra resources (which can be added to the existing pool), create a virtual pool.
@@ -12,16 +11,15 @@
{subsection: Engineering/Design Requirements}
*: (E1) The VM gahp should be made as lightweight and minimalistic as possible.
-*: (E2) The VM Gahp shall support script managed and libvirt managed virtual machines.
-*:: subsequently hypervisor specific capabilities should be supported. (e.g. ACPI)
+*: (E2) The VM Gahp shall support a pluggable hypervisor mechanism to allow for multiple technolgies. Primary support will be for libvirt - which can support most if not all hypervisors which one would care about.
-*: (E3) Support for multiple CPU's and hard disks (needs further description)
+*: (E3) Support for multiple CPU's and hard disks (needs further description) of what running a N-CPU job actually means on the host machine.
*: (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.
+*: (E5) Support for running multiple virtual machines and/or hypervisors from a single execute node.
-*: (E6) Administrators can allow/override/reject any virtual machine requirement requests. (e.g. limit memory size, reject MAC address settings, etc.)
+*: (E6) Administrators can allow/override/reject any virtual machine requirement requests. via script which "could" xsl transform the incoming xml (e.g. limit memory size, reject MAC address settings, etc.)
{subsection: Functional/Behavioral Requirements}
{subsubsection: Initialization}
