GlideinWMS The Glidein-based Workflow Management System

Search Results

GlideinWMS

Download

Current release

Release Type Release Version Release Date Download Link
Stable Series v2_7 April 02, 2013 [glideinWMS Factory] [glideinWMS Frontend] [glideinWMS full download] [Corral Frontend]
Development Series v3_0 April 5, 2012 [glideinWMS Factory] [glideinWMS Frontend] [glideinWMS full download] [Corral Frontend]

NOTE: UPGRADING TO CONDOR 7.8.2

Following information only applies to glideinwms deployments done using ini-based installer or rpms with one or more secondary schedds in wmspool and/or submit services. This does not apply to installations using traditional Q & A based glideinwms installer.

Ini-Installer:
  • If your wms pool and/or submit service has one or more secondary schedds and you want to upgrade to condor 7.8.2, we strongly recommend to do a fresh install of these services using the ini-installer to avoid triggering a bug in condor that corrupts job queues.
  • However if you still decide to upgrade condor for wms pool and/or submit services with one or more secondary schedds you need to perform following steps -
    1. Stop condor daemons before upgrading to new condor.
    2. Backup the spool area used by each condor schedd. To find spool area run following command with right condor in your environment. This will help in recovering your setup in case of any problem.
      condor_config_val -dump | grep -i "SPOOL ="
    3. After upgrading to condor 7.8.2 verify that the condor configuration has correct information for JOB_QUEUE_LOG for every secondary schedd. For example, every secondary schedd should have its JOB_QUEUE_LOG explicitly defined and separate from other schedds as follows -
      SCHEDD.SCHEDDJOBS2.JOB_QUEUE_LOG = $(SCHEDD.SCHEDDJOBS2.SPOOL)/job_queue.log
      SCHEDD.SCHEDDJOBS3.JOB_QUEUE_LOG = $(SCHEDD.SCHEDDJOBS3.SPOOL)/job_queue.log
      ...
      Failure to do so will corrupt the condor queues.
    4. Start condor daemons
RPMs:
  • If your wms pool and/or submit service has one or more secondary schedds and you want to upgrade to condor 7.8.2, we strongly recommend to do a fresh install of these services using the ini-installer to avoid triggering a bug in condor that corrupts job queues.
  • However if you still decide to upgrade condor for wms pool and/or submit services with one or more secondary schedds you need to perform following steps -
    1. Stop condor daemons before upgrading to new condor.
    2. Backup the spool area used by each condor schedd. To find spool area run following command with right condor in your environment. This will help in recovering your setup in case of any problem.
      condor_config_val -dump | grep -i "SPOOL ="
    3. Merge relevant changes to JOB_QUEUE_LOG based on the number of schedds you have from the condor config file /etc/condor/config.d/02_gwms_schedds.config.rpmnew to config file /etc/condor/config.d/02_gwms_schedds.config. For example, every secondary schedd should have its JOB_QUEUE_LOG explicitly defined and separate from other schedds as follows -
      SCHEDD.SCHEDDJOBS2.JOB_QUEUE_LOG = $(SCHEDD.SCHEDDJOBS2.SPOOL)/job_queue.log
      SCHEDD.SCHEDDJOBS3.JOB_QUEUE_LOG = $(SCHEDD.SCHEDDJOBS3.SPOOL)/job_queue.log
      ...
      Failure to do so will corrupt the condor queues.
    4. Start condor daemons

glideinWMS Frontend RPM

glideinWMS Frontend RPM is available for download from the OSG RPM repository. Refer to
OSG glideinwms frontend installation guide for details.

glideinWMS Factory RPM

glideinWMS Factory RPM is available for download from the OSG RPM repository. Refer to OSG glideinwms factory installation guide for details.

Downloading from Repository

The code is maintained in
GIT. To checkout the version from git, run following commands

git clone http://cdcvs.fnal.gov/projects/glideinwms
git checkout v2_6_3