Professional Documents
Culture Documents
Running Condor in A Virtual Environment With Colinux: Sumanth J.V
Running Condor in A Virtual Environment With Colinux: Sumanth J.V
Running Condor in A Virtual Environment With Colinux: Sumanth J.V
Sumanth J.V
(sumanth@cse.unl.edu)
University of Nebraska -
Lincoln
• Virtualization
Allows for better utilization
and is less intrusive.
• Picking a virtualization
solution
VMWare
Cooperative Linux
• Bridged Networking
Uses WinPcap.
Advantage: Simple setup.
Disadvantage: Requires a real IP.
• NAT
Uses a TAP-Win32 networking device.
Windows performs the NAT.
coLinux does not have a real IP.
Requires GCB or OpenVPN to handle inbound
connections.
OpenVPN does not open up as many ports as GCB
and works with Windows and other OSs too.
Other apps services like NFS can also work
behind a NAT with OpenVPN
Sumanth J.V, RCF/UNL, Condor We 11
ek 2006
coLinux Networking
• host_stats.sh
A simple script (on coLinux) to
connect to the monitoring
service.
Prints out the Total Load, Condor
Load and keyboard/mouse idle
time.
• HostOsLoad = 0.01
• CoLinuxLoad = 0.02
• HostOsKeyboardIdle = 25
Sumanth J.V, RCF/UNL, Condor We 13
ek 2006
Configuring Condor
• condor_config
Setup STARTD_CRON to
periodically execute
host_stats.sh
Suitably edit UWCS policy.
GCB stuff.
• Why not install Condor on
Windows also?
• gen_xml.exe
Determines the name of the required real
network adapter.
Generates MAC address for virtual network
device based on host’s IP.
Writes coLinux’s XML file.
• Non-Interactive coLinux install.
• Setup Windows services.
• Unzip disk images.
• Can perform complete install by popping in
an install CD.
• Template of this CD will be made available.
Sumanth J.V, RCF/UNL, Condor We 15
ek 2006
Acknowledgements