Project

General

Profile

Bug #1891

writedesign for staged implementation of grid-enabled kepler

Added by Matt Jones over 14 years ago. Updated about 12 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
core
Target version:
Start date:
01/20/2005
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
1891

Description

During the January 2004 meeting we discussed grid-enabling kepler. Matt and
Ilkay agreed to write this up as a design document.


Related issues

Blocked by Kepler - Bug #1899: Implementation of grid-enabling keplerResolved01/20/2005

History

#1 Updated by Matt Jones over 14 years ago

It will include a design for:
1) Nimrod/APST style grid jobs
2) Distributed kepler in 3 stages
a) separate client/server sides of kepler to allow remote execution on
multiple server nodes, no user interaction with server side
b) Add interaction where two directors know about each other and can send
messages (GUI output plus user interaction)
c) Add kepler as a remote deployment system, any kepler node is a client
server system that allows others to submit jobs to it with access control

#2 Updated by Matt Jones over 14 years ago

In addition, we need to:
3) add in ability to dynamically load the workflows to be run as archive files
(.kar) that contain the moml, actors, required jars and libs, etc.

This last point can be implemented independently of the others and would have
benefits locally as well. Chad agreed to tackle this part and it will be
described in a separate bug.

#3 Updated by Matt Jones almost 14 years ago

Several ideas have been proposed and fleshed out on the wiki. Need to
consolidate and decide on a course for implementation. See:
http://kepler-project.org/Wiki.jsp?page=PeerToPeerKepler

#4 Updated by Chad Berkley about 12 years ago

consolidating to one bug

#5 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 1891

Also available in: Atom PDF