1 / 21

Advancing GCM: Architecture, Components, and Interoperability

This session explores the current status of the Grid Component Model (GCM) and various advancements in areas such as wrapping CCA components, large-scale experiments, non-functional features, and metadata framework. Talks will cover topics like GCM architecture and principles, component specification, hierarchical composition, interface definition, packaging, interoperability, and more. Attendees will gain insights into the latest developments in GCM and its applications in grid programming.

rkerns
Download Presentation

Advancing GCM: Architecture, Components, and Interoperability

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. Session 2: task 3.2 GCM,Kracow, June 27 2006 Current status of GCM Denis Caromel (10 mn each talk) Wrapping CCA Components as GCM ComponentsMaciej Malawski, Marian Bubak Grid and Large Scale GCM Component ExperimentsNikos Parlavantzas, Vladimir Getov Non-Functional Features and Autonomic GCM ComponentsJeremy Buisson, Marco Danelutto, Marco Aldinucci Towards GCM Metadata Framework Alexander Bolotov, Vladimir Getov

  2. Current status of GCM Denis Caromel GCM Architecture and Principles Specificities: Multicast, Gathercast Towards Autonomy Strongly related EU project: GridCOMP Interactions and Relations

  3. A Fractal Component

  4. GCM in short • 1. Component Specification: ADL, an XML schema or DTD • Hierarchical: Primitives and Composites • 2. Definition of Interfaces: • server, client, event, stream, ... • various interface specifications: Java Interface, C++ .h, Corba IDL, WSDL, etc. • 2. Run-Time API defined in several languages • 3. Packaging described as an XML schema (Fractal packaging) • 4. Specification of Grid aspects: • Parallelism, Distribution, Virtual Nodes, QoS, File Transfer, etc. • 5. Interoperability: • Export WSDL, use Web Services

  5. Programming Model – Component Model • Component = Interface  Remote Method Invocation • GRID (Distribution and Parallelism): • One to many communications • Scattering, Gathering, Redistributing • Asynchrony • GCM = Unifying RMI and GRID: • Scattering, Gathering, Redist. at the Cp. level : Specif • High-Level Composition • To be compared with low-level, Message Based MPI

  6. Multicast interfaces • Transform a single invocation into a list of invocations • Multiple invocations • Parallelism • Asynchronism • Dispatch • Data redistribution (invocation parameters) • Parameterisable distribution function • Broadcast, scattering • Dynamic redistribution (dynamic dispatch) • Result = list of results

  7. Multicast interfaces Results as lists of results Invocation parameters may also be distributed from lists

  8. Gathercast interfaces

  9. Transform a list of invocations into a single invocation Synchronization of incoming invocations ~ “join” invocations Timeout / drop policy Bidirectional bindings (callers  callee) Data gathering Aggregation of parameters into lists Result: redistribution of results Redistribution function Gathercast interfaces

  10. SCATTERING: Multicast N components M components GATHERING: Gathercast REDISTRIBUTION from M to N On-going : MxN Redistribution

  11. On Going: Dynamic Controllers • An extension of Fractal: controllers can be components (they still belong to the membrane)

  12. Extension of the Fractal-ADLfor Behavior Specification of Components • with Charles Univ., Prague, Czech Rep., Santiago, Chile, … • Goal: • Specifying and verifying behavior • Coherent notations for compatibility • Mean: • Extension of the ADL • Behaviors can be attached to components, to interfaces, or to bindings • Referring to external formats: e.g. Lotos specification

  13. Typical Usage : • . Finite Model Generation Tool Input : ADL + Interfaces + Behaviour specs Model Checker

  14. WP 2 GRID PROGRAMMING WITH COMPONENTS: AN ADVANCED COMPONENT PLATFORM FOR AN EFFECTIVE INVISIBLE GRID

  15. Anim

  16. GridCOMP Objectives • Get money to implement and experiment with the GCM • Build a solid, usable implementation with tools • Asses GCM in an industrial framework • Provide feedback to CoreGRID

  17. GridCOMP Partners

  18. Approach & Work Packages Structure • Grid Component Model (GCM, NoE CoreGrid) as a starting point, with ObjectWeb ProActive implementation • Interoperability with other standards: EGEE gLite, UNICORE, NorduGrid, Globus, Web Services, etc., • Coordination with the NESSI initiative: • involvement of ObjectWeb, IBM, ATOS • Structure: • WP 2: core Components Framework Implementation • WP 3: Non-Functional Cp Feature • WP 4: Grid IDE • WP 5: Industrial Use Cases

  19. Relations : WP 3 -- GridCOMP • GridCOMP: • Implementation of GCM specification • Experiments with Industrial Use Cases • Assessment and Recommendations • CoreGrid: • Specification of the GCM • Experiments with Research, Scientific Use Cases Integration • Contributions to the Open Source base

  20. Session 2: task 3.2 GCM,Kracow, June 27 2006 Current status of GCM Denis Caromel (20 mn each talk) Wrapping CCA Components as GCM ComponentsMaciej Malawski, Marian Bubak Grid and Large Scale GCM Component ExperimentsNikos Parlavantzas, Vladimir Getov Non-Functional Features and Autonomic GCM ComponentsJeremy Buisson, Marco Danelutto, Marco Aldinucci Towards GCM Metadata Framework Alexander Bolotov, Vladimir Getov

More Related