CDB Configuration for the SLC3 FTS services

This descirbes the CDB configuration for two of the following services, FTS-T0-EXPORT and FTS-T0-EXPORT, the ones currently running on SLC3.

The SLC4-based service (*-21) are described in FtsTier0CDBConfiguration21.

DNS alias	SLS name	OS	Lemon	Version (20th May 2010)
fts-t2-service.cern.ch	FTS-T2-SERVICE	SLC4 64-bit	lemon subcluster	FTS 2.2.3
fts-patch4084.cern.ch	FTS-PILOT-SERVICE	SLC4 64-bit	lemon subcluster	FTS 2.2.4
fts22-t0-export.cern.ch	FTS22-T0-EXPORT	SLC4 64-bit	lemon subcluster	FTS 2.2.3

Template forrmat

All FTS components are contained within a single CDB Template which is pro_type_gridfts_slc3.tpl with all the operating independent configuration in pro_system_gridfts.tpl.

For each node we use two variables to define the node type and the sub cluster it belongs to:

  "/system/function"              = "ftschannel";
  "/system/cluster/subname" = "prod"

  "/system/function"              = "ftsmon";
  "/system/cluster/subname" = "prod"

  "/system/function"         = "ftsws";
  "/system/cluster/subname = "tiertwo"

  "/system/function"         = "ftsvo";
  "/system/cluster/subname = "pilot"

Cluster sub-name

This controls which FTS service the node serves. For the SLC3-based services, there are two:

See FtsTier0Deployment for the current up-to-date status of which nodes are deployed for which services.

For a description of these services themselves, see ScGridFTS.

Function

This describes what the node actually does within the cluster (i.e. whether it is an FTA agent node or a FTS webservice node).

See FTSServiceClass for a description of what each component is for.

N.B. There are no monitoring components (FTM) for the SLC3 service (these all run on SLC4).

Software configuration

All components of the FTS are configured using YAIM underneath the ncm-yaim component and CDB configuration. YAIM uses the ncm configuration trees:

/software/components/yaim/

/software/components/yaim/FTA/

/software/components/yaim/FTS/

to control the FTS configuration. The YAIM configuration tree in pro_system_gridfts.tpl defines trhe full configuration for the two services.

Once the CDB template is updated then on the nodes in question the profiles should be updated and the ncm component should be run. A typical cycle follows.

1. fts116 # ccm-fetch
2. fts116 # ncm-ncd --co yaim
3. If the ncm generated yaim config file /etc/lcg-quattor-site-info.def has not be modified then yaim will not run. Delete the file to force YAIM to run.

Note that a yaim configuration will restart tomcat on the FTS web-services but will not restart the FTA agents, the FTA agents must be restarted by themselves service transfer-agents restart

Detail: web-service

The web-service requires almost no configuration, except the database password, which is delivered by the fts_oracle_passwd SINDES component. This file dropped in by SINDES (/etc/fts-passwords/fts-db-password) is automatically picked up by ncm-yaim component.

• The DBURL (FTS_DBURL) is set to give the correct JDBC database connect string.

• The HOST_ALIAS (FTS_HOSTALIAS) is set for BDII to publish the correct DN alias instead of the local hostname.

See FtsServerInstall20 and FtsYaimValues20 for more details.

Detail: agents

In short, the configuration specifies which agent daemons reside on whch nodes in the cluster, and what the various properties of the FTS agent daemons are. The database password is the same as for the web-service for a given FTS service.

See FtsServerInstall20 and FtsYaimValues20 for more details.

SINDES

SINDES is used to add:

• the standard host certificates
• the standard load-balancing snmpd password
• the standard password file information
• the ssh key (not standard)
• fts_oracle_passwd which is a cluster-level component that delivers the database passwords to the nodes, using the sub-cluster name to select the correct password

Procedures

Service manager procedures are availble at FtsServiceProcedures.