60 likes | 226 Views
UMD and EMI Middleware. Kashif Mohammad Oxford. Middleware R elease F low. Software is developed by EMI. After internal testing, software is released in Stage Rollout(SR) repo and Early Adopters(EA) are informed.
E N D
UMD and EMI Middleware Kashif Mohammad Oxford
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.
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