1 / 34

1. ProActive context 2. GCM

Overview of GCM (Grid Component Model) and Grid COMP EU Project Denis Caromel OASIS INRIA-UNSA-CNRS I3S Melbourne, Jan. 29 2007. 1. ProActive context 2. GCM. ProActive and GCM. Structuring of the library 3 big layers Inner bricks Component Aspects: not only

kort
Download Presentation

1. ProActive context 2. GCM

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. Overview of GCM (Grid Component Model)and GridCOMPEU Project Denis Caromel OASIS INRIA-UNSA-CNRS I3SMelbourne, Jan. 29 2007 1. ProActive context2. GCM INSERT PROJECT ACRONYM HERE BY EDITING THE MASTER SLIDE (VIEW / MASTER / SLIDE MASTER)

  2. ProActive and GCM • Structuring of the library • 3 big layers • Inner bricks • Component Aspects: not only in Cp Box!

  3. ProActive • New GUIs • IC2D Eclipse • TimIt

  4. Shanghai Amsterdam Grid Computing with ProActive Melbourne Hierarchical Deployment Challenges: Programming Model, Scale, Latency, Heterogeneity, Versatility (protocols,firewalls...) Beijing

  5. JVM A A WBN! ProActive : Active objects A ag =newActive (“A”, […], VirtualNode) V v1 = ag.foo (param); V v2 = ag.bar (param); ... v1.bar(); //Wait-By-Necessity JVM ag v2 v1 V Wait-By-Necessity is a Dataflow Synchronization Java Object Active Object Req. Queue Future Object Proxy Thread Request

  6. A V Creating AO and Groups A ag = newActiveGroup (“A”, […], VirtualNode) V v = ag.foo(param); ... v.bar(); //Wait-by-necessity JVM Group, Type, and Asynchrony are crucial for Cpt. and GRID Typed Group Java or Active Object

  7. Objects to Distributed Components ComponentIdentity Cpt = newActiveComponent (params); A a = Cpt … .getFcInterface ("interfaceName"); V v = a.foo(param); A Example of a component instance V Truly Distributed Components Typed Group Java or Active Object JVM

  8. GCM + Scopes and Objectives: Grid Codes that Compose and Deploy No programming, No Scripting, … No Pain Innovation: Composite Components Multicast and GatherCast MultiCast GatherCast INSERT PROJECT ACRONYM HERE BY EDITING THE MASTER SLIDE (VIEW / MASTER / SLIDE MASTER)

  9. GCM: Grid Component Model • GCM Being defined in the NoE CoreGRID (42 institutions) • Open Source ObjectWebProActive implements a preliminary version of GCM • Service Oriented: NESSI relation exp. • GridCOMP takes: • GCM as a first specification, • ProActive as a starting point, and Open Source reference implementation. The vision: GCM to be the GRID GSM

  10. GridCOMP Partners

  11. GCM Architecture

  12. GCM Technical Structure • Component Specification as an XML schema or DTD • Run-Time API defined in several languages C, Java • Packaging described as an XML schema • Information for Deployment (Virtual Nodes, … Variables, File Transfer, …)

  13. Content and Activities • 1 - Primitive Component Programming • 2 - Legacy Code Wrapping, Interoperability • 3 - Composition and Composites, Deployment • 4 – Autonomic features • 5 – IDE for GCM (Composition GUI, etc.)

  14. Collective Interfaces

  15. Collective Interfaces • Simplify the design and configuration of component systems • Expose the collective nature of interfaces • Cardinality attribute • Multicast, Gathercast, gather-multicast • The framework handles collective behaviour • at the level of the interface • Based on Fractal API : • Dedicated controller • Interface typing  Verifications

  16. 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

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

  18. Transform: a list of invocations   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

  19. Status of GCM in ProActive • Partial implementation: • ADL schema, API, Multicast, Gathercast, … • Component GUI (prototype) • Distributed components for various applications: • Numerical, Legacy, … • On-going experiments: • up to 300+ CPUs

  20. Current GCM experiments in ProActive • JEM3D: 3D electromagnetic application: a single Cp on 300+ CPUs on Grid • Vibro-Acoustic application with EADS (legacy MPI coupling)

  21. Current GCM experiments in ProActive • IBM: • Security Fingerprint System • ATOS Origin: • Financial Application Optimization • GridSystems: • Wing Simulation • Telecom Application, EDR processing

  22. Update on ProActive and GCM (1) • New Version under preparation: • Nov. 10: ProActive Version 3.2 Beta • Jan. 26: ProActive Version 3.2 (After PlugTests’ Learning, New Web Site) • New features in 3.2 release: Next slide

  23. New Web Site with 3.2 Version

  24. Chinese Web thank to Tsinghua Univ.

  25. Update on ProActive and GCM (2) • New Features in ProActive Version 3.2: • New features in 3.2 release: • Conformance tests for Fractal, towards conformance tests for GCM • IC2D Eclipse Plugin • TimIt (Hierarchical, Visual) • Skeleton (improved, with File Transfer, Documentation) • gLite EGEE deployment updated • Support for Java 1.5 Generics: • Active Objects can be instantiated from Generic Classes • Some Warnings removed • Improvements in OSGi integration • Prototype TTools for UML modeling of GCM components (TBC)

  26. A Vision:GCM as EU’s GSM • Once upon a time: • GSM: Global System for Mobile communication • Process: • “critical decisions […] the GSM initiative became a success in Europe […] • Initially the strategy and technical specifications were agreed for Europe and […] incorporating all non-European requirements […] worldwide to participate ” From: Gsm & Umts: The Creation of Global Mobile Communications Standardization of GSM was crucial for EU advances in Mobile Telephony (Science and Business)

  27. A Vision:GCM as EU’s GSM GRID faces the same challenge: • Build Flexibility • Openness • Interoperability Objectives: Build a Word-Wide standard for Science and Business GRIDs: GCM

  28. GSM and GCM Pictures • GSM cells: • Components:

  29. GSM and GCM Pictures

  30. GSM and GCM Pictures

  31. Conclusion (1)Scientific Issues and DirectionsComponents in the membrane: • Membrane: • Meta-Objects  Java Objects • Components: • Active Objects • If Cp in Mb: • Active Objects as Meta-Objects • Not suited for all cases. If Dist. AO If light+local POJO TBD

  32. Conclusion (2) Key technology advancements • Programming the Grid with reusable, composable, components • vs. ad hoc solutions • Component for Separation of Concerns and AOP: • Gathercast allows to have synchronisation outside functional code • Deployment on various architectures • Super Computer Center, Clusters, data-center, desktop Grids, … • Interoperability with related Grid software • Integration into Service Oriented Architecture (SOA) INSERT PROJECT ACRONYM HERE BY EDITING THE MASTER SLIDE (VIEW / MASTER / SLIDE MASTER)

  33. Conclusion (3) Research Challenges • A general enough GCM, still efficient • Effective composition: Semantics, Deployment, Portability • Non-Functional Aspects: Security, Load-Balancing, Fault-tolerance, CP. Specif (Lotos, UML TTools, pNets) and Model Checking Verification INSERT PROJECT ACRONYM HERE BY EDITING THE MASTER SLIDE (VIEW / MASTER / SLIDE MASTER)

More Related