UMD, EMI, etc

John Gordon, STFC

GDBCERN, 18th April 2012

2

• This is not meant to be a criticism of anyone or any project.

• Issues have been observed that affect WLCG and others

• They may not be substantive but better that everyone knows the solution.

Strawman

3

• Quality of software reaching production. There have been a number of issues with the products. They might be EMI's fault but they have made it into UMD so it is also an issue for you. EMI are proposing a testbed earlier than staged rollout. Should this be coordinated so it is clear who is testing what/when.

Quality of software

4

• biomed were recently affected when their Hydra client was not included in the EMI WN release because it had not benn released yet in EMI.

• I think EGI should have a view on what is included. WLCG too.

WN content

5

• Sites are having to use several repositories (EMI, glite as well as UMD) because required components (eg WMS) have not been included. Can we hear about your policies for inclusion and reasons why certain products are failing. Can WLCG facilitate a plan for resolution?

Content of UMD