Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1) Before starting a new install, set up the environment variables:

RHEL4-32 bit:  built on atlas-prod02.slac.stanford.edu
               pacman version = 3.26
               AFS: /afs/slac/g/atlas/d/  (currently soft linked to /b/)

Code Block

export PATH=/bin:/usr/bin:/usr/etc:/usr/afsws/bin:/usr/afsws/etc:/usr/bin/X11:.
.

...

 /afs/slac/g/atlas/packages/pacman/3.26/setup.sh

RHEL5-32 bit:  built on atlas-prod05.slac.stanford.edu

               pacman version = 3.29
               AFS: /afs/slac/g/atlas/c/
               For some reason, it's necessary to unset PYTHONPATH               

Code Block

export PATH=/bin:/usr/bin:/usr/etc:/usr/afsws/bin:/usr/afsws/etc:/usr/bin/X11:.

...


unset PYTHONPATH

...


. /afs/slac/g/atlas/packages/pacman/3.29/setup.sh

-----------------------------------------------------

2) Go to the target release partitions, /c/ or /d/.

Code Block

...


cd /afs/slac/g/atlas/c  # for example

...

 RHEL5-32bit

     Makes sure there is enough space with '" fs lq * '".
     There are 17 more AFS partitions mounted, in addition to the /c/ partition.
     If more space is needed, send a request to unix-admin@slac.stanford.edu
     (All examples below will assume installation in /c/)
---------------------------------------------------------------

3) Installing base release: x.x.x
     Issue the pacman command found in the HN/e-news announcement, and direct to pacman.log      

Code Block

pacman -allow any-platform trust-all-caches tar-overwrite

...

 -get http://atlas-computing.web.cern.ch/atlas-computing/links/kitsDirectory/projects/cache:AtlasProduction_15_6_5_i686_slc5_gcc43_

...

opt>> pacman.log &

...


------------------------------------------------

4) Installing AtlasProduction cache: x.x.x.x
     After steps 1-3, setup the release:

Code Block

...


. ~/reldirs/15.6.6/cmthome/setup.sh -tag=15.6.6,32

     Issue the pacman command found in the HN/e-news announcement, and direct to pacman.log. For example:      

Code Block

pacman -get http://cern.ch/atlas-computing/links/kitsDirectory/Production/cache:AtlasProduction_15_6_5_1_i686_slc5_gcc43_opt

...

 >> pacman.log &

...


    Note1: After the install is finished,

Code Block

...


cd /afs/slac/g/atlas/c/AtlasProduction/15.6.5.1/AtlasProductionRunTime/cmt/

...


cmt config

...


    Note2: If the AtlasProduction package requires a new DBRelease, it has to be downloaded manually.
           Check the status of the Production cache in the corresponding web page,
           http://atlas-computing.web.cern.ch/atlas-computing/projects/releases/status/15.6.5.1/AtlasProduction/
           which usually lists the DBRelease version number.
           If it uses a new DBRelease version, scp the tar file over from lxplus.cern.ch and
           put it in /c/DBRelease/ and "tar -xf" and move it as the way others are.
           DBRelease tar files are stored in
           /afs/cern.ch/atlas/www/GROUPS/DATABASE/pacman4/DBRelease/    
           This script will do all the work:

...

6) When there is an announcement of new AtlasLogin or AtlasSettings
     Go to the install area (/c/ in this example) and execute:

Code Block

...


pacman -update AtlasLogin

...


pacman -update AtlasSettings

     They are supposed to be backward compatible, unless stated otherwise.
----------------------------------------------------------------------------

...