FTS web-service software rolling upgrade procedure

What is it?

This is the procedure for performing a rolling upgrade to the FTS web-service nodes.

The rolling upgrade assumes you have more than one FTS web-service and have a load-balanced production alias.

If you do not, the downtime is around 1 minute, depending on how fast you type.

When to use it?

When you want to upgrade the FTS web-service or change its configuration files without causing service downtime.

Procedure

We use in the example the two-node load-balanced cluster at CERN. The SMS controls are part of the CERN CC environment; substitute appropriately for your site.

Mark one of the nodes for maintenance and drop it from the alias

sms set maintenance other "FTS upgrade" fts103

Wait for the node to drop out of the load-balanced alias.

host prod-fts-ws.cern.ch

Upgrade the software / config files

Upgrade the web-application resource file RPM glite-data-transfer-fts and/or make the necessary YAIM configuration changes:

spma_wrapper.sh

[ edit the YAIM configuration files ]

Perform the FtsProcedureTomcatClean15 procedure to clean Tomcat.

Rerun the YAIM config tool:

/opt/glite/yaim/scripts/configure_node \
    /afs/cern.ch/project/gd/SC3/SC4/yaim/agents-split-between-fts101-and-fts102/site-info.def FTS

This will restart the web-service.

Re-enable the node

sms set production none "FTS upgrade done" fts103

Wait for the host to come back into the load-balanced alias before doing the other node:

host prod-fts-ws.cern.ch

Repeat for the other node

For CERN-PROD, this is fts104.

Last edit: SteveTraylen on 2007-04-10 - 13:18

Maintainer: GavinMcCance