1. Elton Mathias and Jean Michael Legait 1 Elton Mathias, Jean Michael Legait, Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis, IUF CoreGrid Summer School 2007 ProActive / GCM

2. Elton Mathias and Jean Michael Legait 2 GCM: Grid Component Model –GCM being defined in the NoE CoreGRID Open Source ObjectWeb ProActive – implements a preliminary version of GCM GridCOMP takes: –GCM as a first specification, –ProActive as a starting point, and Open Source reference implementation. GCM Components Scopes and Objectives: - Grid Codes to Compose and Deploy - No programming, No Scripting, …

3. Elton Mathias and Jean Michael Legait 3 GCM Partners

4. Elton Mathias and Jean Michael Legait 4 Rationale: grid applications RequirementsSolutions with ProActive/GCM DistributionDistributed components Multiple administrative domains Handled by the middleware Heterogeneity Portable implementations, interoperability Legacy codeEncapsulation, interoperability Performance Legacy code, parallelism Complexity Hierarchies, collective interfaces Dynamicity Adaptation and coherent reconfigurations Tools ADL, GUI, Packaging

5. Elton Mathias and Jean Michael Legait 5 Approach Based on the Fractal Model INRIA - France Telecom, V1 in 02 Fractal requires extensions for Grid Computing Specified in the Grid Component Model (CoreGRID) However: – Distribution ? – Deployment ? – Parallelism ? Simple, extensible, hierarchical, dynamic Separation of concerns (controllers) General model, core concepts – Encapsulation – Strict Definition – Assembly and deployment units

6. Elton Mathias and Jean Michael Legait 6 Some important Fractal Concepts Content Controller (or membrane) Server Interface Client Interface Bind(ing) Functional interface Control (or non-functional) Interface

7. Elton Mathias and Jean Michael Legait 7 Implementation of Fractal based on ProActive middleware Model – conformant up to level 3.3 (fully compliant with the API) –Based on MOP architecture: Component as Active Object –Distributed components, asynchronous communications (futures) –Benefits from underlying features of the middleware Middleware services (Fault Tolerance, Security, Mobility etc..) Deployment framework (Grids) –Sequential processing of requests in each component –Main extensions to fractal: deployment, collective interfaces –Configurable and extensible ProActive/Fractal

8. Elton Mathias and Jean Michael Legait 8 Standard Fractal Interfaces Only 1 to 1 communications! collective interfaces –Multicast –Gathercast

9. Elton Mathias and Jean Michael Legait 9 Collective Interfaces Simplify the design and configuration of component systems Expose the collective nature of interfaces –Cardinality attribute Multicast, Gathercast, gather-multicast Based on ObjectWeb Fractal API : –Dedicated controller –Interface typing Verifications The framework handles collective behaviour at the level of the interface

10. Elton Mathias and Jean Michael Legait 10 Multicast interfaces single invocation list of invocations Multiple invocations – Parallel – Asynchronous – Selective – Dynamic Data distribution –Automatic –Parameterizable distribution function –Broadcast, scattering, reduction –Explicit typing, Parameterized collections Compatibility verified at runtime when binding

11. Elton Mathias and Jean Michael Legait 11 Multicast Interfaces Illustrated Configurable distribution policies Parallelism Strong typing Configurable distribution policies Parallelism Strong typing

12. Elton Mathias and Jean Michael Legait 12 Gathercast Interfaces Synchronization – ~ join invocations –Customizable: wait-for-all, wait-for-some, elections –Timeout Data distribution - Aggregation / reduction of parameters - Redistribution of results - Symmetrical to multicast list of invocations single invocation

13. Elton Mathias and Jean Michael Legait 13 Gathercast Interfaces Illustrated Configurable distribution policies Synchronization Strong typing Configurable distribution policies Synchronization Strong typing

14. Elton Mathias and Jean Michael Legait 14 Architecture Description Language (ADL) Used to configure and deploy component systems. The ADL has been updated and is now an extension of the standard Fractal ADL: –allowing to reuse ProActive-specific features like deployment Support to Collective Interfaces definition (comming soon!)

15. Elton Mathias and Jean Michael Legait 15 Virtual Nodes Permits a program to generate automatically a deployment plan: find the appropriate nodes on which processes should be launched. In the future: –adjunction of more sophisticated descriptions application requirements (hw description, topology, QoS, …)

16. Elton Mathias and Jean Michael Legait 16 Virtual Nodes in the ADL Renames a VN Exports a VN name Pa.: final version of the GCM specification will precisely define the syntax for the virtual node definition, and their composition.

17. Elton Mathias and Jean Michael Legait 17 Ongoing Work – Grid Component Model, adaptive components – Model checking, formal verification of behavioral properties – Components for scientific computing (and legacy code wrapping) – VERCORS: VERification of models for distributed communicating COmponants, with safety and Security Vercors editor

18. Elton Mathias and Jean Michael Legait Vercors Editor UML2 Component Diagram Integrated into the Eclipse environment Fast system specification Easy navigation through statical errors

19. Elton Mathias and Jean Michael Legait Vercors Editor UML2 State-Machine Diagram Component behaviour specified with UML State Machines Formal verification based on Labelled Transition Systems

20. Elton Mathias and Jean Michael Legait 20 Lets practice a little more ! http://proactive.objectweb.org

21. Elton Mathias and Jean Michael Legait 21 Conclusion