1 / 18

From requirements through objectives to development plans

From requirements through objectives to development plans. Bal ázs Kónya (Lund University) Technical Director 2 nd All-Hands meeting Lund, 31 May 2011. outline. EMI is about software, the mission of the project is to deliver software for DCIs What are we supposed to do after EMI 1

frye
Download Presentation

From requirements through objectives to development plans

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. From requirements through objectives to development plans Balázs Kónya (Lund University) Technical Director 2nd All-Hands meeting Lund, 31 May 2011

  2. outline EMI is about software, the mission of the project is to deliver software for DCIs • What are we supposed to do after EMI 1 • Workplan preparation • The high-level view on the Workplan Without dwelling into the details https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDNA132 Lund All-hands

  3. Congratulation! Kebnekaise, 12 May 2011 Lund All-hands

  4. Next peak to climb Matterhorn, April 2012 Lund All-hands

  5. How do we get there? We need a plan! Technical workplan: DNA1.3.2 Area workplans: DJRA1.1.2, DJRA1.2.2, DJRA1.3.2, DJRA1.4.2 Development plan (PT tasks): (tracker) Lund All-hands

  6. the plan: software portfolio EMI products (DNA1.3.2) • 58 products of different maturity level • 51 products are released as part of Kebnekaise • from AMGA to WMS • 3 products are under certification • FTS, Hydra, StoRM • 4 products are in its early development • STS, Pseudonimity, EMI Service Registry, EMI Messaging • 5 items are already dropped • Grid Manager, SCAS, SLCS, gstat-validation, update-crls • Couple of things are missing • EMI_datalib, EMI_auth, ... Lund All-hands

  7. the plan: product portfolio Lund All-hands

  8. the plan: requirements • EMI listens to its customers • Requirements of different kind were comunicated via direct email, verbally, EGI-TCB • PTB assesses and prioritizes requirements • Adjusts and/or creates new objectives • Continous process, though requirements don’t have an immediate effect on workplan • Everything is recorded and tracked: • https://savannah.cern.ch/task/?group=emi-req • Note: initial set of requirements already were taken into account by DoW and DNA1.3.1 • These are not in the tracker Lund All-hands

  9. the plan: top priority requirements • WMS should provide better feedback about jobs, automated resubmission of stuck jobs • Release EMI clients on SL5/32 • Standard file locations for logs and temporary files • Publish mw service version • Provide Nagios probes for EMI services • Better error messages (more verbose, informative) • Coherency of command line commands parameters • Coherency of APIs • Debian 6 support • Ubuntu support at least for EMI clients • CEs should support a set of LRMS • Reduce memory consumption of CREAM • Support for SL6 Lund All-hands

  10. the plan: not accepted requirements • Fixing known bugs before adding new features • Uniform logging • Improving (automatization) yaim configuration • Unicore GUI improvements Lund All-hands

  11. High-level Roadmap • Phase-1 (completed with Kebnekaise, see Morris’ JRA1 slide): • Software integration: created a distribution • Agreements: EMI-ES, STAR, GSI-replacement, messaging use cases • Design: EMI_authlib, EMI Registry • Completed tasks: server-side GLUE2, consistent SRM, ... • Phase-2 (Matterhorn) • Functionality integration • Implementation of all the agreements • Furher Agreements: compute accounting, delegation, ... • Delivery of the Consolidation plans • Design: AAI strategy, Cloud strategy • Phase-3 (Monte Bianco) • Realization of the consolidation plans • Implementation of AAI and Cloud strategy • Finalization of developments by bringing code to production level • New platforms Lund All-hands

  12. The plan: objectives Lund All-hands

  13. The plan: objectives Lund All-hands

  14. The plan: objectives Lund All-hands

  15. The plan: objectives Lund All-hands

  16. The plan: objectives Lund All-hands

  17. Development tasks • Comming soon: • Partially covered by the area workplans • https://savannah.cern.ch/task/?group=emi-dev Lund All-hands

  18. Thank you EMI is partially funded by the European Commission under Grant Agreement INFSO-RI-261611 Lund All-hands

More Related