1 / 11

EGEE Middleware

EGEE Middleware. General presentation Last update May 2007. Grid middleware . The Grid relies on advanced software, called middleware , which interfaces between resources and the applications The Grid middleware: Basic services Secure and effective access to resources High level services

argus
Télécharger la présentation

EGEE Middleware

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. EGEE Middleware General presentation Last update May 2007

  2. Grid middleware • The Grid relies on advanced software, called middleware, which interfaces between resources and the applications • The Grid middleware: • Basic services • Secure and effective access to resources • High level services • Optimal use of resources • Authentication to the different sites that are used • Job execution & monitoring of progress • Problem recovery • Transfer of results back to the user EGEE Middleware

  3. File and ReplicaCatalogs User Interface Resource Broker Computing Element Storage Element Site X Job submission Information System submit query retrieve update credential publish state submit query retrieve AuthorizationService EGEE Middleware

  4. Middleware structure Applications • Access for applications to: • Higher-level Grid Services • Foundation Grid Middleware • Higher-Level Grid Services are supposed to help the users building their computing infrastructure but should not be mandatory • Foundation Grid Middleware will be deployed on the EGEE infrastructure • Must be complete and robust • Should allow interoperation with other major grid infrastructures • Should not assume the use of Higher-Level Grid Services Higher-Level Grid Services Workload Management Replica Management Visualization Workflow Grid Economies ... Foundation Grid Middleware Security model and infrastructure Computing (CE) and Storage Elements (SE) Accounting Information and Monitoring Overview paper http://doc.cern.ch//archive/electronic/egee/tr/egee-tr-2006-001.pdf EGEE Middleware

  5. Grid Middleware Key success factors for production quality software: • Strict software process • Use industry standard software engineering methods • Software configuration management, version control, defect tracking, automatic build system, … • Conservative in what software to use • Be careful about “cutting-edge” software • Deployment on some 200 sites cannot assume a homogenous environment – middleware needs to work with many underlying software flavors • Be aware of evolving standards • Evolving standards change quickly (and sometime significantly cf. OGSI vs. WSRF) – impossible to keep pace on almost 200 sites You will not develop and deploy your PhD project on a production Grid infrastructure There is a long (and tedious) path from prototypes to production EGEE Middleware

  6. EGEE Middleware: gLite • gLite 3.0 ⇨ Merger of LCG 2.7 and GLite 1.5 • Exploit experience and existing components from VDT (Condor, Globus), EDG/LCG, and others • Develop a lightweight stack of generic middleware useful to EGEE applications (HEP and Biomedics are pilot applications). • Should eventually deploy dynamically (e.g. as a globus job) • Pluggable components – cater for different implementations • Focus is on providing a stable and usable infrastructure EGEE Middleware

  7. gLite Services gLite offers a range of services EGEE Middleware

  8. gLite Key Concepts • Centered around VOs • It’s ultimately the VO who gets resources allocated and need to decide how to best use them (share them among the VO users) • Distinguish between infrastructure and VO services • Infrastructure services • Operated and trusted by the resource administrator • Implement site policies • Including what share of the resources are allocated to a VO • Provide the required security, auditing, and accounting • Grid and standard services • E.g. batch system, gatekeeper, gridFTP, … EGEE Middleware

  9. Middleware Challenges • Security: • Different administrative domains interconnected on the Grid and the need to establish mutual trust • Data management: • Need to store and transfer data on different storage systems using different access technologies • Workload: • Computational tasks of thousands of users need to be managed and monitored on the available Grid resources EGEE Middleware

  10. gLite Software Process Development Directives Error Fixing Software Serious problem Integration Certification Pre-Production Deployment Packages Testbed Deployment Problem Fail Production Infrastructure Pre-Production Deployment Fail Integration Tests Pass Functional Tests Pass Fail Installation Guide, Release Notes, etc Scalability Tests Release Pass EGEE Middleware

  11. Summary • gLite 3.0 merges LCG 2.7 and gLite 1.5 • EGEE provides a complete middleware stack ⇨Security infrastructure, information system and monitoring, workload management, data management • Developed according to a well defined process ⇨Controlled by the EGEE Technical Coordination Group • Development is continuing to provide increased robustness, usability and functionality • Responsive to user needs • Deployed on EGEE production service www.glite.org EGEE Middleware

More Related