Story #15455

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

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

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

0%

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

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).

If a container request is submitted without an owner_uuid and without submitted_by_container_uuid, the API server creates a project for the the container request.

The container gets a new field, "runtime_project_uuid". This is set to the owner of the container request that created the container.

If a container request has "submitted_by_container_uuid", get the container and create the request under "runtime_project_uuid".

If the container in "submitted_by_container_uuid" doesn't exist (because it is federated container) then create a new project and create a stub container record with the remote container uuid and "runtime_project_uuid" set.


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 2 months ago

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

#2 Updated by Peter Amstutz 2 months ago

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

#3 Updated by Peter Amstutz 2 months ago

  • Description updated (diff)

#4 Updated by Peter Amstutz 2 months ago

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

#5 Updated by Peter Amstutz 2 months ago

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

#6 Updated by Peter Amstutz 2 months ago

  • Description updated (diff)

#7 Updated by Peter Amstutz 2 months ago

  • Description updated (diff)

#8 Updated by Peter Amstutz 2 months ago

  • Description updated (diff)

#9 Updated by Peter Amstutz 5 days ago

  • Description updated (diff)

Also available in: Atom PDF