You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

 - Originally from Peter Kim, now maintained by Andy Haas -

EXPERT only! ! !

Ask Andy Haas to install new releases for you!

0) HN/e-news announcement of new release pacman package
     https://groups.cern.ch/group/hn-atlas-releaseKitAnnounce/default.aspx

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

RHEL4-32 bit:  built on atlas-prod02.slac.stanford.edu:

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:

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

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

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:

. ~/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:

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,

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:

pacman trust-all-caches -get http://atlas.web.cern.ch/Atlas/GROUPS/DATABASE/pacman4/DBRelease:DBRelease-current

    See https://twiki.cern.ch/twiki/bin/viewauth/Atlas/AtlasDBRelease

5) Problems with release install
     Check the postings in https://groups.cern.ch/group/hn-atlas-releaseKitProblem/default.aspx
     as others might have similar problems.
   
     Ask Peter or Zach.
     If all fails, start a new thread in that forum.      

     If you ran out of disk space during an install, manually download the last missing tarball with a command like:

wget http://atlas-computing.web.cern.ch/atlas-computing/links/kitsDirectory/projects/kits/AtlasAnalysis_16_5_0_i686_slc5_gcc43_opt.tar.gz

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

pacman -update AtlasLogin
pacman -update AtlasSettings

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

7) Updating pacman:
    There are usually ATLAS announcements asking to install a new version.
    New version of pacman can be downloaded from BU:

wget http://physics.bu.edu/pacman/sample_cache/tarballs/pacman-latest.tar.gz
tar -xf pacman-latest.tar.gz

    Move the pacman package to /afs/slac/g/atlas/packages/pacman/, go into the new
    pacman directory and set up.

cd x.xx
source setup.sh

     (Please note that any installs in /c/ or /d/ must stay with the pacman version
     that was originally used. pacman does not get updated often, but when it does
     it might be a good time to build a new install with it switching between
     /c/ and /d/.)

  • No labels