Denis Caromel 1 Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis, IUF Strong Programming.

Slides:



Advertisements
Similar presentations
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,
Advertisements

Agents & Mobile Agents.
Christian Delbe1 Christian Delbé OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis November Automatic Fault Tolerance in ProActive.
M. Muztaba Fuad Masters in Computer Science Department of Computer Science Adelaide University Supervised By Dr. Michael J. Oudshoorn Associate Professor.
European Commission Directorate-General Information Society Unit F2 – Grid Technologies INSERT PROJECT ACRONYM HERE BY EDITING THE MASTER SLIDE (VIEW.
Distributed System Structures Network Operating Systems –provide an environment where users can access remote resources through remote login or file transfer.
26 Mai 2004 Séminaire Croisé : Sécurité Informatique Ubiquitaire1 Security Architecture for GRID Applications Séminaire Croisé Sécurité Informatique Ubiquitaire.
Remote Procedure Call (RPC)
Denis Caromel1 Joint work with Ludovic Henrio – Eric Madelaine et. OASIS members OASIS Team INRIA -- CNRS - I3S – Univ. of Nice Sophia-Antipolis, IUF.
Fabrice Huet Mobility of Active Objects Fabrice Huet INRIA-I3S-CNRS.
Denis Caromel, Arnaud Contes OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis 1. Introduction to the GRID.
Denis Caromel Denis Caromel 3 Clouds.
Ameoba Designed by: Prof Andrew S. Tanenbaum at Vrija University since 1981.
Denis Caromel 1 Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis, IUF September 4.
1 Ludovic Henrio Paris, An Open Source Middleware for the Grid Programming Wrapping Composing Deploying.
Denis Caromel1 Institut Universitaire de France (IUF) OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis ECCOMAS, July 2004 ProActive: Components.
Session 2: task 3.2 GCM, Kracow, June l Current status of GCM Denis Caromel (10 mn each talk) l Wrapping CCA Components as GCM Components Maciej.
Rheeve: A Plug-n-Play Peer- to-Peer Computing Platform Wang-kee Poon and Jiannong Cao Department of Computing, The Hong Kong Polytechnic University ICDCSW.
490dp Synchronous vs. Asynchronous Invocation Robert Grimm.
Denis Caromel1 Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis, IUF 3 rd ProActive User Group, Nov Model.
CS 603 Threads, Processes, and Agents March 18, 2002.
Fabien Viale 1 Matlab & Scilab Applications to Finance Fabien Viale, Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S.
KARMA with ProActive Parallel Suite 12/01/2009 Air France, Sophia Antipolis Solutions and Services for Accelerating your Applications.
Denis Caromel1 Institut universitaire de France (IUF) OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis REUNA, Santiago, May 2004 GRID.
1 Secure Distributed Objects for Grid Applications Laurent Baduel, Arnaud Contes, Denis Caromel OASIS team ProActive
SALSA: Language and Architecture for Widely Distributed Actor Systems. Carlos Varela, Abe Stephens, Department of.
Oct Multi-threaded Active Objects Ludovic Henrio, Fabrice Huet, Zsolt Istvàn June 2013 –
The Grid Component Model: an Overview “Proposal for a Grid Component Model” DPM02 “Basic Features of the Grid Component Model (assessed)” -- DPM04 CoreGrid.
The Grid Component Model and its Implementation in ProActive CoreGrid Network of Excellence, Institute on Programming Models D.PM02 “Proposal for a Grid.
Architectures of distributed systems Fundamental Models
1 Update Strategies for First Class Futures Khan Muhammad, Ludovic Henrio INRIA, Univ. Nice Sophia Antipolis,CNRS.
Formalism and Platform for Autonomous Distributed Components Bio-inspired Networks and Services A Distributed Component Model Formalisation in Isabelle.
Denis Caromel1 Troisieme partie Cours EJC 2003, AUSSOIS, Denis Caromel OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis.
Denis Caromel 1 Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis, IUF Open Source.
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
OASIS OASIS Active Objects, Semantics, Internet, and Security Team: 30 persons Research Themes: Grid Computing Objects and Components Practice and Theory.
Spring/2002 Distributed Software Engineering C:\unocourses\4350\slides\DefiningThreads 1 RMI.
A High Performance Middleware in Java with a Real Application Fabrice Huet*, Denis Caromel*, Henri Bal + * Inria-I3S-CNRS, Sophia-Antipolis, France + Vrije.
1 Romain Quilici ObjectWeb Architecture meeting July 2nd 2003 ProActive Architecture of an Open Middleware for the Grid.
Denis Caromel1 Institut universitaire de France (IUF) INRIA Sophia-Antipolis – CNRS – I3S – Université de Nice Luis Mateu DCC – Universidad de Chile Eric.
Denis Caromel1 Denis Caromel, Romain Quilici OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis Albufeira,
Emil Salageanu ProActive Parallel Suite ActiveEon March 2008 ActiveEon Hands On Programming.
Grid programming with components: an advanced COMPonent platform for an effective invisible grid © GridCOMP Grids Programming with components.
Transparent Mobility of Distributed Objects using.NET Cristóbal Costa, Nour Ali, Carlos Millan, Jose A. Carsí 4th International Conference in Central Europe.
1 BRUSSELS - 14 July 2003 Full Security Support in a heterogeneous mobile GRID testbed for wireless extensions to the.
1. 2 Objects to Distributed Components (1) Typed Group Java or Active Object ComponentIdentity Cpt = newActiveComponent (params); A a = Cpt ….getFcInterface.
A Software Framework for Distributed Services Michael M. McKerns and Michael A.G. Aivazis California Institute of Technology, Pasadena, CA Introduction.
ProActive components and legacy code Matthieu MOREL.
SelfCon Foil no 1 Variability in Self-Adaptive Systems.
A visualisation and debugging tool for multi-active objects Ludovic Henrio, Justine Rochas LAMHA, Nov 2015.
Transparent First-class Futures and Distributed Components Introduction: components, futures, and challenges Statically Representing Futures An Example.
Denis Caromel1 Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis, IUF October
1 OASIS Team, INRIA Sophia-Antipolis/I3S CNRS, Univ. Nice Christian Delbé Data Grid Explorer 15/09/03 Large Scale Emulation Mobility in ProActive.
Distributed Components and Futures: Models and Challenges A Distributed Component Model Distributed Reconfiguration Calculi for Components and Futures.
A Theory of Distributed Objects Toward a Foundation for Component Grid Platforms Ludovic HENRIO l A Theory of Distributed Objects l Components l Perspectives.
Mastère RSD - TC4 2005/20061 Distributed JAVA Aims and Principles The ProActive library Models of behaviours Generation of finite (parameterized) models.
1 Romain Quilici OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis, IUF July 2nd 2003 ProActive Architecture.
2. CALCULUS: A S P. A Theory of Distributed Objects D. Caromel, L. Henrio, Springer 2005, Monograph A Calculus: ASP: Asynchronous Sequential Processes.
Denis Caromel1 Institut universitaire de France (IUF) OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis JAOO, Cannes, May 2004 Programming,
© Oxford University Press 2011 DISTRIBUTED COMPUTING Sunita Mahajan Sunita Mahajan, Principal, Institute of Computer Science, MET League of Colleges, Mumbai.
Denis Caromel1 OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis -- IUF IPDPS 2003 Nice Sophia Antipolis, April Overview: 1. What.
ASYNCHRONOUS AND DETERMINISTIC OBJECTS ASP: Asynchronous Sequential Processes l Distributed objects l Asynchronous method calls l Futures and Wait-by-necessity.
Asynchronous Distributed Components: Concurrency and Determinacy I. Context: Distributed Components and Active Objects II. Asynchronous Distributed Components.
CHAPTER 3 Architectures for Distributed Systems
Architectures of distributed systems Fundamental Models
Architectures of distributed systems Fundamental Models
ProActive Architecture of an Open Middleware for the Grid
Architectures of distributed systems Fundamental Models
Parallel programming in Java
The Grid Component Model and its Implementation in ProActive
Presentation transcript:

Denis Caromel 1 Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis, IUF Strong Programming Model for Strong Weak Mobility: 1.Introduction to ProActive 2.PM: Active Objects + Groups 3.Mobile Agents 4.Strategies for Localization 5.GUI (Video) 6.Applications: Load Balancing

Denis Caromel 2 ProActive Parallel Suite (1) Open Source + PROFESSIONAL SUPPORT

Denis Caromel 3 ProActive Parallel Suite: GUI

Denis Caromel 4 ProActive Parallel Suite: GUI

Denis Caromel 5

6 ProActive Parallel Suite: Deploy

Denis Caromel 7 ProActive Parallel Suite: Deploy

Denis Caromel 8 Deploy on Various Kinds of Infrastructures Internet Clusters Parallel Machine Large Equipment Internet Job management for embarrassingly parallel application (e.g. SETI) Internet Servlets EJBsDatabases

Denis Caromel 9 Abstract Deployment Model Problem: Difficulties and lack of flexibility in deployment Avoid scripting for: configuration, getting nodes, connecting, etc. A key principle: Virtual Node (VN) + XML deployment file Abstract Away from source code, and Wrapping code: Machines Creation Protocols Lookup and Registry Protocols Protocols and infrastructures: Globus, ssh, rsh, LSF, PBS, SGE, IBM Load Lever, … Web Services,... Data management: File transfer

Denis Caromel 10 Scheduler and Resource Manager: User Interface

Denis Caromel 11 Scheduler: User Interface

Denis Caromel 12 ProActive Parallel Suite: Program

Denis Caromel 13 ProActive Parallel Suite: Program

Denis Caromel 14 ProActive Parallel Suite: Program

Denis Caromel Distributed and Parallel Objects ProActive Programming

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

Denis Caromel 17 ProActive: Inter- to Intra- Synchronization SequentialMultithreadedDistributed Synchronizations, Behavior: not dependent upon the physical location (mapping of activities)

Denis Caromel 18 ProActive : Explicit Synchronizations Explicit Synchronization: - ProActive. isAwaited (v); // Test if available -. waitFor (v); // Wait until availab. Vectors of Futures: -. waitForAll (Vector); // Wait All -. waitForAny (Vector); // Get First A ag = newActive (“A”, […], VirtualNode) V v = ag.foo(param);... v.bar(); //Wait-by-necessity

Denis Caromel 19 ProActive : Intra-object synchronization Explicit control: Library of service routines: Non-blocking services,... serveOldest (); serveOldest (f); Blocking services, timed, etc. serveOldestBl (); serveOldestTm (ms); Waiting primitives waitARequest(); etc. class BoundedBuffer extends FixedBuffer implements RunActive { // Programming Non FIFO behavior runActivity (ExplicitBody myBody) { while (...) { if (this.isFull()) serveOldest("get"); else if (this.isEmpty()) serveOldest ("put"); else serveOldest (); // Non-active wait waitArequest (); } }} Implicit (declarative) control: library classes e.g. : Blocking Condition Abstraction for concurrency control: doNotServe ("put", "isFull");

Denis Caromel 20 ProActive: First-Class Futures SequentialMultithreadedDistributed Synchronizations, Behavior: not dependent upon the physical location (mapping of activities)

Denis Caromel 21 Wait-By-Necessity: First Class Futures ba Futures are Global Single-Assignment Variables V= b.bar () c c c.gee (V) v v b

Denis Caromel 22 Standard system at Runtime: No Sharing NoC: Network On Chip Proofs of Determinism

Denis Caromel 23 Calculus ASP: Asynchronous Sequential Processes

Denis Caromel 24 Proofs in GREEK ASP  Confluence and Determinacy Future updates can occur at any time, Mobility does not change behavior

Denis Caromel 25 TYPED ASYNCHRONOUS GROUPS

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

Denis Caromel 27 Broadcast and Scatter JVM ag cg ag.bar(cg); // broadcast cg ProActive.setScatterGroup(cg) ; ag.bar(cg); // scatter cg c1 c2 c3 c1 c2 c3 c1 c2 c3 c1 c2 c3 c1 c2 c3 c1 c2 c3 s c1 c2 c3 s Broadcast is the default behavior Use a group as parameter, Scattered depends on rankings

Denis Caromel 28 Dynamic Dispatch Group JVM ag cg c1 c2 c3 c4 c5 c6 c7 c8c0 c9c1 c2 c3 c4 c5 c6 c7 c8c0 c9 c1 c2 c3 c4 c5 c6 c7 c8c0 c9 Slowest Fastest ag.bar(cg);

Denis Caromel 29 ProActive Parallel Suite

Denis Caromel 30 ProActive Parallel Suite

Denis Caromel Mobile Agents

Denis Caromel 32 ProActive : Migration of active objects Migration is initiated by the active object itself through a primitive: migrateTo Can be initiated from outside through any public method The active object migrates with: all pending requests all its passive objects all its future objects Automatic and transparent forwarding of: requests (remote references remain valid) replies (its previous queries will be fullfilled)

Denis Caromel 33 Principles and optimizations Same semantics guaranteed (RDV, FIFO order point to point, asynchronous) Safe migration (no agent in the air!) Local references if possible when arriving within a VM Tensionning (removal of forwarder)

Denis Caromel 34 Principles and optimizations Same semantics guaranteed (RDV, FIFO order point to point, asynchronous) Safe migration (no agent in the air!) Local references if possible when arriving within a VM Tensionning (removal of forwarder)

Denis Caromel 35 Principles and optimizations Same semantics guaranteed (RDV, FIFO order point to point, asynchronous) Safe migration (no agent in the air!) Local references if possible when arriving within a VM Tensionning (removal of forwarder) direct

Denis Caromel 36 Principles and optimizations Same semantics guaranteed (RDV, FIFO order point to point, asynchronous) Safe migration (no agent in the air!) Local references if possible when arriving within a VM Tensionning (removal of forwarder) direct

Denis Caromel 37 Principles and optimizations Same semantics guaranteed (RDV, FIFO order point to point, asynchronous) Safe migration (no agent in the air!) Local references if possible when arriving within a VM Tensionning (removal of forwarder) direct forwarder

Denis Caromel 38 Principles and optimizations Same semantics guaranteed (RDV, FIFO order point to point, asynchronous) Safe migration (no agent in the air!) Local references if possible when arriving within a VM Tensionning (removal of forwarder) direct forwarder

Denis Caromel 39 Principles and optimizations Same semantics guaranteed (RDV, FIFO order point to point, asynchronous) Safe migration (no agent in the air!) Local references if possible when arriving within a VM Tensionning (removal of forwarder) direct forwarder

Denis Caromel 40 Principles and optimizations Same semantics guaranteed (RDV, FIFO order point to point, asynchronous) Safe migration (no agent in the air!) Local references if possible when arriving within a VM Tensionning (removal of forwarder) direct forwarder

Denis Caromel 41 ProActive : API for Mobile Agents Mobile agents (active objects) that communicate Basic primitive: migrateTo public static void migrateTo (String u) // string to specify the node (VM) public static void migrateTo (Object o) // joinning another active object public static void migrateTo (Node n) // ProActive node (VM)

Denis Caromel 42 ProActive : API for Mobile Agents Mobile agents (active objects) that communicate // A simple agent class SimpleAgent implements runActive, Serializable { public SimpleAgent () {} public void moveTo (String t){ // Move upon request ProActive.migrateTo (t); } public String whereAreYou (){ // Repplies to queries return ( “ I am at ” + InetAddress.getLocalHost ()); } public runActivity (Body myBody){ while ( … not end of itinerary … ){ res = myFriend.whatDidYouFind () // Query other agents … } myBody.fifoPolicy(); // Serves request, potentially moveTo }

Denis Caromel 43 ProActive : API for Mobile Agents Mobile agents that communicate Primitive to automatically execute action upon migration public static void onArrival (String r) // Automatically executes the routine r upon arrival // in a new VM after migration public static void onDeparture (String r) // Automatically executes the routine r upon migration // to a new VM, guaranted safe arrival public static void beforeDeparture (String r) // Automatically executes the routine r before trying a migration // to a new VM

Denis Caromel 44 ProActive : API for Mobile Agents Itinerary abstraction Itinerary : VMs to visit specification of an itinerary as a list of (site, method) automatic migration from one to another dynamic itinerary management (start, pause, resume, stop, modification, …) API: myItinerary.add (“machine1’’, “routineX”);... itinerarySetCurrent, itineraryTravel, itineraryStop, itineraryResume, … Still communicating, serving requests: itineraryMigrationFirst (); // Do all migration first, then services, Default behavior itineraryRequestFirst (); // Serving the pending requests upon arrival before migrating again

Denis Caromel 45 Host 1Host 2 Host 3 A Home Migration Dynamic itineraries Migration Host 4 foo Host 4 Migration AAAA

Denis Caromel Localization

Denis Caromel 47 Forwarders Migrating object leaves forwarder on current site Forwarder is linked to object on remote site Possibly the mobile object Possibly another forwarder => a forwarding chain is built When receiving message, forwarder sends it to next hop Upon successful communication, a tensioning takes place

Denis Caromel 48 Other Strategy: Centralized (location Server) S Host A A Host BHost CHost D S : Source A : Agent reference Server

Denis Caromel 49 Centralized Strategy (2) S Host A Host B A Host CHost D S : Source A : Agent reference Migration Server Server Update A migrating object updates the server

Denis Caromel 50 Centralized Strategy (3) S Host A Host BHost CHost D S : Source A : Agent reference Message Migration A Server Update Failed A migrating object updates the server

Denis Caromel 51 Centralized Strategy (4) S Host A Host BHost CHost D S : Source A : Agent référence A Server Ask for a new reference Response Message But the AO might have moved again in the meantime … just play again. ! The source get a new reference from the server Request

Denis Caromel 52 Location Server vs Forwarder Server No fault tolerance if single server Scaling is not straightforward Added work for the mobile object The agent can run away from messages Forwarders Use resources even if not needed The forwarding chain is not fault tolerant An agent can be lost What about performance?

Denis Caromel 53 Forwarder vs. Server LAN ( 100 Mb/s ) Response time (ms) vs. Communication rate Server better on a LAN

Denis Caromel 54 Forwarder vs Server MAN ( 7 Mb/s ) Response time (ms) vs. Communication rate Forwarders sometimes better on a MAN

Denis Caromel 55 Formal Performance Evaluation of Mobile Agents: Markov Chains Together with Fabrice Huet and Mistral Team Objectives: Formally study the performance of Mobile Agent localization mechanism Investigate various strategies (forwarder, server, etc.) Define adaptative strategies Modeling: Frequency of: –Message from source –Agent migration Time for: –Message transmission –Agent migration

Denis Caromel 56 Modeling of Forwarder Strategy No message One In-transit message

Denis Caromel 57 Modeling of Server Strategy

Denis Caromel 58 TTL-TTU mixed parameterized protocol TTL:Time To Live + Updating Forwarder: After TTL, a forwarder is subject to self destruction Before terminating, it updates server(s) with last agent known location TTU:Time To Update mobile AO: After TTU, AO will inform a localization server(s) of its current location Dual TTU: first of two events: maxMigrationNb: the number of migrations without server update maxTimeOnSite: the time already spent on the current site 5 s s.

Denis Caromel 59 TTL-TTU mixed parameterized protocol S Host A A Host BHost CHost D S : Source A : Agent reference Server

Denis Caromel 60 TTL-TTU mixed parameterized protocol S Host A Host B A Host CHost D S : Source A : Agent reference Migration Server Server Update F TTL TTU

Denis Caromel IC2D Interactive Control & Debug for Distribution Eclipse GUI for the GRID

Denis Caromel 62 GUI in ProActive Parallel Suite

Denis Caromel 63 GUI in ProActive Parallel Suite

Denis Caromel 64 Programmer Interface for Monitoring Debugging Optimizing

Denis Caromel 65

Denis Caromel 66 IC2D

Denis Caromel 67 Video 1: IC2D Monitoring, Debugging, Optimizing

Denis Caromel 68 Ongoing Work: 3D View in IC2D

Denis Caromel Example of ProActive Applications

Denis Caromel 70 Load Balancing

Denis Caromel 71 Load Balancing using Mobility (1)

Denis Caromel 72 Load Balancing using Mobility (2) Deals with heterogeneous machines, applications, and network.

Denis Caromel 73 Sylvain Cussat-Blanc, Yves Duthen – IRIT TOULOUSE Artificial Life Generation ApplicationJ+1J+5J+6J+7 Version ProActive CPUs Initial Application 1 PC56h52 => Crash! ProActive Version 300 CPUs19 minutes Developpement of artificial creatures

Denis Caromel 74 Sylvain Cussat-Blanc, Yves Duthen – IRIT TOULOUSE Artificial Life Generation

Denis Caromel 75 JECS : 3D Electromagnetism Radar Reflection on Planes

Denis Caromel 76 Code Coupling : Vibro Acoustic (courtesy of EADS)

Denis Caromel 77 P2P: AO Overlay Network

Denis Caromel 78

Denis Caromel 79

Denis Caromel 80 Summary

Denis Caromel 81 Multi-Core to Distributed Concurrency + Mobility + Parallelism Multi-Cores + Distribution

Denis Caromel 82 Conclusion: Why does it move ? Thanks to a few key features: Connection-less, RMI+JMS unified Messages rather than long-living interactions

Denis Caromel 83 Conclusion: Why does it Communicate and Behave ? Thanks to a few key features: Because it Scales: asynchrony ! Because it is Typed: RMI with interfaces ! First-Class Futures: No unstructured Call Backs and Ports

Denis Caromel 84 Conclusion on Mobile Active Objects Active Objects = a good unit of Computational Mobility Weak Migration OK (even for Load Balancing) Both Actors and Servers Ensuring communications: several strategies to choose from: Location Server Forwarders Mixed: based on TTL-TTU Primitive + Higher-Level abstractions: migrateTo (location) onArrival, onDeparture Itinerary, etc.  Application to Mobile Telecoms: DLP, NH Avatar (NHA), Shared Space for Session Management

Denis Caromel 85 Summary-Perspective: Mobility at the Core

Denis Caromel 86 ProActive/ GCM Specifications for Components Services SLA QoS Open the way to Soft.+Serv. EU Industry with Clouds & Utilities, DAAS ProActive/ GCM Specifications for Components Services SLA QoS Open the way to Soft.+Serv. EU Industry with Clouds & Utilities, DAAS

Denis Caromel 87

Denis Caromel 88 Parallel, Distributed, Hierarchical 3. Components Composing

Denis Caromel 89 Objects to Distributed Components (1) Typed Group Java or Active Object ComponentIdentity Cpt = newActiveComponent (params); A a = Cpt ….getFcInterface ("interfaceName"); V v = a.foo(param); V A Example of component instance JVM Truly Distributed Components IoC: Inversion Of Control (set in XML)

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

Denis Caromel 91 GridCOMP Partners

GCM Scopes and Objectives: Grid Codes that Compose and Deploy No programming, No Scripting, … No Pain Innovation: Abstract Deployment Composite Components Multicast and GatherCast MultiCast GatherCast

Denis Caromel 93 Pies for Analysis and Optimization

Denis Caromel 94 Pies for Analysis and Optimization

Denis Caromel 95 With Summary Report

Denis Caromel 96 Ongoing Work: Integration with JMX JConsole: Monitoring Heap, Threads, CPU Over 60 Hours