Difference between revisions of "Recipe for importing release"

From GridPP Wiki
Jump to: navigation, search
 
(No difference)

Latest revision as of 10:25, 16 November 2009


Installing 24.3.5e

Suppose we want to install 24.3.5e

Log into a machine at SLAC to look at the set up of the release. You can log into yakut01.slac.stanford.edu

[bbr-ral03] cd $BFROOT/dist/releases/18.6.0b

You can check to see if the release is actually based on another one by looking for the link BASE.

 [bbr-ral03] /afs/slac.stanford.edu/g/babar/dist/releases/14.3.5e > ls -l BASE
 lrwxr-xr-x    1 jmorris  br    51 Oct 13 06:14 BASE -> /afs/slac.stanford.edu/g/babar/dist/releases/24.3.5  

You can see that it is linked to 24.3.5, so you will need this release first before importing 24.3.5e. If the link BASE does not exist then you can import 24.3.5e on it's own. As a clue, if a release ends in a letter it usually has a BASE link

So log into RAL to import the release (to build a release designed for SL4, log into lcgui01).

 ssh bfactory@babar.gridpp.rl.ac.uk
 klog bfactory 

Pick an empty AFS volume for each release 24.3.5 and 24.3.5b. If you are importing multiple architectures they should go on the same volume (i.e. SL3/4/5 shouls all go on teh same volume for a given release).

[csff] $ cd $BFROOT/.vol
[csff] $ fs lq rel??
Volume Name                   Quota      Used %Used   Partition
bfactory.rel38             20971520   2903708   14%         34%
bfactory.rel39             20971520   1068181    5%         34%
bfactory.rel40             20971520         7    0%         34%
bfactory.rel41             20971520         7    0%         34%
bfactory.rel01              3145728    445899   14%         83%
 .
 .

I will use rel41. Starting the import we first import 24.3.5 which is the BASE release

[csff] $ cd
[csff] $ cd .rsync
[csff] $ submitimport
Enter release to be imported:
24.3.5
Enter architecture to be imported (e.g Linux24SL3_i386_gcc323):
Linux24SL3_i386_gcc323
Enter AFS volume which the data should be written to (e.g .vol/rel01):
.vol/rel41
Enter the release (BASE) on which tag is based:
(Just press return if none);
Submitting import procedure as a batch job 1311549.csflnx353.rl.ac.uk Job submitted

In the last request from the subimport command above we just press return as 24.3.5 is the BASE release. I don't believe have to do this, but I wait till the above import is finished berfore importing the series release 24.3.5e.

Now import 24.3.5e

[csff] $ cd .rsync
[csff] $ submitimport
Enter release to be imported:
24.3.5e
Enter architecture to be imported (e.g Linux24SL3_i386_gcc323):
Linux24SL3_i386_gcc323
Enter AFS volume which the data should be written to (e.g .vol/rel01):
.vol/rel41
Enter the release (BASE) on which tag is based:
(Just press return if none);
24.3.5
Submitting import procedure as a batch job 1312700.csflnx353.rl.ac.uk Job submitted     

When this import is finished you may need to check that the file setting sin SoftRelTools are correct.

[csff] $ cd $BFROOT/dist/releases/24.4.2/SoftRelTools
[csff] $ chmod a+r *

You then need to setup the local settings for the location of some of the files (e.g. xrootd. tcl,...) on both 24.3.5 and 24.3.5e. For the next step you need a bfactory RAL AFS token.

[csff]/afs/rl.ac.uk/bfactory/dist/releases/24.3.5% klog bfactory@rl.ac.uk

The password is the bfactory one.

For each release create a link in $BFOVERRIDE. For releases designed to be built under SL4 make a link to 24.4.2 release.

> cd $BFOVERRIDE
>  ln -fs 24.2.1 24.3.5
>  ln -fs 24.2.1 24.3.5e

(ie. 24.3.5e (new release) -> 24.2.1 (last release with config changes)

This is necessary as long as SiteConfig is not up to date.

Now run gmake siteinstall on both 24.3.5 and 24.3.5e.

[csff]~% cd $BFROOT/dist/releases/24.3.5
[csff]/afs/rl.ac.uk/bfactory/dist/releases/24.3.5% srtpath 24.3.5
Select/enter BFARCH (CR=1):
1) Linux24SL3_i386_gcc323      [prod][test][active][default]
2) Linux24RHEL3_i386_gcc323    [default2]
1

[csff]/afs/rl.ac.uk/bfactory/dist/releases/24.3.5% gmake siteinstall 
 GNU Make  version 3.79.1, Build OPTIONS = Linux24SL3_i386_gcc323-Debug-native-Objy-Optimize- Fastbuild-Ldlink2-SkipSlaclog- Static-Lstatic
 Linux csff.rl.ac.uk 2.4.21-32.0.1.ELsmp #1 SMP Wed May 25 15:42:26 CDT
 2005 i686 i686 i386 GNU/Linux  [uname -a]
 -> binscripts
 -> AbsBTagging.binscripts:   (Sun Oct 16 01:40:59 BST 2005)
 -> AbsCalo.binscripts:   (Sun Oct 16 01:41:02 BST 2005)
 .
 .
 .

This will take a few hours to complete. Then do the same for 24.3.5e

[csff]~% cd $BFROOT/dist/releases/24.3.5e
[csff]/afs/rl.ac.uk/bfactory/dist/releases/24.3.e5% srtpath 24.3.5e
Select/enter BFARCH (CR=1):
1) Linux24SL3_i386_gcc323      [prod][test][active][default]
2) Linux24RHEL3_i386_gcc323    [default2]
1

[csff]/afs/rl.ac.uk/bfactory/dist/releases/24.3.5e% gmake siteinstall 
 GNU Make  version 3.79.1, Build OPTIONS = Linux24SL3_i386_gcc323-Debug-native-Objy- Optimize-Fastbuild-Ldlink2-SkipSlaclog-Static-Lstatic
 Linux csff.rl.ac.uk 2.4.21-32.0.1.ELsmp #1 SMP Wed May 25 15:42:26 CDT
 2005 i686 i686 i386 GNU/Linux  [uname -a]
 -> binscripts
 -> AbsBTagging.binscripts:   (Sun Oct 16 01:40:59 BST 2005)
 -> AbsCalo.binscripts:   (Sun Oct 16 01:41:02 BST 2005)
 .
 .

Then you have finished. I test the release by building a test binary say BetaMiniApp and make sure all the relevant links in /afs/rl.ac.uk/bfactory/dist/releases/24.3.5e/shlib/Linux24SL3_i386_gcc323/ldlink are not broken.