BibTeX
@MISC{Kecskemeti_automaticgrid,
author = {Gabor Kecskemeti and Gabor Terstyanszky},
title = {AUTOMATIC GRID SERVICE DEPLOYMENT},
year = {}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
This article provides an overview of the current Grid Service deployment problems and proposes a general multi layer architecture for service deployment solutions based on the previously published specialised and partially defined ones. From the architectural point of view a service could be a legacy code wrapped to a service oriented environment, a Web service or a Grid service. 1. TODAY'S GRID 1.1 Closely-Coupled Grid Nowadays there are several possibilities to access the powers of the high throughput computing by creating virtual organisations with the help of a Grid middleware software ([1]) such as gLite, Globus([3]), Gridbus, Legion or UNICORE. These virtual organisations have a great disadvantage during their expansion phase, because all of the newly joint members has to follow the rules and policies laid down by the founders of the VO. These policies are strict rules about the site,
Keyphrases
automatic grid service deployment virtual organisation expansion phase legacy code high throughput web service closely-coupled grid nowadays great disadvantage strict rule general multi layer architecture service deployment solution several possibility architectural point current grid service deployment problem grid service joint member grid middleware software
