Story #15455

Outputs of workflow runs get put into a default location other than the user's home project

Added by Tom Morris 5 months ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Story points:
2.0

Description

Currently all outputs go in the user's home project which is undesirable due to the amount of clutter created.

Change this to create a new sub project under <user> / Workflow runs / <Workflow name + date of run> where all outputs are placed by default (unless the user specifies something different). This will be implemented by the client.

arvados-cwl-runner

Default behavior

  1. search for or create a project named "Workflow runs" owned by the user
  2. Create a project under it called <Workflow name + date of run>
  3. Use that as project_uuid

Custom parent

  1. arvados-cwl-runner --parent "My project xyz"
  2. Search for any project visible to the user that has that name (alternately, can also accept a uuid)
    1. If there is a name conflict, report that and instruct the user to use a uuid / fix the project name so it isn't ambigious
  3. Create a project under it called <Workflow name + date of run>
  4. Use that as project_uuid

If --project-uuid is provided, the behavior is unchanged from current.

If --name was provided, it is used for both the subproject name (instead of name+template) as well as the container request.


Subtasks

Task #15604: Investigate implications changing ownership/permission model for containers & outputsNew


Related issues

Related to Arvados Workbench 2 - Feature #15448: [Running a workflow] Specify destination project for intermediate/output collectionsNew

History

#1 Updated by Tom Morris 5 months ago

  • Project changed from Arvados Workbench 2 to Arvados
  • Target version set to To Be Groomed

#2 Updated by Peter Amstutz 5 months ago

  • Related to Bug #14710: [Workbench] Child containers run on federated clusters do not show up added

#3 Updated by Peter Amstutz 5 months ago

  • Description updated (diff)

#4 Updated by Peter Amstutz 5 months ago

  • Related to deleted (Bug #14710: [Workbench] Child containers run on federated clusters do not show up)

#5 Updated by Peter Amstutz 5 months ago

  • Related to Feature #15448: [Running a workflow] Specify destination project for intermediate/output collections added

#6 Updated by Peter Amstutz 5 months ago

  • Description updated (diff)

#7 Updated by Peter Amstutz 5 months ago

  • Description updated (diff)

#8 Updated by Peter Amstutz 5 months ago

  • Description updated (diff)

#9 Updated by Peter Amstutz 3 months ago

  • Description updated (diff)

#10 Updated by Peter Amstutz 2 months ago

  • Description updated (diff)

#11 Updated by Peter Amstutz 2 months ago

  • Description updated (diff)

#12 Updated by Peter Amstutz 2 months ago

  • Description updated (diff)

#13 Updated by Peter Amstutz 2 months ago

  • Description updated (diff)

#14 Updated by Tom Morris 2 months ago

  • Target version changed from To Be Groomed to Arvados Future Sprints
  • Story points set to 2.0

Also available in: Atom PDF