The 6th IEEE/ACM International Workshop on Grid Computing, 2005. 2005
DOI: 10.1109/grid.2005.1542733
|View full text |Cite
|
Sign up to set email alerts
|

ASKALON: a Grid application development and computing environment

Abstract: Abstract-We present the ASKALON environment whose goal is to simplify the development and execution of workflow applications on the Grid. ASKALON is centered around a set of high-level services for transparent and effective Grid access, including a Scheduler for optimized mapping of workflows onto the Grid, an Enactment Engine for reliable application execution, a Resource Manager covering both computers and application components, and a Performance Prediction service based on training phase and statistical me… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
74
0
2

Year Published

2007
2007
2014
2014

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 147 publications
(83 citation statements)
references
References 15 publications
0
74
0
2
Order By: Relevance
“…Recent work [7,18,11] shows that scheduling through resource reservation and performance modeling can help to ensure the resource availability during executing and theoretically make the grid more predictable, but their approaches do not solve all the problems.…”
Section: Introductionmentioning
confidence: 99%
“…Recent work [7,18,11] shows that scheduling through resource reservation and performance modeling can help to ensure the resource availability during executing and theoretically make the grid more predictable, but their approaches do not solve all the problems.…”
Section: Introductionmentioning
confidence: 99%
“…Such middleware is deployed at a majority of sites, with gLite [5], Globus [6], and UNICORE [7] as three of the more popular representatives, and it also provides the basis for a number of SLA-related developments such as the VIOLA metascheduling service [8] or ASKALON [9]. From the architecture in Figure 12.1, the middleware is the entity that executes the workflow or job once the consumer and provider have agreed on an SLA.…”
Section: Middleware Layermentioning
confidence: 99%
“…JOpera workflows also are based upon the use of a DFG formalism to represent scientific processes. Teuta [13], [14] represents scientific processes through UML diagrams that offer some features, such as limited forms of concurrency, that go beyond the semantic features of a basic DFG. We believe that the Water Budget process described here illustrates aspects of scientific processes that cannot be easily captured using DFGs.…”
Section: Related Workmentioning
confidence: 99%