1. www.egi.eu EGI-InSPIRE RI-261323 EGI-InSPIRE www.egi.eu EGI-InSPIRE RI-261323 Middleware-related EGI and WLCG activities

2. www.egi.eu EGI-InSPIRE RI-261323 Joined EGI WLCG testing activities SHA-2 and RFC testing EGI is planning to test all the new products entering UMD Tests can integrate the activities undergoing in WLCG Clients testing VO may need a more systematic testing workflow for the clients, to check every job type with every SE

3. www.egi.eu EGI-InSPIRE RI-261323 Use of repositories Discussions between EGI and WLCG to use the EGI repositories for WLCG specific products VOBOX Metapackages for EMI products

4. www.egi.eu EGI-InSPIRE RI-261323 Contributions to UMD After EMI, PTs will be grouped in platforms –Set of middleware products released in an integrated release –Current under discussion with EMI possible scenarios of grouping –If the grouping scenario does not satisfy the LCG VOs, WLCG can act as platform integrator Coordinating with the PTs to integrate the set of products relevant for the LCG use case Contribute to UMD with this integrated middleware components

5. www.egi.eu EGI-InSPIRE RI-261323 B/U: Community repository The products will be contained in separated sub-repositories. The tool under development will allow to upload multiple binaries (rpm or deb) per product, therefore a product could be actually a set of products. The directory structure of each product repository would follow a pattern like: production/community/ / / / / eg. production/community/torque/4/debian-squeeze/amd64/ Internal versioning schema (M.m.U-R) will be followed, however the ability will be given to the user in order to set his own version label and that version (if defined) will be exposed to the front-ends Initially the binaries that constitutes a given update (not a major), will be uploade in a scratch/unverified area where all operations, add & delete, will be permitted. Once the update is included into a major release exist into production, no file deletions will be allowed The user should be able to create one release candidate instance per product-flavor in order to test the produced repositories before he/she finally injects a release into the production.