1. EGI Tech-Forum Cristina Aiftimiei

2. 14 Sett - Software Provisioning in EGI 1.UMD Roadmap – Steven Newhose Definition of UMD, who are the contributors: EMI, IGE, NGIs Describes the structure of the UMD & evolution of functional components Def of tech. providers, functionalities, capabilities -> on this EGI is interested Def of TCB composition – representatives from user & operations communities, tech providers, TU representatives Interactions between TCB, UCB & OMB determine UMD workflow Classification of EGI capabilities – functional (compute, data, security, operational capab.), security (authentication & authoriz., cred. management, user mangem.), data mangem. (file access, transfer, db access) operational (messaging, monitoring, accounting) Roadmap updated every 6 months

3. 14 Sett - Software Provisioning in EGI (2) 2.Softw Criteria Verification – C. Fernandez Verify soft before SR Major Rel – test by SP +SA2; Minor Rel – test by SP, SA2 random; Rev release – SP tests, verified by SA2 Tool to be used – RT Process timelines for each of the 4 release types – in MS402: emergency =1 day, revision<=9d, minor<=11d, major<=22d Metrics to be calculated: nr. new versions by SP, nr. rejected vers., nr incidents of a soft comp, etc Status – procedure ready, preparation checking template

4. 14 Sett - Software Provisioning in EGI (3) 3.EGI soft Reposit – K. Koumantaros Same presentation as on 17 Sett, SR session Purpose – contain UMD, JRA1-tools, CA Functionalities – apt, yum, web; Interaction with SP – tkts RT Workflow: SP -> Unverified repo->SR repo-> Prod repo Future – Soft Release Cycle in RT, discussions with SPs, scalability tests

5. 15 Sett - EGI User Support Services 1.User & Community Support Process/Team – S. Brewer Presentation of NA3 (User Community Coordination) as taken from DoW, 4 members Involved – documentation, training, new communties, app. porting support, req. gathering New communties -> VRC Technical services offered: training events (calendar), training repository (collection of training mat.), applications DB (catalogue of applic.), VO services (VOMS & VO DBs)

6. 15 Sett - EGI User Support Services (2) 2.EGI NA3 – Web site training services – D. Ferguson a registry of trainers, a calendar of training events, and a digital library of training materials – migrated from EGEE web to EGI.eu web 3.EGI Applications Database – K.V. Karageorgos AppDB=web portal, develop by INFN & IASA, now only IASA; contain Application & Tools, use cases, people, statistics; tech. info: Zend Framework, dojo, jQuery, MySQL data-backend 4.VO Serivec in Emi – J.Gomes: VO tech services, like VO info – CIC portal, VO registr. – CIC portal, core serv – VOMS, WMS, LFC, VO monitoring & testing services; Future: - Operations Portal (CIC portal), support to VRCs; VO-core services – prvided to small sites; improve & consolidate documentation

7. 15 Sett. – MPI, Current Status and Future Developments 1.MPI support: Users view and perspectives – A. Costantini, compchem experiences 2.Site deployment and MPI support – J. Walsh status in EMI: mpi-start, gLite-MPI_utils, yaim mpi; Issues – infra in transition->integration & interoperability (nagios/mpi testing, standards, accounting=multi-core/multi-thread) 3.Middleware support to MPI through gLite, ARC and UNICORE – E. Fernandez: future for ARC: - multi-core supp, multi-node execution, common MPI execution framework

8. 16 Sett - EMI 1.Introduction to EMI – A. Di Meglio: Mission statement, objectives Tech areas – Compute (A-REX, UAS-Compute, WMS, CREAM, MPI), Data (dCache, StoRM, UAS-Data, DPM, LFC, FTS, Hydra, AMGA), Security (UNICORE Gateway, UVOS/VOMS/VOMS-Admin, ARGUS, SLCS, glExec, Gridsite, Proxyrenewal), Infrastructure (L&B, Messaging, accounting, monitoring, virtualization/clouds support, information systems and providers) EMI evolution – after EMI = Specialized services, professional support and customization, EMI Reference Services pushed in RH, Ubuntu Release Plan – 3 Major releases + intermediate/integration exercise one EMI-1 Roadmap, from requirements, development, building/packaging/signing to prod 2.EMI Collaboration Programs – D. Cresti: DCI Collab: EDGI, EGI_Inspire, IGE, StratusLab, VENUS-C Participation in standardiz bodies – collab with SIENA Commericial partnerships – Google, RedHat Collab Environm – MoUs, Workshops, SLAs, Emi Web community Works with Emi program – MoUbased, tech. preview, access to developm testbed, dedicated tech supp

9. 17 Sett. - Software Rollout to the Production Infrastructure 1.Interim gLite Release Process – M.A. Pardillo Continue to maintain the EGEE process until first EMI release SR as before, directly from patches, after 1 week -> production Issues – lack of EA-sites for all profiles 2.Future perspectives and issues – M. David No interaction from SP with the EGI RT. Creation of the ticket will be done by EGI, with info from SR. Timelines for SR will be reviewed Communication with SP -> GGUS tkts Operations/sites requests to be informed about content of future releases Simplify SR procedure for EA sites Downtime flag for sites in SR? – conclusion -> not needed, no impact on availab/reliab.

10. 17 Sett. - Software Rollout to the Production Infrastructure (2) 3.EMI Release Process – C. Aiftimiei EMI Release baseline – all comp from ARC, UNICORE, gLite, dCaches, to which will be added new services, functionalities, etc Release policies: EMI-major (backward incompat, 1/year) components – Major in an Emi Major Rel; Minor – few times /year, improvements; Revision – bug fixes, 1/week or 2 weeks; Emergency – security bugs, as needed PT – design, implement, test, certify, 3-rd level support RfC – requests from GGUS, EGI, MCB Have priorities, discussed in EMI-EMT RC – equiv for gLite “patch” Guidelines are prepared for PT activities 4.SR Feedback from JRA1 – D. Cesini Monitoring tools – tried SR procedure for Nagios Updates – not a good experience Available for testing & tunning of the SR procedure