www.eu-eela.org e-science grid facility for europe and latin america glite overview user and site...

•www.eu-eela.org

•E-science grid facility for Europe and Latin America•E-science grid facility for Europe and Latin America

gLite Overview

User and Site Admin Tutorial

Riccardo Bruno – INFN Sez. Catania

Dublin (Ireland), 15-18 September 2008

•www.eu-eela.eu •Dublin (Ireland) , Tutorial for User and Site Admin., 15.09.2008 – 18.09.2008•www.eu-eela.eu

Grid Aim

•2

Grid Systems & Applications aim is to:

Integrate

Virtualise

Manage

RESOURCEs and SERVICEs across different VOs.

VO – Individuals and/or Institutions having direct access to resources.


Grid Requirements

•3

•Heterogeneous (OSes, Devs, Apps.)

•VO Resource Sharing (Management, Security and Accounting)

•Resource Utilisation (Reservation, Metering, Monitoring and Logging)

•Job Execution (VO access, QoS, LCM, WFM, SLA)

•Data Services (Integration, Provisioning, Cataloguing, Metadata)

•Security (Authentication, Authorisation and Auditing)

•Administrative Costs (Provisioning, Deployment and Configuration)

•Scalability

•Availability (Disaster Recovery, Fault Management)

•Specific Requirements: (EGEE: HEP, BioMed)https://savannah.cern.ch/support/?group=egeeptf


??VO VO

VOUniversity of Catania

Italian CNR

Italian institute of Particle Physics

Garr-B

•4

•Many VOs need sharing of resources through services

• Access

• Allocate

• Monitor

• Use

Grid Requirements

• gLite Middleware: Layer between services and resources• gLite - Lightweight Middleware for Grid Computing

www.glite.org

•www.eu-eela.eu •Dublin (Ireland) , Tutorial for User and Site Admin., 15.09.2008 – 18.09.2008•www.eu-eela.eu •5

Other Grid Projects•Global Grid Forum - GGF

•Open Grid Services Architecture – OGSA

•EU DataGrid

•AliEn

•Globus

•Condor

• …

LCG

GTK2 Web services based

gLite-2gLite-1LCG-2LCG-1 gLite-3

GTK4

Behind gLite


•6

Available

Pending

gLite Services Overview

Job repository

Job repositoryJob repository

Job repository Job repository


Security Service

JobManagement

Monitoringand

Discovery

DataManagement

High-levelApplications and Tools

gLite - simplest view


Two possibilities: APIs and CLI.

API+CLI used to build High Level Grid Access UIs

Advanced GUIs (Grid2Win) and Web based portals (GENIUS, P-GRADE…)


Identify entities (users, systems and services) when establishing a context for message exchange (Who are you?).

Aim - Provide a Credential having a universal value that works for many purposes across many infrastructures, communities, VOs and projects.

gLite uses:

PKI (X.509) infrastructure using CAs as thrusted third parties.

MyProxy (http://grid.ncsa.uiuc.edu/myproxy/) extended by VOMS.

2 Important features: Single sign on, Delegation mechanism

CA and Trust domain: The set of all EGEE CAs is our Trust Domain.

Revocation: Identities must be revocated timely

Credential Storage: Local or delegated credential (Services or Users)

Privacy Preservation: Preserve the use of personal data by mutual AutH

Security Consideration: Trusted computing env. Do not serve a whole VO.

Authentication


Authorization

Allows or denies access to services, based on policies.

•Agent: The user interacts with a centralized Authorization Server•Push: Authorization Services issue Tokens.•Pull: The resource asks to the Authorization Services.

Authorization Sources (VOMS):

•Attribute Authority (AA): User <-> Set of Attibutes. •Policy Assertions: Third party policies. (CAS)

•VOMS – Virtual Organization Membership Serivce•Attribute Certificate

•FQAN

•www.eu-eela.eu •Dublin (Ireland) , Tutorial for User and Site Admin., 15.09.2008 – 18.09.2008•www.eu-eela.eu •12•To change: View -> Header and Footer

Information services are vital low level component of Grids.

•www.eu-eela.eu •Dublin (Ireland) , Tutorial for User and Site Admin., 15.09.2008 – 18.09.2008•www.eu-eela.eu •13•To change: View -> Header and Footer

Modeling of Grid Information

• GLUE Schema (Open Grid Forum)– Abstract modeling for Grid resources– Mapping to concrete schema

RDBMS LDAP XML Others

• More information …– http://glueschema.forge.cnaf.infn.it/Main/HomePage


•Accumulates information about the resource usage done by users or groups of users (VOs).

•Information on Grid Services/Resources needs sensors (Resource Metering, Metering Abstraction Layer, Usage Records).

•Records are collected by the Accounting System (Queries: Users, Groups, Resource)

•Grid services should register themselves with a pricing service when accounting for billing purposes.

•INFN enanced the Accounting System also to Data Storage (SAGE)•http://sage.gilda-forge.ct.infn.it

Accounting


•WMS set of middleware components responsible of distribution and management of jobs across Grid resources.

•Two core components of WMS:

• WM: accepts and satisfy requests for job management.Matchmaking is the process of assigning the best available resource.

• Logging & Bookeeping : keeps track of job execution in term of events: (Submitted, Running, Done,...)

Workload Management


•Service that represents the computing resource that is responsible of the job management: (submission, control, etc.)

•The CE may be used by a Generic Client: an end-user interactingdirectly with the Computing Element, or the Workload Manager, which submits a given job to an appropriate CE found by a matchmaking process.

•Two job submission models (accordingly to user requests and site policies):

• PUSH (Eager Scheduling) (jobs pushed to CE),

• PULL (Lazy Scheduling) (jobs coming from WMS when CE has free slots)

•CE responsible to collect accounting information.

Computing Element


SE Services are at least:

•Storage back-end (Drivers and Hardware)

•SRM Interface (Storage Specific: dpm, rfio, …)

•Transfer service (Protocols: GridFTP(gsiftp), glubus-url-copy, …)

•Native POSIX like file I/O API (GFAL)

•Auxiliary Accounting and Logging services (accounting: SAGE)

Storage Element

Data are stored on Disk Pool Servers or Mass Storage Systems


OS like file access metaphor.

• LFN (Logical file name)

• GUID (Grid unique identifier)

• SimLinks

• SURL (Site URL)

• TURL (Transfer URL)

Catalog


•Data Scheduler (DS) Keeps track of user/service transfer requests•File Transfer/Placement Service (FTS/FPS) •Transfer Queue (Table)•Transfer Agent (Network)

Data Movement


AMGA – Arda Metadata Grid Application

•23

Metadata

• Metadata is data about data• On the Grid: information about files

Describe files Locate files based on their contents

• But also makes DB access a simple task on the Grid Many Grid applications need structured data Many applications require only simple schemas

Can be modelled as metadata

Main advantage: better integration with the Grid environment Metadata Service is a Grid component Grid security Hide DB heterogeneity


•Configuration and Instrumentation Service – Queries service state.

•Agreement Service – Implements a communication protocol for the SLAs.

•Bandwidth Allocation & Reservation service (BAR) – Controlling, Balancing and Manage Network flows.


• Grid Access– User Iinterface– Info system– Security

• MyProxy (Normal, Long term)

• VOMS

• Job submission– WMS– Computing Element– Worker Node

• Data management– Catalogs– Storage elements

BDII

Grid Services Interaction


• gLite Home Page– www.glite.org

• gLite Architecture – https://edms.cern.ch/file/476451/1.0/architecture.pdf

• gLite Architecture Design v 1.5– https://edms.cern.ch/file/606574/1.0/design.pdf

•26

Grid Services Interaction

www.eu-eela.org e-science grid facility for europe and latin america glite overview user and site...

Documents