1. Glite

2. Architecture Applications have access both to Higher-level Grid Services and to 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 Applications 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

3. Services

4. Components UI: User Interface CE: Computing Element SE: Storage Element WN: Worker Node WMS: Workload Management System VOMS: Virtual Organization Membership Service LB: Logging and Bookkeeping MonBOX: monitoring LFC: Logical File Catalog BDII: Berkeley Database Information Index, stores all infomation about the resources available in the grid infrastructure

5. Security Authentication based on X.509 PKI infrastructure – Certificate Authorities (CA) issue (long lived) certificates identifying individuals (much like a passport) Commonly used in web browsers to authenticate to sites – Trust between CAs and sites is established (offline) – In order to reduce vulnerability, on the Grid user identification is done by using (short lived) proxies of their certificates Proxies can – Be delegated to a service such that it can act on the user’s behalf – Include additional attributes (like VO information via the VO Membership Service VOMS) – Be stored in an external proxy store (MyProxy) – Be renewed (in case they are about to expire)

6. Security Local Centre Authorization Service (LCAS) handles authorization requests to the local computing fabric Local Credential Mapping Service (LCMAPS) provides all local credentials needed for jobs allowed into the fabric. Batch Local ASCII Helper – The protocol (BLAHP): provides a set of plain ASCII commands used by Condor-C (and CREAM) to manage jobs on the batch systems. – The daemon (BLAHPD): implements the helper daemon responsible for converting BLAHP commands into batch system actions, interpreting their results and reporting them in BLAHP format.