CMS in the UK

-- very much work in progress ---

Setup within the UK - Overview

There are nominally four Tier 2 sites:
T2_UK_London_IC (UKI-LT2-IC-HEP)
T2_UK_London_Brunel (UKI-LT2-Brunel)
T2_UK_SGrid_Bristol (UKI-SOUTHGRID-BRIS-HEP)
T2_UK_SGrid_RALPP (UKI-SOUTHGRID-RALPP)

and six Tier 3:
T3_UK_London_QMUL
T3_UK_London_RHUL
T3_UK_London_UCL
T3_UK_ScotGrid_ECDF
T3_UK_ScotGrid_GLA
(all associated with Imperial)
T3_UK_SGrid_Oxford
(looked after by RALPP)

How to contact CMS in case of problems ?
Ask your friendly Tier 2 contact person (Chris B, (Andrew L), Daniela). If they can't help you (CMS internals are rather baroque), file a GGUS ticket. After much to-and-fro these are actually matched to CMS internal ticketing system. If in doubt, do both.

For the Tier2s: There is hn-cms-t2 *at* cern.ch, or if it's more urgent: hn-cms-comp-ops *at* cern.ch

Monitoring

Please also see the CMS section of the Monitoring Pages. However if you keep an eye on the links below, that should cover most issues.
For everyone:
CMS Nagios
The CMS dashboard.
For the Tier 2s:
Site Readiness Table and Site Ranking
Hammercloud: From the CMS dashboard, use 'Interactive View' and then set the filters to 'hcjobrobot' and 'Sort by' to 'ce' and stick your site name in the appropriate box. The hammercloud FAQ.

---

Site configuration

CMS will per se try and run on any CEs that advertise CMS. However certain tests/workflows are only tested if a SE is included in the CMS SiteDB. If you are a Tier 3, this has to be done by the associated Tier 2, so please let them know.

CMS keeps a bunch of local configuration files in your software area. These can be found in $VO_CMS_SW_DIR/SITECONF. The files you might have to modify on occasion are: cmsset_local.(c)sh, site-local-config.xml and storage.xml.
CMS also keeps a backup of these files in git(*) and the nagios tests will fail after 72 if they are not consistent. To put a new version of one of these files into CVS please talk to your associated Tier 2. There should only ever be one version of all these files on your site.
(*)Yes, they are world readable. You shouldn't have to put anything in there that you didn't want the world to know.

CMS Computing Operations policies (mainly for T2s)

CVMFS

From Spring 2014 CVMFS will be compulsory for all CMS sites.
CVMFS for CMS

gLexec
CMS would like some, though I am not aware of any specific instructions. There is still the old WLCG page.

*** SE related stuff

xrootd

CMS xrootd main page
The official CMS mailing list for xrootd issues is: hn-cms-wanaccess at cern.ch (though I have yet to see anyone having their questions answered there).

Phedex (data transfer)

You can check the Phedex debug streams here: T2 , T3

Clean up
CMS uses a number of temporary areas on the SE which need to be cleanup on a regular basis: CompOpsStoreTemp
Stuart's script which used to implement this for the T3s has lost some of its lustre and I need to debug this.