Condor

From Ogce

The Condor portlet uses Condor 6.8's BirdBath SOAP and WSDL enabled Collector and Schedd daemons. Condor does not need to be installed on the same machine as the portal server.

Condor Configuration

Please see the Condor documentation and the (now mostly obsolete) Birdbath Project site for more detailed instructions and security recommendations. We summarize the steps below.

1. Create the file /usr/local/condor/web
2. Grab the Schedd and Collector WSDL files from http://www.cs.wisc.edu/condor/birdbath/ . The easiest way is to use Unix's wget command.
3. Edit the condor_config file to add the following lines to the end:

 WEB_ROOT_DIR=$(RELEASE_DIR)/web
 ENABLE_SOAP = TRUE
 ALLOW_SOAP = */*
 ENABLE_WEB_SERVER = TRUE
 QUEUE_ALL_USERS_TRUSTED=TRUE

ALLOW_SOAP is used to specify the DNS name or IP address of machines that are allowed to use the SOAP interface. Note the sample setting allows all SOAP client connections, which is not recommended for production systems.

It is also convenient for testing purposes that you configure condor to submit jobs aggressively. In Section 3 of the condor_config file, set these options:

 START=TRUE
 SUSPEND=FALSE
 CONTINUE=TRUE
 PREEMPT=FALSE
 KILL=FALSE

See https://www-auth.cs.wisc.edu/lists/condor-users-rc/2005-February/msg00259.shtml for more information.

Portlet Configuration

The Condor Job Submission portlet is written with Java Server Faces and is converted into a portlet using the Apache JSF Portlet Bridge, so the relevant configuration parameters are in the file condor_job_submission/WEB-INF/faces-config.xml. Open this file with your favorite text editor and set the following property:

   <managed-property>
       <property-name>collectorUrl</property-name>
       <value>http://your.collector.host.name:9618</value>
   </managed-property>

Change "your.collector.host.name" to the name of the host where you installed your Condor Central Manager. This is the machine that runs the Collector and Negotiator daemons and is the machine that has the modified configuration properties above.

The portlet is now configured to use Condor to submit batch jobs to remote resources on your flock. You can edit faces-config.xml after deployment in the ogce-portal-only/portal_deploy directory, or you can edit it in the source tree at ogce-portal-only/portlets/condor-job-submission. Then recompile/redeploy with

 [shell> mvn clean install -f portlets/condor-job-submission/pom.xml

in the ogce-portal-only directory.

Screen Shots

The screen shot shows a sample form for submitting simple jobs. These are monitored at the bottom, and output files are available for download after the job completes.