On Tue, Mar 15, 2011 at 02:33:07PM -0500, Jaime Frey wrote:
On Mar 14, 2011, at 2:50 PM, Ian Main wrote:
On Fri, Mar 11, 2011 at 04:17:18PM -0500, John R. Dunning wrote:
Other tidbit that I didn't see: We have the ability to inject some small snippet of data at launch time, correct? For instance as a karg or something? I'm pretty sure we talked about this offline, but I want to make sure (a) the answer is yes, and (b) we build it into the api.
Actually I was just looking through the code and AFAICT this is only supported for Xen based VMs, not KVM. It would be easy enough to add to condor though.. but then we are getting into needing a modified condor again. Perhaps this line of development would be useful to upstream though?
Does libvirt provide a mechanism to do this? We'd be interested in adding this to Condor.
It does, but I've been corrected since.. you can basically pass in whatever libvirt/virsh XML you want so it's not necessary that we do it via a classad variable. At least there is a workaround by doing it this way. As Chris mentioned in a separate email you want to do this via SMBIOS extensions. You can see them here:
http://libvirt.org/formatdomain.html#elementsSysinfo
The other thing I noticed is that there is no way to override the architecture via condor. Eg run an i686 guest on x86_64 hardware.
You should be able to do this in your Condor submit file:
requirements = Arch =!= undefined
But does it ever make sense for Condor to restrict the possible execute machines to ones with matching architecture? I think I should take that behavior out of Condor.
Not sure I follow what you are saying, but the issue is that it will restrict the architecture of the machines but it's generally perfectly valid to start an i386 guest up in an x86_64 host, not the other way around though.
Ian