Overview

Requirements

Unlike the Vanilla Condor portlet, the Condor-G portlet requires that you install Condor and the OGCE portal on the same server. Condor-G also requires Globus to be installed on the portal server.

Condor's BirdBath requires additional configuration, as described below. You must also manually insert classads describing your Globus resources into Condor's matchmaking system.

Condor-G Configuration

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

1. 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
   

   The SCHEDD_ARGS property sets the port number of the scheduler. 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.
2. Create and publish a Condor classad for each Globus resource that you want Condor-G to manage. These classads must be renewed frequently and so should be placed in a cron script. A sample classad is shown below.

   MyType = "Machine"
   TargetType = "Job"
   Name = "condorTest05"
   Machine = "condorTest05"
   gatekeeper_url = "login-co.ncsa.teragrid.org/jobmanager"
   UpdatesSequenced = 9
   CurMatches = 0
   Requirements = TARGET.JobUniverse == 9
   Rank = 0.000000
   CurrentRank = 0.000000
   OpSys = "LINUX"
   Arch = "INTEL"
   State = "Unclaimed"
   Activity = "Idle"
   LoadAvg = 0.000000
   Memory = 2048
   WantAdRevaluate = True
   StartdIpAddr = "129.79.216.5"
   

   The parameters all apply to the host of the Globus GRAM that you want to use, except for StartIpAddr, which should be the IP for your portal/condor-g host. The classad above should be placed in a file ("ncsa-cobalt-classad.txt") and advertised using the command

   condor_advertise UPDATE_STARTD_AD $HOME/ncsa-classad.txt 
   

Portlet Configuration

The Condor-G 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 /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 grid.