Middleware Readiness WG

Mandate

• To help ensure that operations won't suffer when a site upgrades to version X of Middleware (MW) package Y, i.e. that versions are not only tested and certified internally by the Product Teams (PT), validated by the EGI staged rollout but also ready to be used in operation at the sites, integrated into the experiment workflows to the extent needed.
• The Working Group (WG) concentrates on WLCG sites in EGI, as the OSG sites are run in close collaboration with the LHC experiment US projects which advise on the software to be deployed. Potential OSG-EGI interoperability issues should be reported to the MW Officer and/or WLCG Operations Coordination.

Members

See the members of the e-group wlcg-ops-coord-wg-middleware.

JIRA tracker

The MWREADY tracker. Alternative Dashboard view.

Baseline Versions

WLCGBaselineVersions

Products

The list of candidate products for MW Readiness Validation will change over time, depending various factors.

Product	Contact	Test Repository	Production Repository	Used by which experiment	Comments
dCache	P. Fuhrmann	same as prod repo	dCache site + UMD	All
StoRM	A. Ceccanti	same as prod repo	StoRM site + UMD	ATLAS, CMS, LHCb
EOS	A. Peters , L Mascetti	same as prod repo	yum repos	All	ATLAS tests via Hammercloud
xrootd	A. Hanushevsky G. Ganis (vomsxrd plugin)	EPEL testing	EPEL stable	All
DPM	O. Keeble	EPEL testing	EPEL stable	All
FTS3	A. Manzi	EPEL testing	EPEL stable	ATLAS, CMS, LHCb
VOMS client	A. Ceccanti	same as prod repo	VOMS site + UMD + MAVEN for java stuff	All
HTCondor	Tim Theisen (HTCondor), Tim Cartwright (OSG Middleware), Rob Quick (OSG Ops)	downloads (Development Release)	downloads (Stable Release)	All	CMS position: The testing that OSG and in particular the glideinWMS developers do, is enough. ATLAS position here
CVMFS	J.Blomer, D.Dykstra	here disabled by default	cvmfs site	All	Release procedure. D.Dykstra runs the OSG tests.
ARC CE	Balazs.Konya (hep.lu.se)	EPEL testing (but also final tags in OS-specific repos) & ARC own repos for yum & apt release candidates	Nordugrid web site, includes prod and test variants	All	Puppet code
CREAM CE EL7, SL6	M. Verlato	UMD Preview	UMD	All
Argus	A. Ceccanti	Argus site, UMD Preview	UMD	All
UI		UMD Preview	UMD	All
WN		UMD Preview	UMD	All	Puppet code
DM clients	A. Manzi, O.Keeble	EPEL testing	EPEL stable	Atlas, CMS, LHCb

Experiment workflows

• ATLAS documentation
• CMS documentation

ALICE and LHCb have not had the resources to participate in these efforts.

Volunteer Sites

Procedure Guidelines

• The validation of a new version will need to have a deadline in practice.
• A new version may get deployed independently e.g. to fix ongoing issues.

Actions for the experiments

• The experiment writes and maintains a document with concrete instructions to the Volunteer sites on how to configure their parallel infrastructure for readiness verification through designated workflows.

Actions for the Volunteer Sites

• Set up an environment where new versions of the chosen MW can be quickly deployed, in order to be validated by the supported experiment(s). This will typically be parallel to the production infrastructure, but this is not a strict requirement.

WLCG MW Officer Tasks

See WLCGMWOfficerTasks.

The MW Officer can be reached through the wlcg-middleware-officer e-group.

Archive

MiddlewareReadinessArchive