GCM: a grid extension to Fractal for autonomous distributed components

Abstract

This article presents an extension of the Fractal component model targeted at programming applications to be run on computing grids: the Grid Component Model (GCM). First, to address the problem of deployment of components on the Grid, deployment strategies have been de ned. Then, as Grid applications often result from the composition of a lot of parallel (sometimes identical) components, composition mechanisms to support collective communications on a set of components are introduced. Finally, because of the constantly evolving environment and requirements for Grid applications, the GCM de nes a set of features intended to support component autonomicity. All these aspects are developed in this paper with the challenging objective to ease the programming of Grid applications, while allowing GCM components to also be the unit of deployment and management

SuperQuant Financial Benchmark Suite for Performance Analysis of Grid Middlewares

“…As we can see in Figure 1, the KAAPI/TAKTUK team was successful in computing the maximum number of TestCases and was also able to deploy application on a significantly large number of nodes. [3]. The infrastructure descriptors and application descriptors required by GCM were bundled with the benchmark suite.…”

Exogenous coordination of concurrent software components with JavaBIP

“…Otherwise, the internal transition is disabled. Instead, to move to state done, the route has to wait for the processing termination event, associated with the spontaneous transition end ( @Transition(name = "end", source = "wait", target = "done", guard = "!g") 30 public void spontaneousEnd() {} // "!g" in the guard above means "not g" 31 32 @Transition(name = "", source = "wait", target = "done", guard = "g") 33 public void internalEnd() {} 34 35 @Transition(name = "finished", source = "done", target = "off") 36 public void finishedTransition() {} 37 38 @Guard(name = "g") 39 public lines [27][28][29][30] that checks whether the available memory limit of the system, defined through the constructor of the MemoryMonitor class ( Figure 4: lines [12][13][14], is sufficient for adding more running routes.…”

“…For example, in Figure 4, transition add (lines [16][17][18][19][20] depends on the guard hasCapacity, which requires the datum memoryUsage (lines [27][28][29][30]. This datum is received from another component potentially participating in an interaction.…”

A Framework for Reasoning on Component Composition

“…Our intent is to build a mechanised model of the GCM component model [4], but giving it a runtime semantics so that we can reason on the execution of component application and their evolution. Thus we start by describing the concepts of the GCM which are useful for understanding this paper.…”