Middleware transition

From GridPP Wiki
Jump to: navigation, search

gLite to UMD/EMI middleware transition

This is to collate information about site status and plans in moving from the gLite middleware stack to EMI-x/UMD-x. There is also information on the technical processes of EMI/UMD middleware transition, including an example .

LondonGrid

UKI-LT2-BRUNEL

gLite3.1/SL4

I have the following services on glite 3.1

-> CEs dgc-grid-40, and dgc-grid-44

Soon to be replace by CreamCEs

-> CE dgc-grid-35

it should be decommissioned by the end of the year

-> BDII

to be upgraded in the next few months

-> SE dgc-grid-50

it has only 2% of the data at the site. I'm planning an upgrade for the 3rd week of December. Most of the data at Brunel is in dc2-grid-64, glite 3.2 SE.

gLite3.2/EMI

ARGUS

. EMI Argus server running stable since May.

BDII_site

. Upgrading to glite 3.2 in October

CE (CREAM/LCG)

. dgc-grid-43 running on EMI CreamCE.
. Other CEs on LCG, but to be upgraded before the end of the year 

glexec

 . Deployed in dgc-grid-43
 . To be deployed in all CEs when they are upgraded

SE

 . Main SE (95%) of the storage running on SL5 DPM 1.8
 . Remaining SE will be upgraded in December

UI

. SL5 glite 3.2

WN

. All glite 3.2

Comments

UKI-LT2-IC-HEP

I have a SL4 WMS (wms02.grid.hep.ph.ic.ac.uk) as there is no SL5 WMS in glite. I use wms01 to test the EMI WMS, but it took today's (9/8/11) update to get it working. I intend to keep the glite 3.2 WMS around for a while longer until the EMI version is stable. Note that our lcg-CEs are running SL5 (technically CentOS 5).

gLite3.2/EMI

ARGUS: none so far

BDII_site: glite 3.2

CE (CREAM/LCG): CREAM glite 3.2, no SGE support in EMI so far, lcg-CE 3.1 on CentOS 5

glexec: not so far

SE: dCache 1.9.12-8 (updates directly from dCache)

UI: glite 3.2

WMS: glite 3.1 and EMI

WN: glite 3.2

Comments

UKI-LT2-QMUL

lcg-CE (SL4): and having problems with CREAM (Glite 3.2 version), so will remain until that's done.

* Will require sge support in CREAM to move to UMD release. 


gLite3.2/EMI

ARGUS: Not yet

BDII_site: Glite 3.2 version deployed. This had problems with stability, so now using openldap 2.4 - which seems much more stable.

CE (CREAM/LCG):

* ce01: lcg-CE (old hardware, remains for testing and through inertia)
* ce02: lcg-CE (Old hardware, remains for testing and through inertia)
* ce03: lcg-CE x5420 machine. In service, will be kept until CREAM problems solved
* ce04: CREAM - having problems from time to time. See sge-cream discussion


glexec : Not yet deployed.

SE:

* se01: Test  - Storm 1.5 - to be decommissioned. 
* se02: Decomissioned
* se03: Production - Storm 1.7.0 and 1.7.1. Frontend is EMI release, backend is previous EMI (and UMD) release. 
* se04: Test - StoRM 1.7.1 EMI release (I've submitted a staged rollout report recommending it fails). 


UI

* Not run at the grid site. 

WMS

* NA

WN

* 3.2.10 tarball release.

Comments

UKI-LT2-RHUL

lcg-CE:- have to plan for this by finding a suitable hardware.

gLite3.2/EMI

ARGUS - 3.2.4-2

BDII_site - 3.2.11-1

CE (CREAM/LCG)3.2.10

glexec 3.2.6-3

SE 1.8.1

UI


WN 3.2.11

Comments

UKI-LT2-UCL-CENTRAL

Comments

Site no longer exists!

UKI-LT2-UCL-HEP

gLite3.2/EMI

ARGUS: not yet

BDII_site: gLite 3.1

CE (CREAM/LCG): CREAM CE on gLite 3.2, will soon retire LCG CE, which is on 3.1

glexec: not yet

SE: head node still gLite 3.1 on SLC4, to be upgraded soon

UI

WMS

WN: gLite 3.2

Comments

NorthGrid

UKI-NORTHGRID-LANCS-HEP

gLite3.2/EMI

ARGUS - Not yet, need to plan this one out.

BDII_site - glite-BDII_site-3.2.10-1.sl5.x86_64

CE (CREAM/LCG) - glite-CREAM-3.2.10-0.sl5 / lcg-CE-3.1.40-0

glexec - Not yet (waiting on relocatable version)

SE - DPM-server-mysql-1.7.4-7sec.sl5.x86_64 (will upgrade to 1.8 towards the end of the month/start of October)

UI - SL5

WMS -NA

WN - glite-WN-3.2.9-0.sl5 tarball

Comments

We're planning to tentatively test the waters with UMD/EMI by installing a supplimentary cream CE with it, however like our peers we'd rather let the dust settle for a bit and only swap over when the benefits outweight the risks.

UKI-NORTHGRID-LIV-HEP

gLite3.2/EMI

APEL: x86_64, SL 5.5, emi-apel-1.0.0-0.sl5

ARGUS: x86_64, SL 5.5, emi-argus-1.4.0-1.sl5

BDII_site: x86_64, SL 5.5, emi-bdii-site-1.0.0-1.sl5

CE (CREAM/LCG): hepgrid10: x86_64, SL 5.5, emi-cream-ce-1.1.0-4.sl5 (emi2) hepgrid6: x86_64, SL 5.5, emi-cream-ce-1.1.0-4.sl5 (emi2) hepgrid5: x86_64, SL 5.5, emi-cream-ce-1.1.0-4.sl5 (emi2)

glexec: x86_64, SL 5.3, emi-glexec_wn-1.1.1-2.sl5

SE (Headnode): x86_64, SL 6.3, dpm-1.8.4-1.el6.x86_64 (emi2) SE (Disknodes): x86_64, SL 6.3, emi-dpm_disk-1.8.4-1.el6.x86_64

WMS: na

WN: x86_64, SL 5.3, emi-wn-2.0.1-1.el5

UI: i386, SL 4.7, glite-UI-3.1.45-0; x86_64, SL 5.5, glite-UI-3.2.10 (tarball)

Comments

Current planning: Our current baseline is stable at present. We have done a staged transition of grid servers to a new EMI baseline. Next plan is to move all to EMI2 (form EMI1) in UI, and use SL6 on all server except WN. Eventual move WN to SL6.

UKI-NORTHGRID-MAN-HEP

All services are x86_64, SL5 and glite3.2

gLite3.2/EMI

ARGUS glite-ARGUS-3.2.4-2
BDII_site glite-BDII_site-3.2.11-1.sl5
BDII_top  glite-BDII_top-3.2.11-1.sl5
CE (CREAM) glite-CREAM-3.2.10-0.sl5 (ce01), glite-CREAM-3.2.11-2.sl5 (ce02)
glexec glite-security-glexec-0.7.0-2.sl5 (ce02)
SE glite-SE_dpm_mysql-3.2.7-2.sl5 (head node), glite-SE_dpm_disk-1.8.0-1.sl5 (data servers)
UI glite-UI-version-3.2.8-0.sl5
WN  glite-WN-version-3.2.10-0.sl5

Comments

Same as Liverpool.

UKI-NORTHGRID-SHEF-HEP

glite 3.1 ce will be reinstalled as EMI CREAM CE in October

gLite3.2/EMI

ARGUS glite 3.2 installed

BDII_site glite 3.2

CE (CREAM/LCG) CREAM CE glite 3.2

glexec glite 3.2 installed

SE DPM 1.8.0 on DPM headnode and all disk servers

UI

WMS

WN glite 3.2

Comments

ScotGrid

UKI-SCOTGRID-DURHAM

gLite3.2/EMI

ARGUS

BDII_site

CE (CREAM/LCG)

glexec

SE

UI

WMS

WN

Comments

UKI-SCOTGRID-ECDF

gLite3.2/EMI

ARGUS Look to deploy over the next couple of months. Place in production once verifed support.

BDII_site glite-BDII_site-3.2.11-1

CE (CREAM/LCG) 2 x glite 3.2 CreamCE (one virtual based, one real), 1 LCG-CE Virtual instance suffering from performance issues, likely to migrate this service to a non-virtual host. LCG-CE host will be decomissioned when two stable CreamCE services are in place.

glexec No plans yet. Will look to deploy gLExec-WN tarball when officially available and once gLExec is fully validated by ATLAS and LHCb.

SE production SE: SL4 glite 3.1 (plan to move to SL5 glite 3.2 before the end of the year) test SE: EMI 1.0 SL5

UI No UI - we use our local T3 setup to get user level access to grid services.

WN Use tarball version. Plan to upgrade 3.2.11 in the next couple of months.

Comments

UKI-SCOTGRID-GLASGOW

  • DPM MySQL head node. Upgrade planned.
  • Some DPM pool nodes - rolling update to SL5 (around half of the oldest disk servers to be decommissioned after next procurement).
  • WMS & L&B servers. Will remain until there is a supported combination of L&B and WMS that will run on the same host.
  • VOMS server (already under threat of upgrade due to incident) - upgrade planned.
  • SL4 VOBOX for PANDA. In discussion with the VO on that one.

No problems anticipated in update to SL5, once software requirements are handled

gLite3.2/EMI

ARGUS: Will deploy when CREAM/DPM have Argus support (currently use SCAS)

BDII_site: glite 3.2: glite-BDII-3.2.9-0

CE (CREAM/LCG): glite 3.2: glite-CREAM-3.2.8-2

glexec: glite-3.2 glite-security-glexec-0.7.0-2

SE: glite-3.2 DPM 1.8.0-1

UI: glite3.2: glite-UI-version-3.2.8-0

WMS: glite 3.1: glite-WMS-3.1.31-0

WN: glite 3.2: glite-WN-3.2.9 through 11 (rolling upgrade)

LB: glite 3.1: glite-LB-3.1.20-2

VOMS: glite 3.1: Voms-Admin version 2.0.15

Comments

WMS and LB will be updated once stable release version for SL5 (EMI)

We have an EMI CREAM instance and ARC CEs under testing

We have a test version of DPM running on svr025

SouthGrid

UKI-SOUTHGRID-BHAM-HEP

  • An overhaul is pending in the following weeks (9/11 - 10/11) where we hope to shift all service nodes to a new set of hardware and retire the LCG CEs
  • All nodes are on SL5 (.4 or .5) except the LCG-CEs which are SL4.

gLite3.2/EMI

ARGUS : gLite 3.2

BDII_site : gLite 3.2

CE (CREAM) : 2 x gLite 3.2

CE (LCG) : 2 x gLite 3.1

glexec : gLite 3.2

SE : gLite 3.2, DPM 1.8

UI : gLite 3.2

WMS (No WMS) : N/A

WN : gLite 3.2

Comments

  • This is probably available somewhere and I just don't know, but a comprehensive, one stop guide for versions of software that should running and also expected loads/requirements would be *very* useful!

UKI-SOUTHGRID-BRIS-HEP

  • StoRM v1.3 SE (lcgse02.phy.bris.ac.uk) is still SL4 as is its slave gridftp server gridftp01.phy.bris.ac.uk. StoRM v1.4 & 1.5 are not supported on SL5, and StoRM v1.6 & 1.7 (supported on SL5) are very unstable & not production ready yet (just ask Chris Walker who's had ++painful experience with them). Waiting on stable StoRM for SL5 - soon hopefuly.
  • lcgnetmon (owned+operated by RAL) is still SL4 AFAIK

gLite3.2/EMI

ARGUS : Not yet

BDII_site : gLite 3.2

CE (CREAM/LCG) : 2 x gLite 3.2 CREAM-CE

glexec : Not yet

SE : see above

UI : gLite 3.2

WMS : Ain't got one (content to use others')

WN : gLite 3.2

Comments

UKI-SOUTHGRID-CAM-HEP

All nodes running SL5, exceptfollowing nodes:

  • lcgCE 3.1 (condor)
  • SE (DPM)

running SL4 Upgrading

SE under progress. the lcgCE would stay longer I imagine.

gLite3.2/EMI

ARGUS/glexec

Not yet installed

BDII_site

gLite 3.2

CE (CREAM/LCG)

1 LCG CE (condor)
1 CREAM CE (torque) 

SE

The SE itself running DPM v1.7.4 (SL4)
All the disk servers running v1.8 (SL5)

UI

gLite 3.2

WMS

N/A

WN

gLite 3.2

Comments

EFDA-JET

All nodes running SL5

gLite3.2/EMI

ARGUS

BDII_site

CE (CREAM/LCG)

glexec

SE

UI

WMS

WN

Comments

UKI-SOUTHGRID-OX-HEP

  • SL4 DPM head nodes still in use
  • Some DPM pool nodes , although we are in the process of draining an migrating to SL5 based nodes.
  • All old LCG-ce's have been decommissioned.
  • On the UK Nagios monitoring we use an SL4 based my proxy server as it is not yet available on SL5

gLite3.2/EMI

ARGUS : gLite3.2

BDII_site: gLite 3.2

CE (CREAM/LCG):

2 CE's gLite3.2

1 CE EMI (latest release under stage rollout )

glexec: gLite3.2

SE:

UI : gLite3.2

WMS: gLite3.1 ( Used only by gridppnagios only)

WN : glite3.2

Comments

UKI-SOUTHGRID-RALPP

2 lcg-CE's, Both now decommissioned and reinstalled as CreamCEs.

gLite3.2/EMI

ARGUS: gLite-3.2

Will replace with second VM and transition service to that

BDII_site: gLite-3.2

Will replace with second VM and transition service to that

Cluster Publisher: UMD 1.1

CE (CREAM/LCG): 1x gLite 3.2 2 x UMD 1.1

gLite CreamCE will be decommissioned soon and another UMD CreamCE installed to replace it

WN/glexec: gLite 3.2

Believe there are current issues with the UMD release of WN and it is not currently recommended, will do a rolling reinstall/upgrade once it is. gLexec version will follow WNs

SE: dCache 1.9.5

Starting testing update to 1.9.12

UI: gLite 3.2

No current plans for update, will probably do a rolling reinstall

Comments

Tier1

RAL-LCG2-Tier-1

gLite3.1/SL4

WMS - 3 nodes v3.1.32-0.slc4

LCG-CE - 1 node v3.1.37-0 (planned to be migrated to glite3.2 CREAM, not scheduled yet)

PROXY - v3.1.29-0

gLite3.2/EMI

APEL - v3.2.5-0.sl5

ARGUS - n/a

BDII_site - 3 nodes v3.2.10-1.sl5

BDII_top - 5 nodes v3.2.10-3.sl5

CE (CREAM/LCG) - 4 CREAM nodes v3.2.10-0.sl5, 1 CREAM node v3.2.6-0.sl5

FTS - v3.2.1-2.sl5 (Oracle backend)

glexec - v3.2.2-2.sl5

LB - 2 nodes v3.2.12-11.sl5

LFC - 7 nodes v3.2.7-2 (Oracle backend)

SE - Castor 2.1.10-0

UI - v3.2.10-1.sl5

VOBOX - v3.2.11-0.sl5

WMS - n/a

WN - v3.2.7-0

Comments

Plan to virtualize further Grid Services deployments using Microsoft Hyper-V

Regarding migration to EMI/UMD, no work yet, but would prefer to have access to some installation and maintenance recipes supported by developers (similar to what does exist for gLite).