We have found it useful to stress-test a release candidate by giving it to Igor Sfiligoi to run in =glideinWMS=.  This exercises a lot of Condor features that are important to OSG-type users: glidein, Condor-G, CE schedd, CCB.  Igor suggested that it would be a good idea of we could run this test in-house, and we agree, so we have set up the machinery to do so.  This document describes roughly how we installed it.

{section: High-level View}

*: *ghost-pool* - runs light-weight jobs on cluster nodes.  The setup is in /unsup/condor/ghost-pool.  Some nodes in CHTC also join the ghost pool.  These are configured in the CHTC cfengine.

*: *CE: vdt-itb.cs.wisc.edu* - an OSG CE that is part of the ITB (integration test bed).  This node will be referred to as the CE.  The schedd on this node is part of the ghost pool.  The jobmanager is vdt-itb.cs.wisc.edu/jobmanager-nfslitecondor.

*: *factory: c157.cs.wisc.edu* - the glideinWMS factory, installed in /data1/itb-stress.  It submits glideins to the CE.  This node is part of the GLOW pool (despite its domain name).  It normally runs condor jobs.  Turn off condor when doing a large-scale test.

*: *submit: c158.cs.wisc.edu* - the glideinWMS VO frontend, user job submission node, and collector tree for the glidein pool, all installed in /data1/itb-stress.  This node normally runs condor jobs.  Turn off condor when doing a large-scale test.


{section: glidein factory setup}

Go to c157.chtc.wisc.edu.  Install the factory in /data1/itb-stress.