Project introduction

transcript

Project introduction Mike Mineter

m.mineter@ed.ac.ukTOE-NeSC, Edinburgh

2EU project: RIO31844-OMII-EUROPE

• This file contains several short talks given during the OMII-Europe / NextGRID event in Edinburgh on 17 March 2008

• A fuller set of material is here , the OMII-Europe tutorial for D-Grid.

What is OMII-Europe

• OMII-Europe stands for– Open Middleware Infrastructure Institute for Europe

• It is an EU-funded project: FP6, RI• It has an initial duration of 2 years

• May 2006 -> April 2008

• It has been granted a contribution of 8M €• It involves 16 partners

– 8 EU– 4 USA– 4 China

Vision

“ e-Science having

easy access and use

of Grid resources

in heterogeneous

e-infrastructures

crossing national,

pan-European

and global boundaries “

Mission

“ Enabling of

e-infrastructure

interoperability

by providing

standards-based

middleware components

leveraging existing work

and activities “

Further Information

Later talks!

http://omii-europe.org

Current status of grids: the need for standards

Mike Mineterm.mineter@ed.ac.uk

TOE-NeSC, Edinburgh

Outline

• Effect of the grid islands

• Bridging grid islands

• What OMII-Europe is Doing

Revision

• Grid supports “virtual computing across administrative domains”

• EGEE and most grids have Virtual Organisation concept– A VO is a collaboration– Shares resources– Express membership of VO, its groups and roles in

some way as a basis for grid services to authorise users’ requests

Grid Islands

gLite Globus Toolkit 4

UNICORE CROWN

Isolate:

Computers

Expertise

Effect of grid islands

• A VO can only use resources that share the same Authorisation/Authentication basis– Can’t span UNICORE and EGEE grids for example

• EGEE – EU-funded grid infrastructure promoting collaborative research by sharing access to data and clusters, gLite with VOMS (Virtual Organisation Membership Service)

• DEISA – grid spanning HPC resources, built on UNICORE middleware

• Applications must be written for specific grid• Disincentive for tool / high level service developers• Need standards that all grids accept… and are complete!

– “Complete” = if standards are supported, then services are interoperable

Bridges – to enable…

UNICORE CROWN

“The global grid”

VO to span gridsApplication portability

Bridges – for interoperability

UNICORE CROWN

Job execution

Data access and integration

Accounting

Info Services

AuthN, AuthZ

Approaches to Interoperability

• Adapters-based:– The ability of Grid

middleware to interact via adapters that translate the specific design aspects from one domain to another

• Standard-based:– the native ability of Grid

middleware to interact directly via well-defined interfaces and common open standards

* definition inspired by OGF GIN CG

Who Benefits from Interoperability?

• Grid Developers– A single standard set of services on all Grid middleware systems– Applications portable across different Grid middleware systems

• E-Science application users– Common ways for accessing any e-infrastructure resources– Potential access to a significantly larger set of resources

• E-resource owners– Reduced management overheads as only a single Grid

middleware system needs deployment– Potential for greater resource utilisation

“For the Grid to deliver on it’s promises interoperability needs to be taken for granted like network interoperability”

How to achieve interoperability?

• Application level– SAGA – support same API on all grids– Interoperability or simply easier, portable applications?

• Need – Conform to standards– BUT standards are not enough (at present)– E.g. Common security basis

• OMII-Europe: build components in negotiation with gLite, UNICORE, Globus, CROWN

Web Services Grid Technology

Grid Services• Commerce

• Standards

• Tools

• Research driven

• Data-intensive

• Compute intensive

• Collaboration – sharing of resources

- Trust: opening resources

October 2001 View

Open Grid Services Architecture

What OMII-Europe is Doing?

• Initial focus on providing common interfaces and integration of major Grid software infrastructures

• Common interoperable services:– Database Access– Virtual Organisation Management– Accounting– Job Submission and Job Monitoring

• Infrastructure integration– Initial gLite/UNICORE/Globus interoperability– Interoperable security framework– Access these infrastructure services through a portal

The Virtuous Cycle – Technology transfer with Grid projects and standards organisations

Globus

OMII-UK

Components

JRA2New Components

Standards Implementation

Standards Compliance Testing and QA

Benchmarking

Integrated Components

Supported Components on Eval. Infrastructure

Repository

You will easily be able to find out!

Evaluation infrastructuresCommon security base

Components based on standards

OMII-Europe Gateway (portal)

Components – How easy are they to use?

Participation in Middleware Standardisation• Most project participants involved as member/observer in many OGF WG• 11 project participant hold senior positions in

– OGSA DAIS WG (Database Access and Integration Services)– OGSA RUS WG (Resource Usage Server)– OGSA BES WG (Basic Execution Service)– OGSA JSDL WG (Job Submission Description Language)– GIN CG (Grid Interoperability Now)– OGSA-AuthZ-WG (Authorization)– GLUE WG – GFSG WG (Grid File System)– RM WG (Reference Model)– OGSA Naming WG– Technical Standards Committee– GSA RG (Grid Scheduling Architecture)– GRAAP WG (Grid Research Agreement Allocation Protocol)– OGSA BYTE IO WG– OGSA D WG (Data)– OGSA DMI WG (Data Movement Interface)

Summary• OMII-Europe is a 24 Month EU funded project with 16 partners

to establish grid infrastructure interoperability through implementing a set of agreed open standards on all middleware platforms

• OMII-Europe is implementing a number of components that will allow identically specified jobs to be run, managed and migrated to different middleware platforms

• Users can try interoperability on the OMII-Europe evaluation infrastructure, or obtain services for installation on their own resources from the OMII-Europe repository

• We anticipate OMII-Europe services will be integrated into standard middleware distributions - already in UNICORE 6

Further Information

http://omii-europe.org

Information Schema and Mike Mineter

Next slide is to illustrate how…

• OMII-Europe is:– Leading in standards initiatives– Alert to non-grid world– Building with others’ software where possible– Cooperating – the glue between different middleware

developers and seeking community agreement

And for information systems, the GLUE 2 …

Context: Summary View

Slide from Sergio Andreozzi

More standards-related bodies….

• Web-Based Enterprise Management (WBEM) - seeks to unify the management of distributed computing environments. http://wbemservices.sourceforge.net/ – Common Information Model

• Distributed Management Task Force http://www.dmtf.org/homeDeveloping management standards & promotinginteroperability for enterprise & Internet environments

Security Mike Mineter

Not only Classic VOMS but also SAML-VOMS

• Same VO database can release:attribute Certificates signed SMAL assertions

Venturi et al. [3]

http://www.unicore.

• Open standards-based SAML-compliant VOMS is the foundation for interoperability

• Works not onlyin conjunction withOGSA-BES

• The basic idea worksin principle with allWeb services

SAML-based Interoperability

Marzolla et al. [4]

Technical: Interoperability approach in OMII-Europe

e-InfrastructureInteroperability by using more

than one technology!

Venturi et al. [3]

From Morris Riedel, OMII-Europe training for D-Grid

Job execution: Interoperability scenario Mike Mineter

SLIDES: From Morris Riedel, OMII-Europe training for D-Grid

VOMS in Interoperability Scenario WISDOM

SAML- based Attribute Authority (AA) VOMS

gets central role & middleware independent

http://www.unicore.

• CREAM-BES Support SAML-based VOMS authorization

• Developed by

• gJAF Framework usesSAML assertions to grantor deny access

CREAM-BES + SAML VOMS

http://www.unicore.

• Used in conjunction withAuthZ Attribute Exchange Profile (OGF AuthZ group)to obtain a SAML assertionfrom a Policy Information Point (PIP)

• SAML assertions are transported in the SOAPheader during WS calls– E.g. WS-Security Extensions

• Developed by

SAML-based VOMS Support in UNICORE 6

Available Components of this Scenario (1)

• CREAM-BES (gLite) released in OMII – Europe repository– http://repository.omii-europe.org/projects/

• SAML VOMS released in OMII – Europe repository– http://repository.omii-europe.org/projects/

• SAML-based VOMS Support and OGSA-BES for UNICORE 6 released in OMII – Europe repository– http://repository.omii-europe.org/projects/

• Also released on the UNICORE@SourceForge platform– http://www.unicore.eu

Data management Mike Mineter

Data Access

• Porting OGSA-DAI 3.0 from Globus / OMII-UK to other middleware distributions available throughout Europe and China– UNICORE– gLite

(port = GT4 + classic VOMS)

– CROWN

Project introduction

Documents