D0 Code - Initial installation of UPS/UPD/PERL

We are using Fermilab's ups/upd (Unix Product Support and Unix Product Distribution) to maintain and distribute the multiple versions of our code. ups/upd allows a large number of variations on how it is installed, and on how the code it is managing is installed. This document describes only one such, essentially the one we are using here at D0 on d0chb.

The steps you'll need to take in order to setup your site tobe able to receive remote distributions of the D0 software are:

• You'll need at least one large disk, the bigger the better. A small disk (few Gig) will work to keep a few releases. The size depends on how many versions you want to keep at any one time.
• You'll need to decide how you want your databases and product areas organized.
• You'll need to install ups, upd and perl, see below

• /usr/products are those products maintained and distributed by Fermilab from fnkits.fnal.gov. These include products such as ups, upd, perl, cern, python etc.
• /d0usr/products are those products that are similar in nature to the /usr/products products but are maintained and distributed by D0. These include products like ace that haven't yet gotten into fnkits
• /d0dist/dist is the real D0 offline code base.

NOTE: the names of these areas need not be as given above, but it makes life simpler if they are. In the following I will assume these names. If you wish to put them somewhere else, just substitute your names.

UPS/UPD/Perl installation

1. obvious:

2. where the db's live
   • SETUPS_DIR for us is /usr/local/products, but we recommend /fnal/ups/ or /usr/products. In any case, this area is the only area that must be hard coded into users' login files. They will need to:
     source setups.(c)sh
     whichever is appropriate for their shell in their .login or .profile.
   • UPD_USERCODE_DIR is /usr/products/upsdb/.updfiles, a subdirectory of the "main" ups db
   • PROD_DIR_PREFIX, for each of the three databases, is:
     • /usr/products
     • /d0usr/products
     • /d0dist/dist
     Each of these will have subdirectories: upsdb, the actual database, plus others. Most of these are explained later in the summary.

3. from ftp://fnkits.fnal.gov/products/ ups/, upd/ and perl/
   look for the latest version, then the "flavor" either the "NULL" flavor (for upd) or for your machine type for the others.

   You can save the tar files using your web browser, but in order to use upd or anonymous ftp you'll need to be registered. These programs are freely available for anyone in the high energy physics community. But you do need to fill out and email the UPD Registration Request form to me at d0-release-mgr@fnal.gov. I'll get you registered at the FNAL kits site (fnkits) as well as at D0's distribution site.

   If you have or will have only a single "flavor" of operating system reading from this disk, unwind them into: /usr/products/ups/v4_x or the directory appropriate for the version you pulled. If you'll have multiple "flavors" using that disk then add a further level of subdirectories named for the flavor you are pulling (ie IRIX+6/). The latter is assumed in several of the examples below.

4. Do this for each of the three db's, /usr/product/upsdb/... Only the main db needs all of the subdirectories. All of them need the .upsfiles/ and the .upsfiles/statistics/ (if you want to collect statistics, we don't) directories.
   • <d0chb> cat /usr/products/upsdb/.upsfiles/dbconfig
     displays the main dbconfig file on d0chb.
   • <d0chb> cat /usr/products/upsdb/.updfiles/updconfig
     shows the updconfig file. This is, by far the most complicated of the configuration files. But if you've named your databases the same as we have, you should be able to just copy this one. The places where changes might be needed are clearly marked.

     Follows is a very short description of why this file is so complex:
     There are four sections because this file is where the directory structure assumed by upd is determined. We have four different structures and or destinations. /usr/products and /d0usr/products will normally have the same structure, but we must be able to tell upd which db the product goes into. /d0dist/dist has two different structures, the packages/ tree and the releases/ tree. Therefore our updconfig file must be able to handle the four cases.
     NOTE: this example is for an installation where several "flavors" of machines share a single /usr/products and/or /d0usr/products disk. If you have only one flavor you can remove the "/${UPS_BASE_FLAVOR}" entry in UPS_PROD_DIR in the relevant sections.

   • <d0chb> cat /usr/products/upsdb_list
     shows our $SETUPS_DIR/upsdb_list file. It is simply a list of all possible ups db's. You are free to add more. If a given db isn't visible on a given node there is no problem. Add it here anyway. It'll only be used if it exists.

5. I hope you won't be doing this!

6. or this!

7. The version specified should be the one you pulled over.

   NOTE: you shouldn't need to edit any fermi files. In fact we are not recommending that you install them. You can, but don't need to. For our purposes all you need do is to tell your users who want/need to use the D0 software to put one of the following lines into their .login or .profile files:

       > source <your-setups_dir>/setups.csh
   or
       > . <your-setups_dir>/setups.sh
   

8. won't need this

9. probably won't need this unless you want ups to startup things like web servers. We do it and it's rather convenient, but not necessary.

10. this is just to keep people from having parts of both ups v3.x and ups v4.x in use at the same time. A new installation doesn't need it.

11. shouldn't be need.