1 / 15

General Status of the Project

This report provides an overview of the current status and future plans of the project, including feedback from the recent reviews, addressed issues, collaboration with other projects, and goals for production quality. The report also highlights the need for improved testbed operations, early standards adoption, and evolution of architecture and software based on user feedback. The project is focused on enhancing stability, quality, and production and aims to aggressively deploy the results while resolving licensing issues.

psawicki
Télécharger la présentation

General Status of the Project

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. General Status of the Project Fabrizio Gagliardi Project Leader

  2. Outline • Review of main issues and feedback from the EU review and EDG4 • Current status • Future plans • Announcements

  3. Review feedback follow up • ESA issues addressed in a dedicate ESA review early June • Role of ESA clarified and cost realigned with the original project budget • Comments on the software release process addressed and clarified in the recent retreat • “In future releases the reviewers will look for scalability, fault tolerance,and security issues to be addressed more in detail.” • Addressed at the retreat, see retreat detailed report in the next talk • “The project licensing issues are seen as important and the project is urged to resolve this quickly to aggressively deploy the results and ensure the project gets the credit for all the innovations it is making.” • Project licence agreed in line with GGF recommendations and Globus policy • “Concerning dissemination: there is the need for tangible quantitative results for the next review.” • PMB dissemination steering board appointed under leadership of Kors Bos • Collaboration with DataTAG and GRIDSTART (Rosy Mondardini)

  4. Future Plans (Technical), from EDG4 • “Expand and consolidate testbed operations” • need to improve the distribution, maintenance and support process, also understand what operating a Grid means • Testbed 1.2 released, new release policy and support structure discussed at the recent retreat • Project re-focussed on quality, stability and production • Requested by all application WPs and by LCG • Role of LCG being clarified • Plan for second test bed release in the future (when?) • “Enhance synergy with US via DataTAG-iVDGL and GLUE” • Being done via DataTAG

  5. Future Plans (Technical), from EDG4 • “Promote early standards adoption with participation to GGF and other international bodies” • Remarkable presence of EDG at the last GGF5 • “Evolve architecture and software on the basis of TestBed usage and feedback from users (consider converging to a common document with PPDG/GriPhyN, understand possible impact of OGSA)” • New ATF re-launched

  6. EDG4 Project conference feedback: Testbed • Applications want testbed stability (WP6 responsibility): • EDG 1.1.2 to be consolidated by mid-March • Separation of dev. testbed from production testbed • Support structure to be deployed ASAP • Test bed support structure remains an issue, addressed at the retreat • Platforms • EDG 1.2: use same Globus release as EDG 1.1 (i.e. GT2b21) • Support for RedHat 7.2 from EDG 1.4 onwards • ITeam to convene at CERN for 3 days each release • Sites • CERN: 200 CPUs available in 2002 • ‘LCFG lite’ (WP4) for installation (limited support)

  7. EDG4 Project conference feedback: MD/ware • Remove redundancy • Logging & Book-keeping (WP1) testing use of R-GMA (WP3) • R-GMA will use Spitfire security (WP2) with common RDBMS and Java development package • Improve integration • NetSaint(INFN) & WP7 integration • WP7, WP4, WP5 info providers with Info System (WP3) • Testing • Integration testing plan (WP6) • WP specific test-plans (unit tests)

  8. Project conference feedback: Architecture • Architecture group • Re-launched to produce a new architecture document • Security • Being addressed by the security group, still under-resourced • Globus/OGSA • Being followed by ATF, not very relevant for the time being • License • Finalized

  9. Current Status • Project at midlife point: • Good visibility in GGF • Major member of GridSTART • Good collaboration with CrossGrid, DataTAG, LCG, US Grid projects (GriPhyN, iVDGL, PPDG etc) Condor and Globus • Need refocus on production quality and demonstrate real applications • A project policy statement has been agreed by all WPs and issued by the project management (on the WEB) • A special effort with a consequent task force launched with one of the particle physics applications (Atlas). Deadline on September 16th • A special retreat held August 27-28 near CERN (with PPARC funds)

  10. EDG Production Quality Retreat • Goals: software process, T/B 1.2 deployment, Atlas exercise, future releases and tutorials • Results: • Software process issues identified by a common document with LCG (see Quality Process Document and Z. Sekera’s slides on the WEB) • First positive results from Atlas test of T/B 1.2 discussed • New architecture document discussed • Actions: • reinforce test-team , establish a certification test bed and develop auto-install and configuration tools

  11. EDG Production Quality Retreat • This project strengthening needs new resources and refocusing of existing ones • Additional new resources being negotiated with LCG: release manager, a certification and test team, end users support to be defined • Process to introduce new people to be worked out • Tutorial and road shows need to be further developed to disseminate the knowledge and facilitate introduction of new people and collaboration with other projects

  12. Plans for the future • Make plans to preserve current major asset of the project: probably the largest Grid development team in the world • EoI for FP6 ( www.cern.ch/egee-ei ), possible extension of the project, etc. • Demonstrate a stable and reliable T/B with appropriate support infrastructure • Develop a revised architecture to guide final release in 2003 • Progress with tutorials in view of a road show • Prepare for the next review (March 14, 2002)

  13. Announcements • New WP 8 Manager (Frank Harris, deputies: Paolo Capiluppi, Pier Giorgio Cerello, Laura Perini, Eric Van Herwijnen) • Thanks to Federico Carminati for the excellent work in driving the application part of the project up to now and through the first successful review • New member of the ATF: Lee Momtahan • New administrator (Karin Burghauser) in WP12 to alleviate the overload • Unfortunately Alexia’s unexpected temporary absence has put the project back in a stressful situation (to be discussed at the PMB)

  14. Announcements • EDG hands-on at the CSC02, September 15-28, near Naples, few posts could still be made available for EDG and related projects members • GGF6 in Chicago mid-October, IST 2002 in Copenhagen November 3-5, EU FP6 launching event 11-13 November in Brussels, SC02 Baltimore end November, next project EU review March 14th, EDG6 in Barcelona early May ‘03 and final project conference in Berlin end of October

  15. Announcements • First cost claim received, please respond to Karin • Please send your plenary presentations to: PNORBERT@SZTAKI.HU

More Related