Project

General

Profile

Bug #4148

Workflow Run Manager - Upload to Repository feature

Added by Derik Barseghian about 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Category:
general
Target version:
Start date:
06/12/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4148

Description

WRM needs to be able to upload runs to the repository. A user selects rows in the WRM and from a context menu clicks to upload. This creates a kar of the runs and will then 'put' it to metacat, along with (correct me if I have this wrong:) any contained metadata docs that point to this kar with the karLSID attribute, e.g run momls and workflow momls. I've had to fork the UploadToRepositoryAction to create a gui-less version. I'm trying to stay in sync with any changes there, so that I can un-fork later.

Part of this work seemed to necessitate or imply getting a KAR from cache. I was unable to get the kar itself from cache, I'll revisit this, but I'm not sure the kar itself is actually being written to cache, just its items (maybe?). Also, I'm currently creating a WorkflowRunCacheObject, so these may be retrieved from cache individually.

The 'depends on' list of this bug is currently probably incomplete. We also change to using setAccess on the items uploaded instead of building access documents in the upload function.


Related issues

Blocks Kepler - Bug #4020: WRP - create WorkflowRun object to encapsulate provenance/report instancesResolved04/23/2009

Blocks Kepler - Bug #4149: Workflow Run Manager - Export Runs featureResolved06/12/2009

History

#1 Updated by Derik Barseghian about 10 years ago

That should read: "We also need to change to using setAccess".

#2 Updated by Derik Barseghian about 10 years ago

This also needs to be able to work without a gui, hopefully by just requiring a list of keplerlsids of runs to upload.

#3 Updated by ben leinfelder about 10 years ago

crucial for the 2a1 release

#4 Updated by ben leinfelder almost 10 years ago

Looks like derik has this non-gui portion working.
I'm now using his classes (in the provenance module) to do the export and upload when we run "automatically" on the webservice-based execution side of things.
Augmenting the LDAP authentication service so that it need not always prompt for user/pass credentials

#5 Updated by ben leinfelder almost 10 years ago

"-server" is now a commandline option that will set a Configuration attribute. ReportingListener will check this and upload reports when appropriate (ie when running on the server)

#6 Updated by ben leinfelder almost 10 years ago

We are allowing for a "-repository" parameter as well. It will let us specify which of the configured Repositories we want the output results to be uploaded to. The Repository also has the username/pass and authentication url needed in order to do the upload.

#7 Updated by ben leinfelder almost 10 years ago

I want to add more specific error handling around each of the put() calls so that we know exactly what is happening. It's very possible that we will end up trying to "reput" the same workflow when we attempt to upload subsequent runs of that workflow. This is fine but we should handle it gracefully.

#8 Updated by ben leinfelder almost 10 years ago

now checking for existing workflows - will not attempt to upload again if it already exists

#9 Updated by ben leinfelder almost 10 years ago

okay - i'm happy with this feature closing

#10 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 4148

Also available in: Atom PDF