FTS Server Installation Guide 1.5

This is the installation guide for FTS server 1.5. It covers both the agent servers (FTA) and the web-service (FTS) components.

It refers to FTS version 1.5 from gLite release 3.0.

Changes from release 1.4 are described in FtsChangesFrom14To15.

If you are upgrading from 1.4 please read the above changes and then follow the instructions in FtsServerUpgrade14to15 instead.

Administration of the service is described in FtsServerAdmin15.

Service procedures specific to 1.5 can be found in FtsProcedures15.

Requirements

  1. You should install the FTS and FTA servers on reasonable Scientific Linux 3 machines, ideally of mid-range server-class. It is recommended to have a least 512M memory, and a modern processor. Large amounts of disk space is not critical, so a disk-server class machine is not needed.
  2. There should be a valid hostcert and hostkey in /etc/grid-security/. The installation and configuration procedure should download the CA hash files and CRL lists specified in the current release at http://www.eugridpma.org/distribution/. If these already exist on the system, they will will be upgraded if necessary.
  3. The configuration makes changes to the password file (it creates 2 users). Your system (and in particular the file /etc/security/limits.conf) should allow these users to obtain a shell, although there is no requirement for remote login to these accounts.
  4. Your system should have Java installed on it, this is available from http://java.sun.com. This is not provided by gLite for redistribution licensing restrictions. The recommended default is j2re1.4.2_08.
  5. Your system should have Oracle instantclient installed on it. This is not provided by gLite for redistribution licensing restrictions. Contact the service challenge team for details of how to obtain the RPMs or go to http://www.oracle.com/technology/software/tech/oci/instantclient/index.html. The recommended version is currently 10.2.0.1.
  6. For the host running the FTS web-service, the firewall should be open for incoming on port tcp/8443 for the web-service. The connection from the client to the web-service is secured with GSI.
  7. For the host running the FTA agent daemons, the outgoing firewall (if present) should allow access to your MyProxy server, the database, all source SRM/gridFTP clusters and all destination SRM/gridFTP clusters.

Choose deployment scenario

Examine the possible deployment scenarios from FtsServerDeploy13 and decide which you want.

The miniumum suggested configuration is:

  • one machine for the FTS web-service
  • one machine for all the FTA agent daemons (both the VO agents and the channel agents)

Both the web-service instances (if there is more than one) and the agent dameons can be (and should be) spread across machines for scalability.

Prepare the site-info.def file

This the site wide config file for YAIM. It should be prepared in advance.

The file will contain the configuration for all of the FTA agents (VO and channel) and the web-service(s).

We describe the configuration of the agent daemons first, and give an example.

FTA agents

The yaim variables for cnfiguring the FTA agents are all prefixed with FTA_ in the site-info.def file. Any variable with prefix FTA_ that the configuration script does not understand will cause it to fail.

Identify:

  • the hostname of the machines you want to be running the FTA agents
  • which agents will run on which machine.

In the example, we assume two VO agents (for dteam and atlas) and two channel agents (CERN-CERN and CERN-BNL). We choose to run:

  • the dteam VO agent and CERN-CERN channel agent together on the host fts001.test.ch
  • the atlas VO agent and CERN-BNL channel agent together on host fts002.test.ch

RPM installation

The RPM installation is managed by YAIM.

See the YAIM installation guide for more details on how to install yaim.

http://grid-deployment.web.cern.ch/grid-deployment/documentation/LCG2-Manual-Install/

There are two distinct server types to install, FTS (the web-service dameons) and FTA (the agent dameons). From the deployment model you have chosen, identify which machines will be running FTS web-service and which machines will be running FTA agents.

FTS web-service

Run the YAIM install_node script:

/opt/glite/yaim/scripts/install_node site-info.def glite-FTS_oracle

This will check that an appropriate version of Oracle instantclient is installed.

FTA agents

Run the YAIM install_node script:

/opt/glite/yaim/scripts/install_node site-info.def glite-FTA_oracle

This will check that an appropriate version of Oracle instantclient is installed.

Run the configuration script

On each node, run the yaim configuration script, dependent on the node type.

FTS web-service

For the web-service nodes, run:

/opt/glite/yaim/scripts/configure_node site-info.def FTS

FTA agents

For the agent nodes, run:

/opt/glite/yaim/scripts/configure_node site-info.def FTA

Starting the service

FTS web-service

To start the FTS web-service:

service tomcat5 start

A single daemon will start under the tomcat4:tomcat4 user.

FTA agents

To start the FTA agent daemons:

service transfer-agents start

Every agent daemon that you have chosen to configure on the box will be started in sequence.

To start a single agent daemon:

service transfer-agents start --instance glite-transfer-channel-agent-srmcopy-CERN-FNAL

where the instance name is described above.

[ incomplete ]


Last edit: FlaviaDonno on 2007-02-02 - 10:03

Number of topics: 1

Maintainer: GavinMcCance


Edit | Attach | Watch | Print version | History: r14 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 2006-04-26 - GavinMcCance
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback