DoIT HTCondor Pool
Overview of HTCondor pools on DoIT resources.
1.0 HTCondor headend and puppet master
condor0.doit.wisc.edu is the headend of the DoIT HTCondor pool. It manages the resources made available for jobs and schedules them. This machine primarily takes linux jobs that overflow from CHTC. In addition, it pushes out linux VM images to windows hosts in the pool.
The linux machines in the pool are managed via puppet. condor0 is the puppet master for these nodes, making it easier to maintain the distributed infrastructure.
2.0 Linux Pool
2.1 Linux Pool dedicated worker nodes
- idc-wisc.net.wisc.edu (dynes project)
- fdt-wisc.net.wisc.edu (dynes project)
- fl-cssc-b217-7.net.wisc.edu (lab captivator)
2.2 Linux Pool virtual machine worker nodesIn order to prevent starvation to other vm's on the host, the VM worker nodes are typically provisioned with 1 or 2 less cpu cores than are usually available. In addition, the CPU shares are configured to low.
- condor1.lab.net.wisc.edu on esx2.lab.net.wisc.edu
- condor2.doit.wisc.edu on moxi-server
- condor3.lab.net.wisc.edu on bw-tester-1.lab.net.wisc.edu
- condor4.lab.net.wisc.edu on bw-tester-2.lab.net.wisc.edu
- condor5.lab.net.wisc.edu on bw-tester-2.lab.net.wisc.edu
- tbd on esx1.lab.net.wisc.edu
- tbd on esx-cssc-b217-4.net.wisc.edu
2.3 Staff workstation VM'sSome staff in Network Services run linux virtual machines on their apple workstations. These resources can also be added into the DoIT HTCondor pool. Optionally, these workstations can be configured to only run jobs at specific times of the day.
See Joining the DoIT HTCondor Pool for specific instructions.
3.0 Windows Pool
Kiosks and Infolabs around campus managed by the DoIT RaDS group are running the windows version of HTCondor. These machines then run a linux vm image (via the HTCondor vm "universe" feature) as their job when the machines are idle. These linux VM's then call home to a submit node at CHTC to find their work. So, effectively, we are running HTCondor inside of HTCondor.