GridCOMP provides the reference implementation of the Grid Component Model (GCM). The developed prototype takes the ProActive Parallel Suite as the starting point to provide the functional features of GCM components such as : - a deployment framework, standardized by ETSI and providing interoperability with several grid schedulers and middleware, - primitive and composite components supporting collective communications. The GCM implementation targets all software architects in need of a comprehensive framework to express at design time the parallelisms and the distribution of an application. Therefore, the architecture of the system itself captures the parallel/distributed aspects, acting as a powerful specification and documentation. The GCM provides functional concerns, but also non-functional concerns by means of (hierarchical-) autonomic managers within behavioural skeletons. With Behavioural skeletons, programmers just provide contracts to be satisfied and instantiate existing GCM composites to get completely functional applications with non functional concern auto-tuning, and, thus, avoid high programming efforts to programmers. Behaviorual skeletons have been already demonstrated to be able to take care of performance non functional concerns. Preliminary results have been shown that demonstrated how they can be used to handle other non functional concerns, including fault tolerance and security issues.
GCM: Grid Component Model - reference implementation with autonomic features (NFCF prototype and early documentation)
ALDINUCCI, MARCO;
2008-01-01
Abstract
GridCOMP provides the reference implementation of the Grid Component Model (GCM). The developed prototype takes the ProActive Parallel Suite as the starting point to provide the functional features of GCM components such as : - a deployment framework, standardized by ETSI and providing interoperability with several grid schedulers and middleware, - primitive and composite components supporting collective communications. The GCM implementation targets all software architects in need of a comprehensive framework to express at design time the parallelisms and the distribution of an application. Therefore, the architecture of the system itself captures the parallel/distributed aspects, acting as a powerful specification and documentation. The GCM provides functional concerns, but also non-functional concerns by means of (hierarchical-) autonomic managers within behavioural skeletons. With Behavioural skeletons, programmers just provide contracts to be satisfied and instantiate existing GCM composites to get completely functional applications with non functional concern auto-tuning, and, thus, avoid high programming efforts to programmers. Behaviorual skeletons have been already demonstrated to be able to take care of performance non functional concerns. Preliminary results have been shown that demonstrated how they can be used to handle other non functional concerns, including fault tolerance and security issues.I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.