Difference: InstallUpgradeOSG (1 vs. 42)

Revision 42
Changes from r40 to r42
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 702 to 702
 

Currently (12/21/2017) this is running with only a small sub-cluster in 30-gip.ini (/etc/osg/config.d) and has about 40 WN slots backing it. The OIM Resource AGLT2_PROD is defined, but AGIS is broken and so no PandaQueue? can be cloned until January.
Changed:
<
<
Following multiple, initial cf-agent runs, the directions at this OSG URL were followed to set the machine going. Upon install, condor-cron is enabled to run, but none of rsv, condor-ce or condor were enabled. We found the following manual actions were required to start this gatekeeper going
>
>
Following multiple, initial cf-agent runs, the directions at this OSG URL were followed to set the machine going. This seems to devolve down to "yum install osg-ce-condor". Upon install, condor-cron is enabled to run, but none of rsv, condor-ce or condor were enabled. We found the following manual actions were required to start this gatekeeper going
 

  • systemctl enable rsv
  • systemctl enable condor-ce
Line: 719 to 719
 

Various submit tests were successfully performed.
Added:
>
>

Notes on installing osg 3.4 on gate02, April, 2018

The repo would not install from cfe, and was manually installed

AFTER THE FACT NOTE; CFENGINE WAS NOT PROPERLY CONFIGURED TO SAY THAT GATE02 WAS SL7, HENCE THIS ERROR IN SETTING UP THE REPO

Had to manually "yum install osg-version"

The rsv service does not need to run, but, we see that the "org.osg.general.vo-supported" probe is now deprecated (both gate01 and gate02)

Remembered to dump from old gate02, and re-copy to new gate02, the condor job plot files from /var/www/html/Monitoring
  • count_MP8_logs directory
  • count_logs directory
  • MPmon_count.log
  • count_jobs.log

From /opt/condor/scan, compile the .c program, and restore scanHistoryTime

The ruby install documented here does not work, ruby crashes

REMEMBER, run the rsv user cron once, manually, to generate a grid proxy.

Manually mount /pnfs after cfe adds it to /etc/fstab
 

CFEngine issues on initial gatekeeper build

The lines of policy in osg_ce_condor.cf where the cron-intervals are modified for 2 probes, do not work with the out-of-the-box rpms, becasue they do not take into account that the intervals are commented out. This should be fixed at some point.
Revision 40
Changes from r38 to r40
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 696 to 696
 

Added:
>
>

Clean install of OSG 3.4

In December, 2017, an SL7.4 gatekeeper, gate01.aglt2.org, was built from Cobbler, and utilizing a full install from cfengine3, including all OSG repos. This was set to use OSG 3.4 via resolved link from the generic rpm osg-3.4-el7-release-latest.rpm to osg-release-3.4-2.osg34.el7. So, Cobbler run to build the gatekeeper, cfengine3 runs, multiple times, until no errors are returned, to configure the gatekeeper.

Currently (12/21/2017) this is running with only a small sub-cluster in 30-gip.ini (/etc/osg/config.d) and has about 40 WN slots backing it. The OIM Resource AGLT2_PROD is defined, but AGIS is broken and so no PandaQueue? can be cloned until January.

Following multiple, initial cf-agent runs, the directions at this OSG URL were followed to set the machine going. Upon install, condor-cron is enabled to run, but none of rsv, condor-ce or condor were enabled. We found the following manual actions were required to start this gatekeeper going

  • systemctl enable rsv
  • systemctl enable condor-ce
  • systemctl enable condor
  • osg-configure -v
  • osg-configure -c
  • systemctl start rsv
  • systemctl start condor
  • systemctl start condor-ce
  • rsv-control --run --all-enabled
  • chkconfig -add gratia-probes-cron
  • chkconfig gratia-probes-cron on
  • service gratia-probes-cron start

Various submit tests were successfully performed.

CFEngine issues on initial gatekeeper build

The lines of policy in osg_ce_condor.cf where the cron-intervals are modified for 2 probes, do not work with the out-of-the-box rpms, becasue they do not take into account that the intervals are commented out. This should be fixed at some point.
  -- WenjingWu - 09 Jul 2008

Revision 38
Changes from r36 to r38
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 688 to 688
  Check that the http certs are owned by tomcat. Found false, so chown tomcat.tomcat /etc/grid-security/http/*.pem service tomcat6 start
Changed:
<
<
yum --enablerepo=osg install osg-info-services chkconfig --add osg-info-services chkconfig osg-info-services on service osg-info-services start
>
>

chkconfig --add gratia-probes-cron chkconfig gratia-probes-cron on service gratia-probes-cron start
 

Revision 36
Changes from r34 to r36
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 676 to 676
 

Manually edit in a gums server in /etc/lcmaps.db
Added:
>
>
[root@gate02 osg]# chkconfig gums-client-cron on [root@gate02 osg]# service gums-client-cron start Enabling periodic gums-host-cron: [ OK ] # Run it once manually [root@gate02 osg]# ! -f /var/lock/subsys/gums-host-cron? || /usr/bin/gums-host-cron

yum install tomcat6 chkconfig tomcat6 on cf-agent run Check that the http certs are owned by tomcat. Found false, so chown tomcat.tomcat /etc/grid-security/http/*.pem service tomcat6 start yum --enablerepo=osg install osg-info-services chkconfig --add osg-info-services chkconfig osg-info-services on service osg-info-services start
 

-- WenjingWu - 09 Jul 2008
Revision 34
Changes from r32 to r34
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 644 to 644
  reboot
Added:
>
>

Clean install of OSG 3.3

gate02 choked. So, a new VM was cloned from the old, it was Cobbler built, and then the following steps were undertaken to do a full osg 3.3 install. This resulted in OSG 3.3.23. For now, this is just a "history" dump. This left condor and condor-ce stopped.

   48  yum install yum-plugin-priorities
   50  rpm -Uvh https://repo.grid.iu.edu/osg/3.3/osg-3.3-el6-release-latest.rpm
   51  yum --enablerepo=osg-empty install empty-ca-certs
   54  yum --enablerepo=osg install condor
   56  yum --enablerepo=osg install osg-ce-condor
   60  mkdir /root/saves
   61  cp -ar /etc/condor/config.d /root/saves/condor_config.d
   64  cp -ar /etc/condor-ce/config.d /root/saves/condor-ce_config.d
   65  cp -ar /etc/osg/config.d /root/saves/osg_config.d
   67  yum --enablerepo=osg install rsv
   68  cf-agent -Kf failsafe.cf; cf-agent -K
   69  service cfengine3 stop
   75  cf-agent -Kf failsafe.cf; cf-agent -K
   82  service autofs start
   84  osg-configure -v
   87  reboot
   88  exit

   90  yum install ruby
   91  yum install rubygems
   92  yum install rubygem-json.x86_64 rubygem-pg
   93  yum install rubygem-activesupport.noarch
   94  gem install activerecord -v 2.3.18
   95  gem list

Manually edit in a gums server in /etc/lcmaps.db

  -- WenjingWu - 09 Jul 2008

Revision 32
Changes from r30 to r32
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 9 to 9
  For full Information of how to install OSG, please refer to this page OSGCE

For a short tuturial see: https://twiki.grid.iu.edu/bin/view/ReleaseDocumentation/ComputingElementHandsOn
Changed:
<
<
  • Most of our config should come over when you do extract_config in an upgrade (more below)
  • Ignore the parts of this tutorial regarding CA setup. Make symlinks as noted below.
  • authorization_method in config.ini is "prima"
  • Also ignore parts about configuring RSV and RSV certs on gate02 at least.
  • Needed host certs pushed automatically into /etc/grid-security from umopt1
>
>
  • Most of our config should come over when you do extract_config in an upgrade (more below)
  • Ignore the parts of this tutorial regarding CA setup. Make symlinks as noted below.
  • authorization_method in config.ini is "prima"
  • Also ignore parts about configuring RSV and RSV certs on gate02 at least.
  • Needed host certs pushed automatically into /etc/grid-security from umopt1
 

Changelog

Changed:
<
<
The following are the commands I used to install OSG100 on gate02.. there are some site-specific issues:
Updated May 12, 2009, for OSG101 install -- B.Ball
>
>
The following are the commands I used to install OSG100 on gate02.. there are some site-specific issues:
Updated May 12, 2009, for OSG101 install -- B.Ball
 
Changed:
<
<
Updated June 13, 2009, for OSG104 -- B.Ball
No changes required to fundamental procedure outlined below.
>
>
Updated June 13, 2009, for OSG104 -- B.Ball
No changes required to fundamental procedure outlined below.
 
Changed:
<
<
August 8 2009 - bmeekhof
Renamed topic, edited according to experience upgrading OSG 1.0.4 to OSG 1.2.0 on gate02 following tutorial linked.
>
>
August 8 2009 - bmeekhof
Renamed topic, edited according to experience upgrading OSG 1.0.4 to OSG 1.2.0 on gate02 following tutorial linked.
 
Changed:
<
<
August 23 2009 - bmeekhof
Updated after installation on gate01. Additional info about updating AFS installations of Pacman, OSGWN and opt/WLCG-client and setting CA locations.
>
>
August 23 2009 - bmeekhof
Updated after installation on gate01. Additional info about updating AFS installations of Pacman, OSGWN and opt/WLCG-client and setting CA locations.
 
Changed:
<
<
November 2, 2010 - Bob Ball
Upgrade OSG 1.2.6 to 1.2.15
>
>
November 2, 2010 - Bob Ball
Upgrade OSG 1.2.6 to 1.2.15
 
Changed:
<
<
January 17, 2011 - Bob Ball
Upgrade OSG 1.2.15 to 1.2.16
>
>
January 17, 2011 - Bob Ball
Upgrade OSG 1.2.15 to 1.2.16
 
Changed:
<
<
April 5, 2011 - Bob Ball
Upgrade OSG 1.2.16 to 1.2.19
>
>
April 5, 2011 - Bob Ball
Upgrade OSG 1.2.16 to 1.2.19
 
Changed:
<
<
October 21, 2011 - Bob Ball
Upgrade OSG 1.2.19 to 1.2.23
>
>
October 21, 2011 - Bob Ball
Upgrade OSG 1.2.19 to 1.2.23
 
Changed:
<
<
October 21, 2011 -- Bob Ball
Install OSGWN 1.2.23
>
>
October 21, 2011 -- Bob Ball
Install OSGWN 1.2.23
 
Changed:
<
<
November 7, 2011 -- Bob Ball
Upgrade OSG 1.2.23 to 1.2.24
>
>
November 7, 2011 -- Bob Ball
Upgrade OSG 1.2.23 to 1.2.24

November 15, 2011 -- Bob Ball
Upgrade OSG 1.2.24 to 1.2.25 on gate02, and apply 1.2.25 gratia security fix on gate01

March 8, 2012 -- Bob Ball
Upgrade OSG to 1.2.28 on both gate01 and on gate02.

February 27, 2016 -- Directions used most recently for an OSG 3.3 upgrade
 
Deleted:
<
<
November 15, 2011 -- Bob Ball
Upgrade OSG 1.2.24 to 1.2.25 on gate02, and apply 1.2.25 gratia security fix on gate01
 

Prepare for install

Line: 62 to 55
  vdt-control --off
Changed:
<
<
Logout to unexport the env variables or login a new shell.
>
>
Logout to unexport the env variables or login a new shell.
 

Set up the env variables.
Added:
>
>
  This is important, don't forget it or you'll be re-installing. Setting OLD_VDT_LOCATION ensures your old configuration gets pulled in, but also we will have to run "extract_config" later to setup config.ini.
Line: 76 to 70
 

Install the software

Install pyOpenSSL
Deleted:
<
<
"We have identified a reporting bug in OSG 1.2 that could impact accounting (for WLCG) and monitoring since it impacts the ability to publish RSV records to the GOC RSV database and WLCG SAM. The current monitoring system shows that all the Tier-2s running 1.2 have either fixed this problem or are aware of it. A VDT update will be available early next week.
 
Added:
>
>
"We have identified a reporting bug in OSG 1.2 that could impact accounting (for WLCG) and monitoring since it impacts the ability to publish RSV records to the GOC RSV database and WLCG SAM. The current monitoring system shows that all the Tier-2s running 1.2 have either fixed this problem or are aware of it. A VDT update will be available early next week.
 

The bug stems from a newly introduced dependency in the RSV Gratia probe on pyOpenSSL. If your site is already running pyOpenSSL, it should not be affected. If you are not running pyOpenSSL, this means that your site is not be reporting Gratia accounting data. The work around is to install pyOpenSSL. Alternatively, as noted above, this will be available in the a soon to be released VDT update. "
Line: 107 to 102
 

Source /afs/atlas.umich.edu/opt/pacman/setup.sh if you have not already.
Deleted:
<
<
  Please read LocalDQ2Tools#The_Installation_Procedure for information about updating this and what you have to do to remount the /opt volume as read-write in AFS.
Changed:
<
<
UPDATE: Or...use /afs/.atlas.umich.edu to use RW volume as documented below and fix the paths in files.
>
>
UPDATE: Or...use /afs/.atlas.umich.edu to use RW volume as documented below and fix the paths in files.
 

Probably should save a copy of current installation and delete existing files.
Changed:
<
<
Then install worker node and wlcg using pacman (note the "." in afs path to use RW volume, and note that we fix the paths up to use the RO volume in usage):
OSGWN updated May 25, 2010 to osg 1.2.9 version
>
>
Then install worker node and wlcg using pacman (note the "." in afs path to use RW volume, and note that we fix the paths up to use the RO volume in usage):
OSGWN updated May 25, 2010 to osg 1.2.9 version
 

 cd /afs/.atlas.umich.edu/OSGWN 
Line: 172 to 166
  pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:ManagedFork
Deleted:
<
<

  These instructions were not performed in upgrading to osg-1.2, not sure they are needed or if they are part of upgrade:
source $VDT_LOCATION/setup.sh
$VDT_LOCATION/vdt/setup/configure_globus_gatekeeper --managed-fork y --server y
Deleted:
<
<

 

Install Job Manager for condor
Added:
>
>
  Install in /opt/osg-1.2:
cd /opt/osg-1.2
Line: 186 to 179
  cd /opt/osg-1.2 pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:Globus-Condor-Setup
Changed:
<
<

>
>
  These instructions were not performed in upgrading to osg-1.2, not sure they are needed or if they are part of upgrade:
##uncomment this line in the condor.pm
vi $VDT_LOCATION/globus/lib/perl/Globus/GRAM/JobManager/condor.pm  
#    $requirements .= " && Arch == \"" . $description->condor_arch() . "\" ";  
Deleted:
<
<

 

Do post-install
Added:
>
>
 
source /opt/osg-1.2/setup.sh
vdt-post-install
Line: 207 to 200
 

gate02 is the machine which updates our AFS certs. It may be necessary to do the setupca command below if not upgrading. There is no longer a vdt-questions.sh to run (reference to it removed below).
Deleted:
<
<

  See the notes in the post-install/README file on CA-Certificates. Edit the value of cacerts_url in the configuration file at /opt/ost-1.2/vdt/etc/vdt-update-certs.conf
cacerts_url = http://software.grid.iu.edu/pacman/cadist/ca-certs-version
Line: 216 to 208
  source /opt/osg-1.2/setup.sh vdt-ca-manage setupca --location local --url osg
Deleted:
<
<

 
Deleted:
<
<

  At AGLT2 -- point the installation at our AFS certificates:
Line: 235 to 227
  ln -s /afs/atlas.umich.edu/OSG_certificates/certificates /opt/osg-1.2/globus/share/certificates ln -s /afs/atlas.umich.edu/OSG_certificates/certificates /opt/osg-1.2/globus/TRUSTED_CA
Deleted:
<
<

 

Configure authentication
Added:
>
>
  Copy auth files from post-install. The files will have the correct values as long as you set OLD_VDT_LOCATION before the installation.
Line: 295 to 290
 

Check your services, enable the ones you want with vdt-control --enable
Changed:
<
<
Turn off condor, turn on anything needed. Gate02 needs to run the cert and crl update services. I didn't need to do the vdt-register-service in an upgrade. This is for gate02:
>
>

Turn off condor, turn on anything needed. Gate02 needs to run the cert and crl update services. I didn't need to do the vdt-register-service in an upgrade. This is for gate02:
 
vdt-control --enable fetch-crl
vdt-control --enable vdt-update-certs
vdt-control --disable condor-cron
vdt-register-service --name condor-cron --disable
Changed:
<
<
NOTE: gate01 is the opposite. Enable condor-cron, disable fetch-crl and vdt-update-certs
>
>

NOTE: gate01 is the opposite. Enable condor-cron, disable fetch-crl and vdt-update-certs
 

Double check that it's all good. Our two gatekeepers are different in requirements. Gate02 needs these:
Line: 366 to 363
 

Modify crontab for root on gate02 (vdt-control should put these in but you will need to adjust timing)
Added:
>
>
  This applies to gate02 only.
Changed:
<
<
  • fetch-crl.cron should run every hour at 8 minutes after every hour
  • vdt-update-certs-wrapper should run at 12 minutes after every hour
>
>
  • fetch-crl.cron should run every hour at 8 minutes after every hour
  • vdt-update-certs-wrapper should run at 12 minutes after every hour
 
8 * * * * /opt/osg-1.2/fetch-crl/share/doc/fetch-crl-2.6.6/fetch-crl.cron
12 * * * * /opt/osg-1.2/vdt/sbin/vdt-update-certs-wrapper --vdt-install /opt/osg-1.2 --called-from-cron
Line: 385 to 382
 
Update various other scripts

I did not do 2) when updating to OSG 1.2.0.
Deleted:
<
<

1) Following directions here
Add this on a one-time only basis to /etc/security/limits.conf
globus hard nofile 16384

2) Still following those directions, add to GLOBUS_OPTIONS in /opt/OSG104/setup.sh
-Dorg.globus.wsrf.container.persistence.dir=/home/GRAM4_metadata
This directory is created with 777 permissions

 
Changed:
<
<

>
>
1) Following directions here
Add this on a one-time only basis to /etc/security/limits.conf
globus hard nofile 16384

2) Still following those directions, add to GLOBUS_OPTIONS in /opt/OSG104/setup.sh
-Dorg.globus.wsrf.container.persistence.dir=/home/GRAM4_metadata
This directory is created with 777 permissions
  3) Bring these startups in line
sed -i s/OSG104/osg-1.2/g /etc/init.d/gsisshd
Line: 413 to 402
  gate01 now employs the same setup.

Deleted:
<
<

 

Verify the site

Line: 582 to 577
 

On gate01, perform only the gratia fix outlined at https://ticket.grid.iu.edu/goc/viewer?id=11248
Added:
>
>

Upgrade to OSG 1.2.28

Upgrade following directions. No changes in condor.pm or in config.ini.
The srmcp-readwrite rsv probe required a second change, that perhaps should have been there all along. The change is shown in this output from the diff command:
[gate01:probes]# diff srmcp-srm-probe srmcp-srm-probe.orig
103c103
<     my $srmcp_cmd = "$o{'srmcpCmd'} -space_token=5904816 -streams_num=1 -srm_protocol_version=".
---
>     my $srmcp_cmd = "$o{'srmcpCmd'} -streams_num=1 -srm_protocol_version=".
109c109
<     $srmcp_cmd = "$o{'srmcpCmd'} -space_token=5904816 -streams_num=1 -srm_protocol_version=".
---
>     $srmcp_cmd = "$o{'srmcpCmd'} -streams_num=1 -srm_protocol_version=".

The metric interval changes made in the upgrade to version 1.2.24 were retained in this update and did not require re-implementation.

The rsv probe disable for gate02 made in the upgrade to version 1.2.23 was again performed.

Upgrade OSG 3.3

The HTCondor repo is installed, but not active, on aglbatch. From there we can see the URL for the repo is http://research.cs.wisc.edu/htcondor/yum/stable/rhel6/ so browse to there and download the needed rpms.

condor-8.4.11-1.el6.x86_64.rpm
condor-classads-8.4.11-1.el6.x86_64.rpm
condor-cream-gahp-8.4.11-1.el6.x86_64.rpm
condor-external-libs-8.4.11-1.el6.x86_64.rpm
condor-procd-8.4.11-1.el6.x86_64.rpm
condor-python-8.4.11-1.el6.x86_64.rpm

The test case is on gate03, but all gatekeepers are treated identically following confirmation of success on gate03.

# Stop cfengine
service cfengine3 stop

# Stop Condor without terminating the shadow/WN processing
condor_off -fast

# Update condor
cd /atlas/data08/ball/admin/condor_rpms_8.4.11
yum localupdate condor-8.4.11-1.el6.x86_64.rpm condor-classads-8.4.11-1.el6.x86_64.rpm \
condor-external-libs-8.4.11-1.el6.x86_64.rpm condor-procd-8.4.11-1.el6.x86_64.rpm \
condor-python-8.4.11-1.el6.x86_64.rpm condor-cream-gahp-8.4.11-1.el6.x86_64.rpm

# Update osg
yum --enablerepo=osg update

# Now, here, watch the yum output for .rpmnew files, check each one thoroughly to understand
# it, and make any needed cf3 changes to config files.  When all is happy....

# Run cf-agent to re-establish anything needing it
cf-agent -Kf failsafe.cf; cf-agent -K

# Verify the osg configuration is clean....
osg-configure -v

# Then apply it
osg-configure -c

# And then reboot.
reboot
  -- WenjingWu - 09 Jul 2008

Revision 30
Changes from r28 to r30
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 46 to 46
  October 21, 2011 -- Bob Ball
Install OSGWN 1.2.23
Added:
>
>
November 7, 2011 -- Bob Ball
Upgrade OSG 1.2.23 to 1.2.24

November 15, 2011 -- Bob Ball
Upgrade OSG 1.2.24 to 1.2.25 on gate02, and apply 1.2.25 gratia security fix on gate01
 

Prepare for install

Line: 563 to 568
  gate01 updated with one modification to the procedure. Before the last step, "vdt-control --on", a check of the rsv probes shows the same two probes as in the 1.2.19 update were once again enabled. Disabled them.
  • rsv-control --disable --host gate02.grid.umich.edu org.osg.gratia.condor org.osg.gratia.metric
Changed:
<
<
Both gate01 and gate02 were rebooted following the updates. Active rsv probes were run and the report was fully green.
>
>

Upgrade OSG 1.2.23 to OSG 1.2.24

Upgrade went smoothly on both gate keepers.

On gate01 the rsv metrics were again disabled. In addition, the global timeout was changed from 1200 to 720 seconds, and the srmcp-readwrite condor-cron interval was changed from "28 *" to "13,28,43,58 *". The following two files were edited to achieve this.
  • /opt/osg/osg-rsv/etc/rsv.conf (timeout)
  • /opt/osg/osg-rsv/meta/metrics/org.osg.srm.srmcp-readwrite.meta (periodicity)

Both gate01 and gate02 were rebooted following the updates. rsv probes that failed during the downtime were run and the report was fully green.

Upgrade OSG 1.2.24 to OSG 1.2.25

Upgrade only gate02 following directions. Total outage was approximately 20 minutes.

On gate01, perform only the gratia fix outlined at https://ticket.grid.iu.edu/goc/viewer?id=11248
 

-- WenjingWu - 09 Jul 2008
Revision 28
Changes from r26 to r28
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 43 to 43
  October 21, 2011 - Bob Ball
Upgrade OSG 1.2.19 to 1.2.23
Added:
>
>
October 21, 2011 -- Bob Ball
Install OSGWN 1.2.23
 

Prepare for install

turn off the existing OSG services
Line: 114 to 118
 

sed -i s/\.atlas\.umich\.edu/atlas\.umich\.edu/g `grep -RIl "\.atlas\.umich\.edu" *`
Added:
>
>
### NOTE: for the 10/21/2011 update to OSGWN, the OSGWN volume was ### remounted rw, all files were moved to the directory old_OSGWN, ### and the pacman command was run on an "empty" directory. ### ### The content of the new dccp/bin directory contained ONLY dccp, ### so all the old lsm files were copied from the old_OSGWN tree to ### the new location
  ln -s /afs/atlas.umich.edu/OSG_certificates/certificates globus/share/certificates ln -s /afs/atlas.umich.edu/OSG_certificates/certificates globus/TRUSTED_CA
Line: 543 to 555
 

Pre-upgrade note:

Directions here look straightforward. However, condor.pm must be modified as I understand it is changed in this release.
Added:
>
>

Post-upgrade note:

Modified condor.pm to not invoke the new condor_account_groups.pm . This was the only real change to condor.pm in this update, on both gate01 and gate02.

gate02 updates smooth and by the book

gate01 updated with one modification to the procedure. Before the last step, "vdt-control --on", a check of the rsv probes shows the same two probes as in the 1.2.19 update were once again enabled. Disabled them.
  • rsv-control --disable --host gate02.grid.umich.edu org.osg.gratia.condor org.osg.gratia.metric

Both gate01 and gate02 were rebooted following the updates. Active rsv probes were run and the report was fully green.
  -- WenjingWu - 09 Jul 2008

Revision 26
Changes from r24 to r26
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 37 to 37
  January 17, 2011 - Bob Ball
Upgrade OSG 1.2.15 to 1.2.16
Added:
>
>
April 5, 2011 - Bob Ball
Upgrade OSG 1.2.16 to 1.2.19

October 21, 2011 - Bob Ball
Upgrade OSG 1.2.19 to 1.2.23
 

Prepare for install

turn off the existing OSG services
Line: 524 to 530
 

This was a small step in versions. Instructions were therefore followed from this URL instead of the path followed for the 1.2.15 upgrade.
Added:
>
>

Upgrade OSG 1.2.16 to OSG 1.2.19

Smooth upgrade following directions. Two complications and one change.
  • print_local_time = TRUE (or anything) is no longer supported for rsv times in config.ini
  • The max value of SI00 is 5000, whereas we had 6700 for the sub-cluster where it was needed, so that is now reset to 5000
  • org.osg.gratia.condor and org.osg.gratia.metric probes were disabled for rsv on gate02. This is made possible by the new rsv-control command documented here.
    • rsv-control --disable --host gate02.grid.umich.edu org.osg.gratia.condor org.osg.gratia.metric
    • This was followed by a gate01 reboot that actually turned off these probes.

Upgrade OSG 1.2.19 to OSG 1.2.23

Pre-upgrade note:

Directions here look straightforward. However, condor.pm must be modified as I understand it is changed in this release.
  -- WenjingWu - 09 Jul 2008

Revision 24
Changes from r22 to r24
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Line: 34 to 34
  November 2, 2010 - Bob Ball
Upgrade OSG 1.2.6 to 1.2.15
Added:
>
>
January 17, 2011 - Bob Ball
Upgrade OSG 1.2.15 to 1.2.16
 

Prepare for install

turn off the existing OSG services
Line: 503 to 506
  configure-osg -v configure-osg -c
Added:
>
>
# Get rid of the gratia probes for gate02 running from gate01 cd /opt/osg/osg-rsv/submissions/probes mv gate02*gratia* /root/osg1.2.15_up

# Note that the srmcp-srm-probe is also different, having been modified to use # a dCache token-controlled area. Compare to /root/srmcp-srm-probe # Directory is /opt/osg/osg-rsv/bin/probes
  vdt-control --on

service condor start

Added:
>
>

Upgrade OSG 1.2.15 to OSG 1.2.16

Smooth upgrade. Also added in Rack 110 and 119 workers, and bl-5 workers, as sub-clusters 7-9.
 
Added:
>
>
This was a small step in versions. Instructions were therefore followed from this URL instead of the path followed for the 1.2.15 upgrade.
 

-- WenjingWu - 09 Jul 2008
Revision 22
Changes from r20 to r22
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"
Added:
>
>
 

Install or Upgrade OSG at AGLT2

The main difference between these instructions and the usual documentation is that we use worker node and wlcg-client installations in AFS as well as certificates in AFS which are kept up to date by gate02.
Line: 29 to 31
  August 23 2009 - bmeekhof
Updated after installation on gate01. Additional info about updating AFS installations of Pacman, OSGWN and opt/WLCG-client and setting CA locations.
Added:
>
>
November 2, 2010 - Bob Ball
Upgrade OSG 1.2.6 to 1.2.15
 

Prepare for install

turn off the existing OSG services
Line: 91 to 96
 

Probably should save a copy of current installation and delete existing files.
Changed:
<
<
Then install worker node and wlcg using pacman (note the "." in afs path to use RW volume, and note that we fix the paths up to use the RO volume in usage):
>
>
Then install worker node and wlcg using pacman (note the "." in afs path to use RW volume, and note that we fix the paths up to use the RO volume in usage):
OSGWN updated May 25, 2010 to osg 1.2.9 version
 
 cd /afs/.atlas.umich.edu/OSGWN 
pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:wn-client
Line: 420 to 427
  vdt-control --on osg-rsv
Added:
>
>

Upgrade OSG 1.2.6 to OSG 1.2.15

This upgrade was performed on November 2, 2010, and went very smoothly. Instructions were followed from this URL. This particular URL is linked from this master URL.

Pre-upgrade steps

# Save some files:
cd /root
mkdir osg1.2.15_up
crontab -l > osg1.2.15_up/crontab_l
vdt-control --list > osg1.2.15_up/vdt-control-list.txt
cp -p /opt/osg-1.2.6/osg/etc/config.ini osg1.2.15_up/
#
# Check some links so we can ensure they are correctly set at the end
[gate02:~]# ll /opt/osg/globus|grep TRUST
lrwxrwxrwx  1 root root    30 Apr 30 17:26 TRUSTED_CA -> /opt/certificates/certificates
[gate02:~]# ll /opt/osg/globus/share|grep cert
lrwxrwxrwx  1 root root    30 Apr 30 17:27 certificates -> /opt/certificates/certificates
#
[gate01:~]# ll /opt/osg/globus|grep TRUST
lrwxrwxrwx  1 root    50 Sep  2 12:32 TRUSTED_CA -> /afs/atlas.umich.edu/OSG_certificates/certificates/
[gate01:~]# ll /opt/osg/globus/share|grep cert
lrwxrwxrwx  1 root    50 Sep  2 12:32 certificates -> /afs/atlas.umich.edu/OSG_certificates/certificates/
#
#  Make sure that condor is cleaned.  Auto-pilots were previously stopped as this is
#    a scheduled outage.
condor_q -constr 'jobstatus==1'|grep " I "|awk '{print $1}'|xargs -n 1 condor_hold
condor_q -constr 'jobstatus==2'|grep " R "|awk '{print $1}'|xargs -n 1 condor_rm

service condor stop

export VDTSETUP_CONDOR_LOCATION=/opt/condor
export VDTSETUP_CONDOR_CONFIG=/opt/condor/etc/condor_config

Actual upgrade steps

This is a summary of the steps explained in the URL above.

cd VDT_LOCATION
source setup.sh
vdt-control --off
cp -a $VDT_LOCATION BACKUP_LOCATION

# Get the latest version of the vdt-updater script:
pacman -update VDT-Updater

# Note: If you do not yet have the updater script (look for $VDT_LOCATION/vdt/update/vdt-updater), 
#   then fetch it with this command:

pacman -get http://vdt.cs.wisc.edu/vdt_200_cache:VDT-Updater

cp -a $VDT_LOCATION NEW_BACKUP_LOCATION

vdt/update/vdt-updater

cp osg/etc/config.ini /tmp/config.ini-backup

pacman -update osg-version
pacman -update osg-config

cp  /tmp/config.ini-backup osg/etc/config.ini

# After updating, re-source the setup.sh file to load any changes in the environment:

source setup.sh

vdt-post-install

On a CE, you will also need to reconfigure your system

configure-osg -v
configure-osg -c

vdt-control --on

service condor start

 

-- WenjingWu - 09 Jul 2008
Revision 20
Changes from r18 to r20
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"

Install or Upgrade OSG at AGLT2

Line: 111 to 111
 

Added:
>
>
Check/fix the openssl path so it is as below (don't do install on host with /opt/globus so it picks up the right path):
/afs/atlas.umich.edu/OSGWN/globus/bin/openssl -> /usr/bin/openssl
/afs/atlas.umich.edu/WLCG-client/globus/bin/openssl -> /usr/bin/openssl
  Be sure to release the volumes:
vos release opt
Line: 400 to 406
 

Added:
>
>
Example of setting up RSV Probes
vdt-control --off osg-rsv

perl osg-rsv/bin/misc/cleanup-rsv.pl --reset

./osg-rsv/setup/configure_osg_rsv --user rsvuser --init --server y --ce-probes \
--ce-uri "gate01.aglt2.org gate02.grid.umich.edu"  --srm-probes --srm-uri "head01.aglt2.org" \ 
--srm-dir /pnfs/aglt2.org/dq2  --srm-webservice-path "srm/managerv2" --gratia --grid-type "OSG" \
--consumers --verbose --setup-for-apache --proxy /tmp/x509up_u55625

vdt-control --on osg-rsv
 

-- WenjingWu - 09 Jul 2008
Revision 18
Changes from r16 to r18
Line: 1 to 1
 
META TOPICPARENT name="OSGNotes"

Install or Upgrade OSG at AGLT2

Deleted:
<
<
These instructions are somewhat general but mostly relate to installation on gate02. Gate01 will have some differences which will be documented here when we find them out.
 
Changed:
<
<
For Full Information of how to Install OSG, please refer to this page OSGCE
>
>
The main difference between these instructions and the usual documentation is that we use worker node and wlcg-client installations in AFS as well as certificates in AFS which are kept up to date by gate02.

For full Information of how to install OSG, please refer to this page OSGCE
 

For a short tuturial see: https://twiki.grid.iu.edu/bin/view/ReleaseDocumentation/ComputingElementHandsOn
    Line: 25 to 26
      August 8 2009 - bmeekhof
    Renamed topic, edited according to experience upgrading OSG 1.0.4 to OSG 1.2.0 on gate02 following tutorial linked.
    Added:
    >
    >
    August 23 2009 - bmeekhof
    Updated after installation on gate01. Additional info about updating AFS installations of Pacman, OSGWN and opt/WLCG-client and setting CA locations.
     

    Prepare for install

    Line: 57 to 60
     

    (message dated Friday Aug 14 2009)
    Added:
    >
    >
    You'll need admin AFS tokens to do this. "kinit admin" and "aklog". Note that sometimes afs paths are .atlas.umich.edu when we need the RW volume.
     
    Install latest Pacman
    Changed:
    <
    <
    Install pacman in /opt:
    >
    >
    Install pacman (AFS):
     
    Changed:
    <
    <
    cd /opt wget wget http://physics.bu.edu/pacman/sample_cache/tarballs/pacman-latest.tar.gz tar xzvf pacman-latest.tar.gz source /opt/pacman-3.29/setup.sh
    >
    >
    cd /afs/.atlas.umich.edu/opt wget http://physics.bu.edu/pacman/sample_cache/tarballs/pacman-latest.tar.gz tar -xzvf pacman-latest.tar.gz rm pacman (remove old symlink) ln -s pacman-x.xx pacman rm pacman-latest.tar.gz vos release opt

    cd /afs/atlas.umich.edu/opt/pacman/

    source setup.sh (first pacman source wants you to be in local dir)
     
    Changed:
    <
    <
    Update AFS installations of OSG Worker Node and OSG WLCG client:
    >
    >
    Update AFS installations of OSG Worker Node and OSG WLCG client

    Source /afs/atlas.umich.edu/opt/pacman/setup.sh if you have not already.
      Please read LocalDQ2Tools#The_Installation_Procedure for information about updating this and what you have to do to remount the /opt volume as read-write in AFS.
    Changed:
    <
    <
    Probably should save a copy of current installation, delete existing files, and remake the directories.
    >
    >
    UPDATE: Or...use /afs/.atlas.umich.edu to use RW volume as documented below and fix the paths in files.
     
    Changed:
    <
    <
    Then install worker node and wlcg using pacman:
    >
    >
    Probably should save a copy of current installation and delete existing files.

    Then install worker node and wlcg using pacman (note the "." in afs path to use RW volume, and note that we fix the paths up to use the RO volume in usage):
     
    Changed:
    <
    <
    cd afs:/OSGWN
    >
    >
    cd /afs/.atlas.umich.edu/OSGWN
      pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:wn-client
    Changed:
    <
    <
    cd afs:/opt/WLCG-client
    >
    >
    sed -i s/\.atlas\.umich\.edu/atlas\.umich\.edu/g `grep -RIl "\.atlas\.umich\.edu" *`

    ln -s /afs/atlas.umich.edu/OSG_certificates/certificates globus/share/certificates ln -s /afs/atlas.umich.edu/OSG_certificates/certificates globus/TRUSTED_CA

    cd /afs/.atlas.umich.edu/opt/WLCG-client
      pacman -get http://www.mwt2.org/caches/osg-1.2:wlcg-client
    Added:
    >
    >
    sed -i s/\.atlas\.umich\.edu/atlas\.umich\.edu/g `grep -RIl "\.atlas\.umich\.edu" *`

    ln -s /afs/atlas.umich.edu/OSG_certificates/certificates globus/share/certificates ln -s /afs/atlas.umich.edu/OSG_certificates/certificates globus/TRUSTED_CA

    Be sure to release the volumes:
    vos release opt
    vos release OSGWN
     
    Deleted:
    <
    <
    (afs: = /afs/atlas.umich.edu)
     

    Install OSG
    Changed:
    <
    <
    Install OSG in /opt:
    >
    >
    Install OSG in /opt on Compute Elements (gate01,gate02):
     
    mkdir /opt/osg-1.2 ; cd /opt/osg-1.2
    pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:ce
    Line: 129 to 164
     

    Configure the software

    Changed:
    <
    <
    Configure certificates
    >
    >
    Configure certificates for OSG CE
     

    gate02 is the machine which updates our AFS certs. It may be necessary to do the setupca command below if not upgrading. There is no longer a vdt-questions.sh to run (reference to it removed below).
    Line: 164 to 199
     

    Configure authentication
    Changed:
    <
    <
    In latest upgrade to osg-1.2 I edited existing files in /etc/grid-security. I recommend copying from post-install instead. The files will have the correct values as long as you set OLD_VDT_LOCATION before the installation.
    >
    >
    Copy auth files from post-install. The files will have the correct values as long as you set OLD_VDT_LOCATION before the installation.
     

    cp /opt/osg-1.2/post-install/gsi-authz.conf /etc/grid-security/
    Line: 222 to 257
     

    Check your services, enable the ones you want with vdt-control --enable
    Turn off condor, turn on anything needed. Gate02 needs to run the cert and crl update services. I didn't need to do the vdt-register-service in an upgrade.
    Added:
    >
    >
    This is for gate02:
     
    vdt-control --enable fetch-crl
    vdt-control --enable vdt-update-certs
    vdt-control --disable condor-cron
    vdt-register-service --name condor-cron --disable
    
    Added:
    >
    >
    NOTE: gate01 is the opposite. Enable condor-cron, disable fetch-crl and vdt-update-certs
     
    Changed:
    <
    <
    Double check that it's all good:
    >
    >
    Double check that it's all good. Our two gatekeepers are different in requirements. Gate02 needs these:
     
    vdt-control --list
    [gate02:osg-1.2]# vdt-control --list
    Line: 251 to 288
      edg-mkgridmap | cron | do not enable
    Added:
    >
    >
    Gate01 needs these:
    [gate01:afs]# vdt-control --list
    Service                 | Type   | Desired State
    ------------------------+--------+--------------
    fetch-crl               | cron   | do not enable
    vdt-rotate-logs         | cron   | enable
    vdt-update-certs        | cron   | do not enable
    globus-gatekeeper       | inetd  | enable
    gsiftp                  | inetd  | enable
    mysql5                  | init   | enable
    globus-ws               | init   | do not enable
    gums-host-cron          | cron   | enable
    MLD                     | init   | enable
    condor-cron             | init   | enable
    apache                  | init   | enable
    tomcat-55               | init   | enable
    gratia-condor           | cron   | enable
    edg-mkgridmap           | cron   | do not enable
    osg-rsv                 | init   | enable
    
     
    Make sure mysql is started up before globus-ws
    This was not necessary in upgrade to osg-1.2. It appears to be fixed in the distribution - services started up in the correct order without modifications below. Init files from dist setup put mysql at 90 and tomcat-55,apache,globus-ws at order 99. Init file is named mysql5 now.
    Line: 267 to 326
      vdt-control --on
    Changed:
    <
    <
    Modify crontab for root (vdt-control should put these in but you will need to adjust timing)
    >
    >
    Modify crontab for root on gate02 (vdt-control should put these in but you will need to adjust timing)
    This applies to gate02 only.
     
    • fetch-crl.cron should run every hour at 8 minutes after every hour
    • vdt-update-certs-wrapper should run at 12 minutes after every hour
    8 * * * * /opt/osg-1.2/fetch-crl/share/doc/fetch-crl-2.6.6/fetch-crl.cron
    Changed:
    <
    <
    12 * * * * /opt/osg-1.2/vdt/sbin/vdt-update-certs-wrapper --vdt-install /opt/OSG101 --called-from-cron
    >
    >
    12 * * * * /opt/osg-1.2/vdt/sbin/vdt-update-certs-wrapper --vdt-install /opt/osg-1.2 --called-from-cron
     

    Make a symlink for OSG104 RSV probes from gate01
    Line: 344 to 404
     

    -- WenjingWu - 09 Jul 2008
    Changed:
    <
    <
    • config.ini: Config file /opt/osg-1.2/osg/etc/config.ini for reference
    >
    >

     
    Changed:
    <
    <
    META FILEATTACHMENT attachment="config.ini" attr="" comment="Config file /opt/osg-1.2/osg/etc/config.ini for reference" date="1249776590" name="config.ini" path="config.ini" size="3955" stream="config.ini" tmpFilename="/usr/tmp/CGItemp61256" user="BenMeekhof" version="1"
    >
    >
    META FILEATTACHMENT attachment="gate02-config.ini" attr="" comment="gate02:/opt/osg-1.2/etc/config.ini for reference" date="1251068567" name="gate02-config.ini" path="gate02-config.ini" size="3955" stream="gate02-config.ini" tmpFilename="/usr/tmp/CGItemp60974" user="BenMeekhof" version="1"
    META FILEATTACHMENT attachment="gate01-config.ini" attr="" comment="gate01:/opt/osg-1.2/osg/etc/config.ini for reference" date="1251068811" name="gate01-config.ini" path="gate01-config.ini" size="4673" stream="gate01-config.ini" tmpFilename="/usr/tmp/CGItemp61031" user="BenMeekhof" version="1"
     
    META TOPICMOVED by="BenMeekhof" date="1249755831" from="AGLT2.InstallOSG100OnGate02" to="AGLT2.InstallUpgradeOSG"
    Revision 16
    Changes from r14 to r16
    Line: 1 to 1
     
    META TOPICPARENT name="OSGNotes"

    Install or Upgrade OSG at AGLT2

    These instructions are somewhat general but mostly relate to installation on gate02. Gate01 will have some differences which will be documented here when we find them out.
    Line: 65 to 65
      tar xzvf pacman-latest.tar.gz source /opt/pacman-3.29/setup.sh
    Changed:
    <
    <
    Then install worker node in /opt using pacman (you can probably leave the URL out and just "-get osg-1.2:wn-client"):
    >
    >

    Update AFS installations of OSG Worker Node and OSG WLCG client: Please read LocalDQ2Tools#The_Installation_Procedure for information about updating this and what you have to do to remount the /opt volume as read-write in AFS.

    Probably should save a copy of current installation, delete existing files, and remake the directories.

    Then install worker node and wlcg using pacman:
     
    Changed:
    <
    <
    mkdir /opt/wn-1.2 ; cd /opt/wn-1.2
    >
    >
    cd afs:/OSGWN
      pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:wn-client
    Added:
    >
    >

    cd afs:/opt/WLCG-client pacman -get http://www.mwt2.org/caches/osg-1.2:wlcg-client
     
    Added:
    >
    >
    (afs: = /afs/atlas.umich.edu)
     

    Install OSG
    Install OSG in /opt:
    Line: 133 to 146
     

    At AGLT2 -- point the installation at our AFS certificates:

    Added:
    >
    >
     
    rm /opt/osg-1.2/globus/share/certificates
    Deleted:
    <
    <
    ln -s /afs/atlas.umich.edu/Certficates/certificates /opt/osg-1.2/globus/share/certificates
      rm /opt/osg-1.2/globus/TRUSTED_CA
    Added:
    >
    >
    gate02 (updates certificates, RW):
    ln -s /afs/atlas.umich.edu/Certficates/certificates /opt/osg-1.2/globus/share/certificates
      ln -s /afs/atlas.umich.edu/Certficates/certificates /opt/osg-1.2/globus/TRUSTED_CA
    Added:
    >
    >
    gate01 (RO):
    ln -s /afs/atlas.umich.edu/OSG_certificates/certificates /opt/osg-1.2/globus/share/certificates
    ln -s /afs/atlas.umich.edu/OSG_certificates/certificates /opt/osg-1.2/globus/TRUSTED_CA
    
     

    Configure authentication
    Revision 14
    Changes from r12 to r14
    Line: 1 to 1
     
    META TOPICPARENT name="OSGNotes"

    Install or Upgrade OSG at AGLT2

    These instructions are somewhat general but mostly relate to installation on gate02. Gate01 will have some differences which will be documented here when we find them out.
    Line: 49 to 49
     

    Install the software

    Added:
    >
    >
    Install pyOpenSSL
    "We have identified a reporting bug in OSG 1.2 that could impact accounting (for WLCG) and monitoring since it impacts the ability to publish RSV records to the GOC RSV database and WLCG SAM. The current monitoring system shows that all the Tier-2s running 1.2 have either fixed this problem or are aware of it. A VDT update will be available early next week.

    The bug stems from a newly introduced dependency in the RSV Gratia probe on pyOpenSSL. If your site is already running pyOpenSSL, it should not be affected. If you are not running pyOpenSSL, this means that your site is not be reporting Gratia accounting data. The work around is to install pyOpenSSL. Alternatively, as noted above, this will be available in the a soon to be released VDT update. "

    (message dated Friday Aug 14 2009)
     
    Install latest Pacman
    Install pacman in /opt:
    Line: 271 to 279
     

    3) Bring these startups in line

    Changed:
    <
    <
    sed -i s/OSG104/oag-1.2/g /etc/init.d/gsisshd
    >
    >
    sed -i s/OSG104/osg-1.2/g /etc/init.d/gsisshd
      sed -i s/OSG104/osg-1.2/g /etc/init.d/gsi_sshd sed -i s/OSG104/osg-1.2/g /etc/syslog-ng/syslog-ng.conf
    Revision 12
    Changes from r10 to r12
    Line: 1 to 1
     
    META TOPICPARENT name="OSGNotes"

    Install or Upgrade OSG at AGLT2

    These instructions are somewhat general but mostly relate to installation on gate02. Gate01 will have some differences which will be documented here when we find them out.
    Line: 221 to 221
      edg-mkgridmap | cron | do not enable
    Deleted:
    <
    <
    Start the services
    vdt-control --on
    
     
    Make sure mysql is started up before globus-ws
    Changed:
    <
    <
    This was not necessary in upgrade to osg-1.2. It may be fixed in the distribution - services started up in the correct order without modifications below.
    >
    >
    This was not necessary in upgrade to osg-1.2. It appears to be fixed in the distribution - services started up in the correct order without modifications below. Init files from dist setup put mysql at 90 and tomcat-55,apache,globus-ws at order 99. Init file is named mysql5 now.
     
    sed '/^# chkconfig:/c # chkconfig: 345 97 09' --in-place=.ORI /etc/rc.d/init.d/mysql
    sed '/^# chkconfig:/c # chkconfig: 345 98 04' --in-place=.ORI /etc/rc.d/init.d/globus-ws
    chkconfig mysql reset
    chkconfig globus-ws reset
    Changed:
    <
    <
    service globus-ws stop service globus-ws start
    >
    >

    Start the services
    vdt-control --on
     

    Modify crontab for root (vdt-control should put these in but you will need to adjust timing)
    Line: 274 to 274
      sed -i s/OSG104/oag-1.2/g /etc/init.d/gsisshd sed -i s/OSG104/osg-1.2/g /etc/init.d/gsi_sshd sed -i s/OSG104/osg-1.2/g /etc/syslog-ng/syslog-ng.conf
    Added:
    >
    >

    Note that for the first 2, the file /etc/sysconfig/vdt.conf is defined now, that specifies the location of the VDT, like so: export VDT_CURRENT=/opt/osg-1.2 The gsisshd and gsi_sshd startups now source this file, and then branch accordingly. syslog-ng.conf cannot do this, and so must be modified by hand.

    gate01 now employs the same setup.
     

    Line: 305 to 314
     

    -- WenjingWu - 09 Jul 2008
    Added:
    >
    >
    • config.ini: Config file /opt/osg-1.2/osg/etc/config.ini for reference

    META FILEATTACHMENT attachment="config.ini" attr="" comment="Config file /opt/osg-1.2/osg/etc/config.ini for reference" date="1249776590" name="config.ini" path="config.ini" size="3955" stream="config.ini" tmpFilename="/usr/tmp/CGItemp61256" user="BenMeekhof" version="1"
     
    META TOPICMOVED by="BenMeekhof" date="1249755831" from="AGLT2.InstallOSG100OnGate02" to="AGLT2.InstallUpgradeOSG"
    Revision 10
    Changes from r8 to r10
    Line: 1 to 1
     
    META TOPICPARENT name="OSGNotes"
    Changed:
    <
    <

    Install OSG100 On Gate02

    For Full Information of how to Install OSG100, please refer to this page OSGCE
    >
    >

    Install or Upgrade OSG at AGLT2

    These instructions are somewhat general but mostly relate to installation on gate02. Gate01 will have some differences which will be documented here when we find them out.

    For Full Information of how to Install OSG, please refer to this page OSGCE

    For a short tuturial see: https://twiki.grid.iu.edu/bin/view/ReleaseDocumentation/ComputingElementHandsOn
    • Most of our config should come over when you do extract_config in an upgrade (more below)
    • Ignore the parts of this tutorial regarding CA setup. Make symlinks as noted below.
    • authorization_method in config.ini is "prima"
    • Also ignore parts about configuring RSV and RSV certs on gate02 at least.
    • Needed host certs pushed automatically into /etc/grid-security from umopt1

    Changelog

     

    The following are the commands I used to install OSG100 on gate02.. there are some site-specific issues:
    Updated May 12, 2009, for OSG101 install -- B.Ball
    Line: 9 to 22
      Updated June 13, 2009, for OSG104 -- B.Ball
    No changes required to fundamental procedure outlined below.
    Changed:
    <
    <

    turn off the existing OSG services

    >
    >
    August 8 2009 - bmeekhof
    Renamed topic, edited according to experience upgrading OSG 1.0.4 to OSG 1.2.0 on gate02 following tutorial linked.

    Prepare for install

    turn off the existing OSG services
    Source the existing OSG install.
     
    Changed:
    <
    <
    source /opt/OSG100/setup.sh
    >
    >
    source /opt/OSG104/setup.sh
      vdt-control --off
    Changed:
    <
    <

    Prepare for install

    logout to unexport the env variables or login a new shell:
    1. set up the env variables.
    >
    >
    Logout to unexport the env variables or login a new shell.

    Set up the env variables.
    This is important, don't forget it or you'll be re-installing. Setting OLD_VDT_LOCATION ensures your old configuration gets pulled in, but also we will have to run "extract_config" later to setup config.ini.
     
    export VDTSETUP_CONDOR_LOCATION=/opt/condor
    export VDTSETUP_CONDOR_CONFIG=/opt/condor/etc/condor_config
    export VDT_GUMS_HOST=linat04.grid.umich.edu
    Changed:
    <
    <
    export OLD_VDT_LOCATION=/opt/OSG100/
    >
    >
    export OLD_VDT_LOCATION=/opt/OSG104/
     
    Changed:
    <
    <
    2 .install the software
    >
    >

    Install the software

    Install latest Pacman
    Install pacman in /opt:
     
    Deleted:
    <
    <
    # pacman re-used from upgrade of OSG080 to OSG100
      cd /opt wget wget http://physics.bu.edu/pacman/sample_cache/tarballs/pacman-latest.tar.gz tar xzvf pacman-latest.tar.gz
    Changed:
    <
    <
    source /opt/pacman-3.26/setup.sh # End of re-use mkdir /opt/OSG101 cd /opt/OSG101 pacman -get OSG:ce
    >
    >
    source /opt/pacman-3.29/setup.sh
     
    Changed:
    <
    <
    3. install Job Manager for condor
    >
    >
    Then install worker node in /opt using pacman (you can probably leave the URL out and just "-get osg-1.2:wn-client"):
     
    Changed:
    <
    <
    source /opt/OSG101/setup.sh pacman -get OSG:Globus-Condor-Setup ##uncomment this line in the condor.pm vi $VDT_LOCATION/globus/lib/perl/Globus/GRAM/JobManager/condor.pm # $requirements .= " && Arch == \"" . $description->condor_arch() . "\" ";
    >
    >
    mkdir /opt/wn-1.2 ; cd /opt/wn-1.2 pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:wn-client

    Install OSG
    Install OSG in /opt:
    mkdir /opt/osg-1.2 ; cd /opt/osg-1.2
    pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:ce
    
     
    Added:
    >
    >
    Install managedfork
    Install into /opt/osg-1.2:
    cd /opt/osg-1.2
    pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:ManagedFork
     
    Changed:
    <
    <
    4. install managedfork
    >
    >

    These instructions were not performed in upgrading to osg-1.2, not sure they are needed or if they are part of upgrade:

     
    Deleted:
    <
    <
    source /opt/OSG101/setup.sh pacman -get OSG:ManagedFork
      source $VDT_LOCATION/setup.sh $VDT_LOCATION/vdt/setup/configure_globus_gatekeeper --managed-fork y --server y
    Added:
    >
    >

     
    Changed:
    <
    <
    5. configure authentication
    >
    >
    Install Job Manager for condor
    Install in /opt/osg-1.2:
     
    Changed:
    <
    <
    cp /opt/OSG100/post-install/gsi-authz.conf /etc/grid-security/ cp /opt/OSG100/post-install/prima-authz.conf /etc/grid-security/ vi /etc/grid-security/prima-authz.conf logLevel info
    >
    >
    cd /opt/osg-1.2 pacman -allow trust-all-caches -get http://software.grid.iu.edu/osg-1.2:Globus-Condor-Setup

    These instructions were not performed in upgrading to osg-1.2, not sure they are needed or if they are part of upgrade:

    ##uncomment this line in the condor.pm
    vi $VDT_LOCATION/globus/lib/perl/Globus/GRAM/JobManager/condor.pm  
    #    $requirements .= " && Arch == \"" . $description->condor_arch() . "\" ";  
     
    Added:
    >
    >

     
    Changed:
    <
    <
    6. Configure certificates
    >
    >
    Do post-install
     
    Changed:
    <
    <
    # see the notes in the post-install/README file on CA-Certificates. # Edit the value of cacerts_url in the configuration file at # $VDT_LOCATION/vdt/etc/vdt-update-certs.conf # Use the OSG certificates . $VDT_LOCATION/vdt-questions.sh; $VDT_LOCATION/vdt/sbin/vdt-setup-ca-certificates # No, repoint to our AFS certificates rm /opt/OSG101/globus/share/certificates ln -s /afs/atlas.umich.edu/Certficates/certificates /opt/OSG101/globus/share/certificates rm /opt/OSG101/globus/TRUSTED_CA ln -s /afs/atlas.umich.edu/Certficates/certificates /opt/OSG101/globus/TRUSTED_CA vdt-control --enable vdt-update-certs # Delay this step, waiting to turn on everything at once #vdt-control --on vdt-update-certs
    >
    >
    source /opt/osg-1.2/setup.sh vdt-post-install

    Configure the software

    Configure certificates

    gate02 is the machine which updates our AFS certs. It may be necessary to do the setupca command below if not upgrading. There is no longer a vdt-questions.sh to run (reference to it removed below).

    See the notes in the post-install/README file on CA-Certificates. Edit the value of cacerts_url in the configuration file at /opt/ost-1.2/vdt/etc/vdt-update-certs.conf

    cacerts_url = http://software.grid.iu.edu/pacman/cadist/ca-certs-version
    
    cd /opt/osg-1.2
    source /opt/osg-1.2/setup.sh
    vdt-ca-manage setupca --location local --url osg
     
    Added:
    >
    >

     
    Changed:
    <
    <
    7. update osg-user-vo-map.txt
    >
    >

    At AGLT2 -- point the installation at our AFS certificates:

     
    Changed:
    <
    <
    vdt-control --enable gums-host-cron $VDT_LOCATION/gums/scripts/gums-host-cron
    >
    >
    rm /opt/osg-1.2/globus/share/certificates ln -s /afs/atlas.umich.edu/Certficates/certificates /opt/osg-1.2/globus/share/certificates rm /opt/osg-1.2/globus/TRUSTED_CA ln -s /afs/atlas.umich.edu/Certficates/certificates /opt/osg-1.2/globus/TRUSTED_CA
     
    Added:
    >
    >

    Configure authentication
    In latest upgrade to osg-1.2 I edited existing files in /etc/grid-security. I recommend copying from post-install instead. The files will have the correct values as long as you set OLD_VDT_LOCATION before the installation.
     
    Deleted:
    <
    <
    8. configure osg attributes
     
    Changed:
    <
    <
    # For update from OSG080 to OSG100 the following was performed #cd /opt/OSG100/monitoring #./configure-osg.py -e ###Using ./extracted-config.ini as the output ### you need to customize the extrated-config.ini #./configure-osg.py -c -f extracted-config.ini # # For OSG101, directions at this URL were followed: # https://twiki.grid.iu.edu/bin/view/ReleaseDocumentation/ComputeElementInstall source /opt/OSG101/setup.sh cd /opt/OSG101/monitoring cp /opt/OSG100/monitoring/config.ini . # Edit this file, changing OSG100 to OSG101 where it occurs ./configure-osg.py -v # Verify output of this step, then actually configure ./configure-osg.py -c
    >
    >
    cp /opt/osg-1.2/post-install/gsi-authz.conf /etc/grid-security/ cp /opt/osg-1.2/post-install/prima-authz.conf /etc/grid-security/ vi /etc/grid-security/prima-authz.conf logLevel info
     
    Added:
    >
    >
    Setup config.ini
    For an upgrade (be sure you set env vars before you started) you will need to run first:
    source /opt/osg-1.2/setup.sh (if not sourced already)
    extract-config
     
    Added:
    >
    >
    Copy extracted-config.ini to /opt/osg-1.2/osg/etc/config.ini and check it over. Then check that it verifies and then apply the config:
     
    Deleted:
    <
    <
    9. configure globus-ws
    1) Enable the services
     
    Changed:
    <
    <
    vdt-control --enable globus-ws mysql
    >
    >
    configure-osg -v configure-osg -c
     
    Changed:
    <
    <
    2) ..modify your sudo file
    >
    >
    Modify your sudo file
     
    Changed:
    <
    <
    visudo ## add/edit this part to /etc/sudo [gate02:monitoring]# more sudo-example.txt
    >
    >
      Runas_Alias GLOBUSUSERS = ALL, root
    Changed:
    <
    <
    daemon ALL=(GLOBUSUSERS) NOPASSWD: /opt/OSG100/globus/libexec/globus-gridmap-and-execute
    >
    >
    globus ALL=(GLOBUSUSERS) NOPASSWD: /opt/osg-1.2/globus/libexec/globus-gridmap-and-execute
      -g /etc/grid-security/grid-mapfile
    Changed:
    <
    <
    /opt/OSG101/globus/libexec/globus-job-manager-script.pl *
    >
    >
    /opt/osg-1.2/globus/libexec/globus-job-manager-script.pl *
     
    Changed:
    <
    <
    daemon ALL=(GLOBUSUSERS) NOPASSWD: /opt/OSG100/globus/libexec/globus-gridmap-and-execute
    >
    >
    globus ALL=(GLOBUSUSERS) NOPASSWD: /opt/osg-1.2/globus/libexec/globus-gridmap-and-execute
      -g /etc/grid-security/grid-mapfile
    Changed:
    <
    <
    /opt/OSG101/globus/libexec/globus-gram-local-proxy-tool *
    >
    >
    /opt/osg-1.2/globus/libexec/globus-gram-local-proxy-tool *
     
    Changed:
    <
    <
    daemon ALL=(GLOBUSUSERS)
    >
    >
    globus ALL=(GLOBUSUSERS)
      NOPASSWD:
    Changed:
    <
    <
    /opt/OSG101/globus/libexec/globus-job-manager-script.pl *
    >
    >
    /opt/osg-1.2/globus/libexec/globus-job-manager-script.pl *
     
    Changed:
    <
    <
    daemon ALL=(GLOBUSUSERS)
    >
    >
    globus ALL=(GLOBUSUSERS)
      NOPASSWD:
    Changed:
    <
    <
    /opt/OSG101/globus/libexec/globus-gram-local-proxy-tool *
    >
    >
    /opt/osg-1.2/globus/libexec/globus-gram-local-proxy-tool *
     
    Deleted:
    <
    <

    modify "daemon" to "globus", because we use the account "globus" to run globus-ws,
     
    Changed:
    <
    <
    3) make sure under /etc/grid-security, both containercert.pem and containerkey.pem belong to the same user globus..
    >
    >
    Check perms on containercert/key
    Make sure under /etc/grid-security, both containercert.pem and containerkey.pem belong to the same user globus..
     
    gate02:monitoring]# ls -l  /etc/grid-security/container*|grep -v old
    -r--r--r--  1 globus osg 1302 Jul  9 11:43 /etc/grid-security/containercert.pem
    -r--------  1 globus osg  887 Jul  9 11:43 /etc/grid-security/containerkey.pem
    
    Changed:
    <
    <
    10. start the services
    >
    >
    Check your services, enable the ones you want with vdt-control --enable
    Turn off condor, turn on anything needed. Gate02 needs to run the cert and crl update services. I didn't need to do the vdt-register-service in an upgrade.
     
    Changed:
    <
    <
    ##disable services you dont want to run
    >
    >
    vdt-control --enable fetch-crl vdt-control --enable vdt-update-certs
      vdt-control --disable condor-cron vdt-register-service --name condor-cron --disable
    Added:
    >
    >

    Double check that it's all good:
      vdt-control --list
    Changed:
    <
    <
    vdt-control --on
    >
    >
    [gate02:osg-1.2]# vdt-control --list Service | Type | Desired State

    --------+--------------

    fetch-crl | cron | enable vdt-rotate-logs | cron | enable vdt-update-certs | cron | enable globus-gatekeeper | inetd | enable gsiftp | inetd | enable mysql5 | init | enable globus-ws | init | enable gums-host-cron | cron | enable MLD | init | do not enable condor-cron | init | do not enable apache | init | enable tomcat-55 | init | enable gratia-condor | cron | enable edg-mkgridmap | cron | do not enable
     
    Added:
    >
    >
    Start the services
    vdt-control --on
     
    Changed:
    <
    <
    11. make sure mysql is started up before globus-ws
    >
    >
    Make sure mysql is started up before globus-ws
    This was not necessary in upgrade to osg-1.2. It may be fixed in the distribution - services started up in the correct order without modifications below.
     
    sed '/^# chkconfig:/c # chkconfig: 345 97 09' --in-place=.ORI /etc/rc.d/init.d/mysql
    sed '/^# chkconfig:/c # chkconfig: 345 98 04' --in-place=.ORI /etc/rc.d/init.d/globus-ws
    Line: 170 to 237
      service globus-ws start
    Changed:
    <
    <
    12. Modify crontab for root
    1) fetch-crl.cron should run every hour at 8 minutes after every hour
    2) vdt-update-certs-wrapper should run at 12 minutes after every hour
    >
    >
    Modify crontab for root (vdt-control should put these in but you will need to adjust timing)
    • fetch-crl.cron should run every hour at 8 minutes after every hour
    • vdt-update-certs-wrapper should run at 12 minutes after every hour
    8 * * * * /opt/osg-1.2/fetch-crl/share/doc/fetch-crl-2.6.6/fetch-crl.cron
    12 * * * * /opt/osg-1.2/vdt/sbin/vdt-update-certs-wrapper --vdt-install /opt/OSG101 --called-from-cron
    

    Make a symlink for OSG104 RSV probes from gate01
    It won't find this binary if you don't do the below:
     
    Changed:
    <
    <
    8 * * * * /opt/OSG101/fetch-crl/share/doc/fetch-crl-2.6.6/fetch-crl.cron 12 * * * * /opt/OSG101/vdt/sbin/vdt-update-certs-wrapper --vdt-install /opt/OSG101 --called-from-cron
    >
    >
    ln -s /opt/osg-1.2/osg/bin/osg-version /opt/osg-1.2/osg-version
     
    Changed:
    <
    <
    13. Update various other scripts
    1) Following directions here
    >
    >
    Update various other scripts

    I did not do 2) when updating to OSG 1.2.0.

    1) Following directions here

      Add this on a one-time only basis to /etc/security/limits.conf
    globus hard nofile 16384
    Added:
    >
    >

     
    Changed:
    <
    <
    2) Still following those directions, add to GLOBUS_OPTIONS in /opt/OSG101/setup.sh
    >
    >

    2) Still following those directions, add to GLOBUS_OPTIONS in /opt/OSG104/setup.sh

      -Dorg.globus.wsrf.container.persistence.dir=/home/GRAM4_metadata
    This directory is created with 777 permissions
    Added:
    >
    >

    3) Bring these startups in line

    sed -i s/OSG104/oag-1.2/g /etc/init.d/gsisshd
    sed -i s/OSG104/osg-1.2/g /etc/init.d/gsi_sshd
    sed -i s/OSG104/osg-1.2/g /etc/syslog-ng/syslog-ng.conf
    

    Verify the site

    Do these as a normal user with your grid cert.
     
    Deleted:
    <
    <
    3) Bring these startups in line
     
    Changed:
    <
    <
    sed -i s/OSG100/OSG101/g /etc/init.d/gsisshd sed -i s/OSG100/OSG101/g /etc/init.d/gsi_sshd sed -i s/OSG100/OSG101/g /etc/syslog-ng/syslog-ng.conf
    >
    >
    source /opt/osg-1.2/setup.sh grid-proxy-init cd /opt/osg-1.2/verify ./site_verify.pl
     
    Changed:
    <
    <
    14. some commands to verify the services:
    >
    >
    Some commands to verify the services:
     
    grid-proxy-init
    ##verify managedfork
    Line: 208 to 303
     

    Deleted:
    <
    <

      -- WenjingWu - 09 Jul 2008
    Added:
    >
    >
     
    META TOPICMOVED by="BenMeekhof" date="1249755831" from="AGLT2.InstallOSG100OnGate02" to="AGLT2.InstallUpgradeOSG"
    Revision 8
    Changes from r6 to r8
    Line: 1 to 1
     
    META TOPICPARENT name="OSGNotes"

    Install OSG100 On Gate02

    For Full Information of how to Install OSG100, please refer to this page OSGCE
    Line: 6 to 6
      The following are the commands I used to install OSG100 on gate02.. there are some site-specific issues:
    Updated May 12, 2009, for OSG101 install -- B.Ball
    Added:
    >
    >
    Updated June 13, 2009, for OSG104 -- B.Ball
    No changes required to fundamental procedure outlined below.
     

    turn off the existing OSG services

    source /opt/OSG100/setup.sh
    Line: 209 to 212
     

    -- WenjingWu - 09 Jul 2008
    Added:
    >
    >
    META TOPICMOVED by="BenMeekhof" date="1249755831" from="AGLT2.InstallOSG100OnGate02" to="AGLT2.InstallUpgradeOSG"
    Revision 6
    Changes from r4 to r6
    Line: 1 to 1
     
    META TOPICPARENT name="OSGNotes"

    Install OSG100 On Gate02

    For Full Information of how to Install OSG100, please refer to this page OSGCE
    Changed:
    <
    <
    The following are the commands I used to install OSG100 on gate02.. there are some site-specific issues:
    >
    >
    The following are the commands I used to install OSG100 on gate02.. there are some site-specific issues:
    Updated May 12, 2009, for OSG101 install -- B.Ball
     

    turn off the existing OSG services

    Changed:
    <
    <
    source /opt/OSG.old/setup.sh
    >
    >
    source /opt/OSG100/setup.sh
      vdt-control --off
    Line: 17 to 18
     
    export VDTSETUP_CONDOR_LOCATION=/opt/condor
    export VDTSETUP_CONDOR_CONFIG=/opt/condor/etc/condor_config
    Changed:
    <
    <
    export VDT_GUMS_HOST=linat02.grid.umich.edu export OLD_VDT_LOCATION=/opt/OSG080/
    >
    >
    export VDT_GUMS_HOST=linat04.grid.umich.edu export OLD_VDT_LOCATION=/opt/OSG100/
     

    2 .install the software
    Added:
    >
    >
    # pacman re-used from upgrade of OSG080 to OSG100
      cd /opt wget wget http://physics.bu.edu/pacman/sample_cache/tarballs/pacman-latest.tar.gz tar xzvf pacman-latest.tar.gz source /opt/pacman-3.26/setup.sh
    Changed:
    <
    <
    mkdir /opt/OSG100 cd /opt/OSG100
    >
    >
    # End of re-use mkdir /opt/OSG101 cd /opt/OSG101
      pacman -get OSG:ce
    3. install Job Manager for condor
    Changed:
    <
    <
    source /opt/OSG100/setup.sh
    >
    >
    source /opt/OSG101/setup.sh
      pacman -get OSG:Globus-Condor-Setup ##uncomment this line in the condor.pm vi $VDT_LOCATION/globus/lib/perl/Globus/GRAM/JobManager/condor.pm
    Line: 43 to 46
     

    4. install managedfork
    Changed:
    <
    <
    source /opt/OSG100/setup.sh
    >
    >
    source /opt/OSG101/setup.sh
      pacman -get OSG:ManagedFork source $VDT_LOCATION/setup.sh $VDT_LOCATION/vdt/setup/configure_globus_gatekeeper --managed-fork y --server y
    Line: 55 to 58
      cp /opt/OSG100/post-install/prima-authz.conf /etc/grid-security/ vi /etc/grid-security/prima-authz.conf logLevel info
    Deleted:
    <
    <
    rm /opt/OSG100/globus/share/certificates ln -s /afs/atlas.umich.edu/Certficates/certificates-37-1 /opt/OSG100/globus/share/certificates
     
    Changed:
    <
    <
    6. update osg-user-vo-map.txt
    >
    >
    6. Configure certificates
     
    Changed:
    <
    <
    vdt-control --enable gums-host-cron osg-rsv
    >
    >
    # see the notes in the post-install/README file on CA-Certificates. # Edit the value of cacerts_url in the configuration file at # $VDT_LOCATION/vdt/etc/vdt-update-certs.conf # Use the OSG certificates . $VDT_LOCATION/vdt-questions.sh; $VDT_LOCATION/vdt/sbin/vdt-setup-ca-certificates # No, repoint to our AFS certificates rm /opt/OSG101/globus/share/certificates ln -s /afs/atlas.umich.edu/Certficates/certificates /opt/OSG101/globus/share/certificates rm /opt/OSG101/globus/TRUSTED_CA ln -s /afs/atlas.umich.edu/Certficates/certificates /opt/OSG101/globus/TRUSTED_CA vdt-control --enable vdt-update-certs # Delay this step, waiting to turn on everything at once #vdt-control --on vdt-update-certs

    7. update osg-user-vo-map.txt
    vdt-control --enable gums-host-cron
      $VDT_LOCATION/gums/scripts/gums-host-cron
    Changed:
    <
    <

    7. configure osg attributes

    >
    >
    8. configure osg attributes
     
    Changed:
    <
    <
    cd /opt/OSG100/monitoring ./configure-osg.py -e ##Using ./extracted-config.ini as the output ## you need to customize the extrated-config.ini ./configure-osg.py -c -f extracted-config.ini
    >
    >
    # For update from OSG080 to OSG100 the following was performed #cd /opt/OSG100/monitoring #./configure-osg.py -e ###Using ./extracted-config.ini as the output ### you need to customize the extrated-config.ini #./configure-osg.py -c -f extracted-config.ini # # For OSG101, directions at this URL were followed: # https://twiki.grid.iu.edu/bin/view/ReleaseDocumentation/ComputeElementInstall source /opt/OSG101/setup.sh cd /opt/OSG101/monitoring cp /opt/OSG100/monitoring/config.ini . # Edit this file, changing OSG100 to OSG101 where it occurs ./configure-osg.py -v # Verify output of this step, then actually configure ./configure-osg.py -c
     
    Changed:
    <
    <
    8. configure globus-ws
    1) make sure mysql is started up before globus-ws
    >
    >
    9. configure globus-ws
    1) Enable the services
     
    vdt-control --enable globus-ws mysql
    Deleted:
    <
    <
    sed '/^# chkconfig:/c # chkconfig: 345 97 09' --in-place=.ORI /etc/rc.d/init.d/mysql sed '/^# chkconfig:/c # chkconfig: 345 98 04' --in-place=.ORI /etc/rc.d/init.d/globus-ws chkconfig mysql reset chkconfig globus-ws reset
     

    2) ..modify your sudo file
    visudo
    Changed:
    <
    <
    ## add this part to /etc/sudo
    >
    >
    ## add/edit this part to /etc/sudo
      [gate02:monitoring]# more sudo-example.txt Runas_Alias GLOBUSUSERS = ALL, root

    daemon ALL=(GLOBUSUSERS) NOPASSWD: /opt/OSG100/globus/libexec/globus-gridmap-and-execute -g /etc/grid-security/grid-mapfile
    Changed:
    <
    <
    /opt/OSG100/globus/libexec/globus-job-manager-script.pl *
    >
    >
    /opt/OSG101/globus/libexec/globus-job-manager-script.pl *
     

    daemon ALL=(GLOBUSUSERS) NOPASSWD: /opt/OSG100/globus/libexec/globus-gridmap-and-execute -g /etc/grid-security/grid-mapfile
    Changed:
    <
    <
    /opt/OSG100/globus/libexec/globus-gram-local-proxy-tool *
    >
    >
    /opt/OSG101/globus/libexec/globus-gram-local-proxy-tool *
     

    daemon ALL=(GLOBUSUSERS) NOPASSWD:
    Changed:
    <
    <
    /opt/OSG100/globus/libexec/globus-job-manager-script.pl *
    >
    >
    /opt/OSG101/globus/libexec/globus-job-manager-script.pl *
     

    daemon ALL=(GLOBUSUSERS) NOPASSWD:
    Changed:
    <
    <
    /opt/OSG100/globus/libexec/globus-gram-local-proxy-tool *
    >
    >
    /opt/OSG101/globus/libexec/globus-gram-local-proxy-tool *
     

    modify "daemon" to "globus", because we use the account "globus" to run globus-ws,
    Line: 121 to 147
      -r-------- 1 globus osg 887 Jul 9 11:43 /etc/grid-security/containerkey.pem
    Changed:
    <
    <
    9. start the services
    >
    >
    10. start the services
     
    ##disable services you dont want to run
    vdt-control --disable condor-cron
    Line: 131 to 157
     

    Changed:
    <
    <
    10. some commands to verify the services:
    >
    >
    11. make sure mysql is started up before globus-ws
    sed '/^# chkconfig:/c # chkconfig: 345 97 09' --in-place=.ORI /etc/rc.d/init.d/mysql
    sed '/^# chkconfig:/c # chkconfig: 345 98 04' --in-place=.ORI /etc/rc.d/init.d/globus-ws
    chkconfig mysql reset
    chkconfig globus-ws reset
    service globus-ws stop
    service globus-ws start
    

    12. Modify crontab for root
    1) fetch-crl.cron should run every hour at 8 minutes after every hour
    2) vdt-update-certs-wrapper should run at 12 minutes after every hour
    8 * * * * /opt/OSG101/fetch-crl/share/doc/fetch-crl-2.6.6/fetch-crl.cron
    12 * * * * /opt/OSG101/vdt/sbin/vdt-update-certs-wrapper --vdt-install /opt/OSG101 --called-from-cron
    

    13. Update various other scripts
    1) Following directions here
    Add this on a one-time only basis to /etc/security/limits.conf
    globus hard nofile 16384

    2) Still following those directions, add to GLOBUS_OPTIONS in /opt/OSG101/setup.sh
    -Dorg.globus.wsrf.container.persistence.dir=/home/GRAM4_metadata
    This directory is created with 777 permissions

    3) Bring these startups in line
    sed -i s/OSG100/OSG101/g /etc/init.d/gsisshd
    sed -i s/OSG100/OSG101/g /etc/init.d/gsi_sshd
    sed -i s/OSG100/OSG101/g /etc/syslog-ng/syslog-ng.conf
    

    14. some commands to verify the services:
     
    grid-proxy-init
    ##verify managedfork
    Revision 4
    Changes from r2 to r4
    Line: 1 to 1
     
    META TOPICPARENT name="OSGNotes"

    Install OSG100 On Gate02

    For Full Information of how to Install OSG100, please refer to this page OSGCE
    Line: 12 to 12
     

    Prepare for install

    Changed:
    <
    <
    logout to unexport the env variables in a new shell:
    1. set up the env varaibles.
    >
    >
    logout to unexport the env variables or login a new shell:
    1. set up the env variables.
     
    export VDTSETUP_CONDOR_LOCATION=/opt/condor
    export VDTSETUP_CONDOR_CONFIG=/opt/condor/etc/condor_config
    Revision 2
    09 Jul 2008 - WenjingWu
    Line: 1 to 1
     
    META TOPICPARENT name="OSGNotes"
    Deleted:
    <
    <
     

    Install OSG100 On Gate02

    Changed:
    <
    <
    For Full Information of how to Install OSG100, please refer to this page [[https://twiki.grid.iu.edu/twiki/bin/view/ReleaseDocumentation/ComputeElementInstall]OSGCE]
    >
    >
    For Full Information of how to Install OSG100, please refer to this page OSGCE
     

    The following are the commands I used to install OSG100 on gate02.. there are some site-specific issues:
     
    This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
    Ideas, requests, problems regarding Foswiki? Send feedback