Coordination of Middleware Development Standardization Sergio Andreozzi INFNCNAF

  • Slides: 15
Download presentation
Coordination of Middleware Development & Standardization Sergio Andreozzi INFN-CNAF sergio. andreozzi@cnaf. infn. it EGI-DS

Coordination of Middleware Development & Standardization Sergio Andreozzi INFN-CNAF sergio. andreozzi@cnaf. infn. it EGI-DS WP 3 Consolidation Workshop 29 -31 Jan 2008, CERN

Outline l EGI and Grid middleware development l Why should I care? l What

Outline l EGI and Grid middleware development l Why should I care? l What can I do? l l The experience of OMII-Europe Standardization Development R&D

Why a Middleware function in EGI l Multiple middleware stacks are in use in

Why a Middleware function in EGI l Multiple middleware stacks are in use in EU l l Required by NGIs l l l They exist in order to satisfy different needs All evolving in functionalities and technologies the progress in the standardization, convergence and full interoperability of the major stacks is expected to be long see WP 2 use case collection Commercial providers not appearing, nor will probably appear soon No Infrastructures without middlewares

Why a Middleware function in EGI l Enhancements will continue to be needed also

Why a Middleware function in EGI l Enhancements will continue to be needed also in the steady state l current VOs still are evolving their modus operandi l l new VOs/Scientific Communities normally need new functionalities l l l most users are researchers who are expected to evolve their way of using the Grid and keep on the cutting edge of technology e. g. WISDOM requiring the usage of different middleware stacks to access different types of resources pushing forward the evolution of the current components standardization process towards uniform interfaces and NGI’s to support more than 1 stack The users/VOs and the EGI “operation branch” will continue for quite some time needing specific enhancements in performance, reliability and/or functionality

Main Grid Middleware Stacks Available Today l From Europe l g. Lite universe l

Main Grid Middleware Stacks Available Today l From Europe l g. Lite universe l UNICORE l ARC l OMII-UK l From US: Globus, Condor/VDT From Asia: NAREGI, Crown. Grid l Europe plays a key role in middleware development

Grid Subsystems made in EU g. Lite OGSA capability UNICORE OMII-UK ARC Security. Attribute.

Grid Subsystems made in EU g. Lite OGSA capability UNICORE OMII-UK ARC Security. Attribute. Authority VOMS+SAML use VOMS-SAML VOMS-Client Security. Accounting DGAS, APEL RUS SGAS Data. Management. Storage Sto. RM, DPM SMS SMART-SE, ARC Gridftp Data. Management. Transfer FTS UNICORE FTS Data. Access. Relational OGSA-DAI Data. Access. Flat. Files GFAL TSI Information. Model GLUE (future) Information. Discovery Open. LDAP CIS Information. Monitoring Grid. ICE, R-GMA CIS, RUS-based LLView Exec. Man. Exec. Service GT 2 Gram, CREAM+BES TSS Grid. SAM Exec. Man. Job. Manager WMS XNJS Taverna & BPEL Man. Workflow Exec. Man. Candidate. Set. Gen Service. Orchestrator GLUE (future) Grimoires Open. LDAP Grid. Monitor Grid. Manager Brokered. Client Exec. Man. Exec. Plann. Service For a complete list, see http: //omii-europe. org/OMII-Europe/docs/DJRA 20. pdf

The Role of EGI for Grid Middleware l l Sustain European Grid Middlewares Coordinate

The Role of EGI for Grid Middleware l l Sustain European Grid Middlewares Coordinate the evolution of the current EU Middleware stacks: l l To introduce in an efficient and compatible way new functionalities and improvements To complete the transition towards the WS-world To adopt a complete agreed set of standards Promote convergence

The Role of EGI for Grid Middleware l Evolve current middleware stacks towards: l

The Role of EGI for Grid Middleware l Evolve current middleware stacks towards: l Achieving standard-based interoperability l l systems/organizations able to provide/accept services from other systems/organizations and to use the services exchanged to enable them to operate effectively together Adding new functionalities based on requirements from: l l l supported VOs potentially new VOs operations

Interoperability l Definition of coherent set of standards/profiles l Participation/contribution to standardization bodies l

Interoperability l Definition of coherent set of standards/profiles l Participation/contribution to standardization bodies l To consolidate the available standards by bringing feedbacks from productions environments l To promote and contribute to the definition of missing standards l To contribute to the definition of compliance test suites standards/ profiles requirements production environments standard bodies contributions software components

Interoperability l Development l l l Moving away from gateway-based interoperation towards standard-based interoperability

Interoperability l Development l l l Moving away from gateway-based interoperation towards standard-based interoperability Automatic standard conformance verification via test suites (supported by ETICS) Definition of common organizational procedures l l l Priorities identification Decision making Program execution

The OMII-Europe Experience l OMII-Europe: l l l Open Middleware Infrastructure Institute for Europe

The OMII-Europe Experience l OMII-Europe: l l l Open Middleware Infrastructure Institute for Europe EU-funded project: FP 6, RI Duration: May 2006 -> April 2008 Involved middleware stacks: l g. Lite, UNICORE, Globus, OMII-UK, Crown. Grid, VEGAGOS Mission: l Enabling of e-infrastructure interoperability by providing standards-based middleware components leveraging existing work and activities

OMII-Europe Working Cicle SA 2 JRA 2 New Components Standards Compliance Testing and QA

OMII-Europe Working Cicle SA 2 JRA 2 New Components Standards Compliance Testing and QA Standards Implementation Components IN Globus OMII-UK CROWN OUT Components JRA 4 JRA 1 Benchmarking Repository SA 1 JRA 3 Supported Components on Eval. Infrastructure SA 3 Integrated Components

OMII-Europe Main Contributions To Standard Adoption l OGSA-BES l l l GLUE l l

OMII-Europe Main Contributions To Standard Adoption l OGSA-BES l l l GLUE l l l Common definition/representation of Grid entities Definition as OGF standard, reference implementations VOMS-SAML l l l Functional interface for executing activites CREAM-BES and UNICORE-BES Functional interface for retrieving user privilege attributes Enabling UNICORE to access VOMS privilege attributes Accounting/RUS l l Functional interface for exchanging accounting information Exchanging accounting information across g. Lite, UNICORE and Globus

EGI and R&D l In connection with l l l Investigation of new approaches

EGI and R&D l In connection with l l l Investigation of new approaches l l l operation and middleware experts external organizations l academies and industries via incubator projects for medium-term evolutions Development of prototypes

Conclusion l l l Grid middleware is the foundation of the European research infrastructure

Conclusion l l l Grid middleware is the foundation of the European research infrastructure EGI recognizes the existence of and needs to support different middleware stacks satisfying different requirements A great set of components made in EU exist! l l these components must be further developed and sustained Standard-based Interoperability is the main path to follow to: l l Realize an integrated European Grid infrastructure with different types of resources Integrate with world-wide Grid infrastructures