No permission to view FIOgroup.FabricServicesMenu
CDB Configuration for the SLC4 FTS services
This descirbes the CDB configuration for two of the following services,
FTS-T0-EXPORT-21 and
FTS-T0-EXPORT-21, the ones currently running on SLC4.
The older SLC3-based service are described in
FtsTier0CDBConfiguration20.
Template forrmat
The FTS components are defined in the new FIO hireachical template structure. The node template defines what a given node does:
include {"services/gridfts/service/t0export"};
include {"services/gridfts/role/webservice"};
include {"services/gridfts/service/t0export"};
include {"services/gridfts/role/agent"};
include {"services/gridfts/service/t2service"};
include {"services/gridfts/role/webservice"};
include {"services/gridfts/service/t2service"};
include {"services/gridfts/role/agent"};
include {"services/gridfts/service/monitor"};
include {"services/gridfts/role/monitor"};
The core template, common to all node types, is
prod/services/gridfts.tpl.
Service name
This 'service' is translated immediately to cluster sub-name - in the following disucssion, the two should be used to mean the same thing.
It controls which FTS service the node serves. For the SLC4-based services, there are two:
and the monitor service (which monitors all FTS services):
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.
Role
This describes what the node actually does within the cluster (i.e. whether it is an
FTA
agent node or a
FTS
webservice node). It is immediately set to the CDB 'function' attribute.
See
FTSServiceClass for a description of what each component is for.
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 CDB
services/gridfts/service/
templates describe the configuration for each separate service. e.g.:
prod/services/gridfts/service/t0export
prod/services/gridfts/service/t2service
prod/services/gridfts/service/monitor
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.
-
fts201 # ccm-fetch
-
fts201 # ncm-ncd --co yaim
- 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.