[kepler-dev] [Bug 4161] New: - Develop kepler workflow execution engine

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4161

           Summary: Develop kepler workflow execution engine
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: tao at nceas.ucsb.edu
        ReportedBy: tao at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


Here is the an email from matt:

I think the next stage would be to have you work on
putting together an execution engine that can, given a schedule of a
workflow to be run, can be called to retrieve the workflow KAR from
metacat, set up a proper staging directory for execution, and run
kepler, making sure that output and errors are handled properly.  On
the output side, this means programatically calling the run manager
that Derik and Aaron are making to create a kar file that contains the
results, and then publish that to metacat (Kepler also should have an
API for this when Derik and Aaron are done).


We decided to use web service as the execution engine. The API will be:

1. execute(workflowID)::runID
2. getStatus(runID)::status

status includes:
SCHEDULED
EXECUTING
SUCCEEDED
FAILED
NOTFOUND