writedesign for staged implementation of grid-enabled kepler
During the January 2004 meeting we discussed grid-enabling kepler. Matt and
Ilkay agreed to write this up as a design document.
#1 Updated by Matt Jones about 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 about 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 over 13 years ago
Several ideas have been proposed and fleshed out on the wiki. Need to
consolidate and decide on a course for implementation. See: