condor_historyfor example) are in the default path (
/usr/bin). If they are not, please see section Non-Standard Condor Host requirements (bare-bone installation):
# EPEL 5 (For RHEL 5, Documentation/Release3.CentOS 5, and SL 5) [root@client ~]$ curl -O https://dl.fedoraproject.org/pub/epel/epel-release-latest-5.noarch.rpm [root@client ~]$ rpm -Uvh epel-release-latest-5.noarch.rpm # EPEL 6 (For RHEL 6, Documentation/Release3.CentOS 6, and SL 6) [root@client ~]$ rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm # EPEL 7 (For RHEL 7, Documentation/Release3.CentOS 7, and SL 7) [root@client ~]$ rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpmWARNING: if you have your own mirror or configuration of the EPEL repository, you MUST verify that the OSG repository has a better yum priority than EPEL (details). Otherwise, you will have strange dependency resolution (depsolving) issues.
Choose the correct package name based on your operating systemís major version:
Install the Yum priorities package:
[root@client ~]$ yum install PACKAGE
PACKAGE with the package name from the previous step.
/etc/yum.conf has the following line in the
[main] section (particularly when using ROCKS), thereby enabling Yum plugins, including the priorities one:
plugins=1NOTE: If you do not have a required key you can force the installation using
yum install --nogpgcheck yum-priorities.
If you are upgrading from OSG 3.1 (or 3.2) to OSG 3.2 (or 3.3), remove the old OSG repository definition files and clean the Yum cache:
[root@client ~]$ yum clean all [root@client ~]$ rpm -e osg-release
This step ensures that local changes to
*.repo files will not block the installation of the new OSG repositories. After this step,
*.repo files that have been changed will exist in
/etc/yum.repos.d/ with the
*.rpmsave extension. After installing the new OSG repositories (the next step) you may want to apply any changes made in the
*.rpmsave files to the new
Install the OSG repositories using one of the following methods depending on your EL version:
For EL versions greater than EL5, install the files directly from
[root@client ~]$ rpm -Uvh URL
URL is one of the following:
For EL5, download the repo file and install it using the following:
[root@client ~]$ curl -O https://repo.grid.iu.edu/osg/3.2/osg-3.2-el5-release-latest.rpm [root@client ~]$ rpm -Uvh osg-3.2-el5-release-latest.rpm
[root@client ~]$ yum install gratia-probe-glideinwms
/etc/gratia/condor/ProbeConfig. First, edit the
ProbeNameto be a unique identifier for your GlideinWMS Submit host. There can be multiple probes (with different names) per site. If you haven't already, you should register your GlideinWMS submit host in OIM. Then you can use the name you used to register the resource.
ProbeName="condor:<hostname>" SiteName="HCC-GlideinWMW-Frontend"Next, turn the probe on by editing the
[root@client ~]$ condor_reconfig
$ service gratia-probes-cron start $ chkconfig --level 345 gratia-probes-cron on
probewith the name of your probe that you configured above. NOTE: Usage could be delayed up to a few hours after the job has completed.
MapUnknownToGroupto the ProbeConfig. In the file
/etc/gratia/condor/ProbeConfig, add the value after the
... SuppressGridLocalRecords="0" EnableProbe="1" MapUnknownToGroup="1" Title3="Tuning parameter" ...Further, if you want to record all usage as coming from a single VO, you can configure the probe to override the 'guessed' VO. In the below example, replace the Engage with a registered VO that you would like to report as. If you don't have a VO that you are affiliated with, you may use Engage.
... MapUnknownToGroup="1" MapGroupToRole="1" VOOverride="Engage" ...
/usr/bin), then you need to tell the probe where to find the Condor binaries. This can be done with a script with a special attribute in
CondorLocation. Point it to the location of the Condor install, such that
empty-condorin order to trick yum into believing you already have condor.
yum install empty-condor gratia-probe-condor
/etc/gratia/condor/ProbeConfig, the value of
DataFolder(near the bottom) needs to be the same as the Condor configuration variable
PER_JOB_HISTORY_DIR. You can get the value of
PER_JOB_HISTORY_DIRwith the command:
/etc/gratia/condor/ProbeConfig, and replace the OSG production host with your desired one:
... CollectorHost="gratia-osg-prod.opensciencegrid.org:80" SSLHost="gratia-osg-prod.opensciencegrid.org:443" SSLRegistrationHost="gratia-osg-prod.opensciencegrid.org:80" ...You can find more information about the content of the configuration file and how to change it in ProbeConfig and ProbeConfigCondor .