UMD and EMI Middleware

Kashif MohammadOxford

Middleware Release Flow• Software is developed by EMI.• After internal testing, software is released in Stage

Rollout(SR) repo and Early Adopters(EA) are informed.

• If no major issues is found by EA’s then software is released in emi production repo.

• EGI teams do some additional checks like security vulnerabilities of dependencies and integration with other EGI components.

• Software is released under UMD.

Component EMI UMD

EMI1 EMI2 UMD1 UMD2SL5 SL5 SL6 SL5 SL5 SL6

CREAM v1.13.5 V1.14.0 V1.14.0 UMD 1.5.0emi 1.13.5

WN V1.0.0 V2.0.0-1 V2.0.0-1 UMD 1.0.0emi 1.0.0

BDII V 1.1.0 V1.1.0 V1.1.0 UMD 1.6.0Emi 1.1.0

UMD 2.0emi 1.1.0

UMD2.0Emi 1.1.0

ARGUS V 1.40 V1.5.0 V1.5.0 UMD 1.3.0Emi 1.4.0

Component EMI UMD

EMI1 EMI2 UMD1 UMD2SL5 SL5 SL6 SL5 SL5 SL6

DPM V 1.8.3 V1.8.3 V1.8.3 UMD 1.7.0V 1.8.3

UMD2.0V1.8.3

UMD2.0V1.8.3

STORM V 1.8.2 V1.9.0 V1.9.0 UMD1.6.0V1.8.2

UMD2.0V1.9.0

UMD2.0V 1.9.0

• Single repository for all emi components– http://emisoft.web.cern.ch/emisoft/index.html

• Single repository for all UMD components– http://

repository.egi.eu/category/umd_releases/distribution/

• Upgrade supported from emi1 to emi2 and UMD1 to UMD2 for SL5.

• Status of EMI/UMD middleware in UK– http://www.hep.ph.ic.ac.uk/~dbauer/grid/

staged_rollout.html

Some Observations• UMD1 CREAM is well tested and working at many

sites.• UMD1 WN’s were only tested at Brunel and tier1.

Some issues with cms jobs • emi2 WN is now available on SL6 so it is likely that

sites will directly go to emi2 on SL6 from glite3.2• UMD DPM is also widely used. UMD DPM head node

works with glite3.2 pool nodes• EMI Argus is working with glite3.2 CREAM at Oxford.• http://www.hep.ph.ic.ac.uk/~dbauer/grid/

staged_rollout.html