|
Update Regarding SAM Installation, September 2004
|
Due to major re-organizations and improvements
in all components of SAM, if you are planning on installing/upgrading
a SAM station, you will need to install/upgrade to at least the
minimum supported version of all the following packages:
| Product |
Minimum Supported Version |
| ups |
v4_7_1 |
| sam_station |
bv6_? (unknown at this time, not stable yet) |
| sam_bootstrap |
v4_3_0 |
| sam |
v6_0 |
| sam_user_pyapi |
b6_1_1_0 |
| sam_admin_pyapi |
b6_1_1_0 |
| sam_mis_pyapi |
b6_1_1_0 |
| sam_common_pylib |
b6_1_1_0 |
| sam_idl_pylib |
b6_1_1_0 |
| sam_config |
v4_2_28 |
| sam_db_srv |
b6_1_1_0_v5_1_1_schema |
| sam_dimension_server_prototype |
b6_1_1_0_v5_1_1_schema |
|
The installation of a SAM station is described in several steps:
- System Preparation:
Software that must be installed and functioning properly before
you can begin to install SAM software.
- SAM Software:
Installation of the sam software components.
- SAM Configuration:
Configuration of SAM system, including all environmental variables
required for each software component you are running.
- SAM Bootstrap:
Installation, configuration and startup of SAM station components.
- File Transfer:
Installation and configuration of the appropriate file transfer
mechanisms to be used by SAM on your system.
- Station Configuration:
Final steps required in order to start your station.
Each of these steps is described in detail under the appropriate link.
Required System Preparation:
- sam account: Your system must have a 'sam' account, UID 7816.
- Firewalls: the sam client and servers must be
able to connect to a restricted number of hosts and ports.
For more information see the
SAM-Grid Manual
at paragraph "Open Ports for Incoming TCP connections".
- UPS/UPD: Your system must be running ups and upd, the Fermilab
product distribution mechanism. Documentation and installation instructions
are available from http://www.fnal.gov/docs/products/ups/.
The minimum recommended versions are ups v4_6_2 and upd v4_6.
-
If you want any SAM station servers to be started at boot time,
your system will need to be configured such that "ups startup"
is called during system boot. This is something that must be
done by the system administrator, and is documented in the
ups documentation.
Troubleshooting:
- Are funny things happening with your ups installation? Are you
on a Linux box, and was it recently upgraded to ups v4_6 from an
earlier release? If so, you may be running multiple incompatible
versions of ups. To check:
$ ups list -aK+ ups
"ups" "v4_5_4" "Linux+2.2" "" "current"
"ups" "v4_6_2" "Linux+2" "" "current"
If, as in this example, you have more than one version of ups declared
as 'current', you will need to undeclare earlier releases:
$ ups undeclare ups v4_5_4 -f Linux+2.2 -y # remove the old one completely
or
$ ups undeclare -c ups -f Linux+2.2 # remove only the 'current' chain
# from the older version
- UPD Configuration issues (obsolete). Prior to SAM v4_1_x, it was important
to make sure that your upd configuration included product name, version,
flavor, and qualifier in the path to the product directory. This is no
longer an issue, as:
- newer releases of upd have a default configuration which includes this
information,
- sam no longer uses qualifiers in the distribution releases.
|
SAM Software Installation Overview:
- SAM Client components:
In order to use any 'sam' command, you must install and configure the client
packages.
$ setup upd
$ upd install -G -c sam
$ ups tailor sam
Follow the menu, and add necessary SAM configurations. For example,
for running station servers
choose the "D0 Production Station Server" as base
configuration, "station_prd" as new qualifier. For users,
choose the "D0 Production User" configuration, with "prd"
as the new qualifier. The "prd" configuration can be set
as default for "setup sam".
See the SAM Configuration documentation for further information
on tailoring the SAM environment.
- SAM Station components:
In order to run a station or file storage server, you must install and configure
the necessary station components.
$ setup upd
$ upd install -G -c sam_bootstrap
$ ups tailor sam_bootstrap
Note that the server environment has to correspond to one of
the sam_config qualifiers (e.g., "station_prd") which are added
during the "ups tailor sam" phase.
See the SAM Bootstrap documentation for further information
on tailoring the station components.
- SAM File Transfer components:
In order for SAM to be able to transfer files to and from your
station, you must install the sam_cp wrapper and at least one
of the available underlying protocols:
$ setup upd
$ upd install -R -G -c sam_cp # INSTRUCTIONS NOT YET WRITTEN!!!
$ upd install -G -c sam_bbftp # if you plan to use the bbftp protocol
# for transfers to/from your station
$ ups tailor sam_bbftp # INSTRUCTIONS NOT YET WRITTEN
$ upd install -G -c sam_kerberos_rcp # if you will be using Fermilab kerberos
# authentication for file transfers
# INSTRUCTIONS NOT YET WRITTEN
$ upd install -G -c sam_encp # if you have direct access to the Fermilab
# Enstore MSS system
For sam_gridftp and further information on configuring the necessary file
transfer components, see the File Transfer
documentation.
For further information, contact sam-admin@fnal.gov
=============================================================================
Project : SAM
Package : $Name: $
Revision : $Revision: 1.1 $
Modified : $Date: 2002/04/17 16:03:42 $ by $Author: lauri $
This work is part of a development project, called SAM, which consists
of a number of coordinated packages each named sam_xxxx. Notice of
authorship, copyright status, and terms and conditions, should the
software eventually become available for use outside Fermilab, can be
found in the README and LICENCE files in the top level directory of
the main sam package.
=============================================================================
|