Bug #14710

[Workbench] Child containers run on federated clusters do not show up

Added by Peter Amstutz 6 months ago. Updated 5 months ago.

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

0%

Estimated time:
Story points:
3.0

Description

Child containers are determined by querying for container requests where requested_by_container_uuid matches the parent container. This does not work for federated workflows, because (a) containers run on remote clusters don't set requested_by_container_uuid and (b) even if it was set, we don't have an easy way to query remotes (requires either #14374 or generalizing javascript multi-site search feature).

Solution:

  1. When controller creates a remote container request, it can supply requested_by_container_uuid
  2. Controller records the uuid of the remote container request, and saves a cache copy of container request record in the local database with the appropriate requested_by_container_uuid
  3. The client can filter on requested_by_container_uuid in the local database and get both local and remote container requests.
  4. When a client makes a list or get request that returns remote objects, fetch the latest records from the remote cluster and merge the updated records into the response. (And update the cached copy?)

What should the owner_uuid by on the cache copy?


Related issues

Related to Arvados - Story #14374: Multi-site (federated) object search in controllerNew

Related to Arvados Workbench 2 - Feature #15278: [Workbench 2] Search for & execute workflows defined on federated clustersNew

Related to Arvados - Feature #15457: [Controller] Delegate new container requests to other clusters based on location of input dataNew

History

#1 Updated by Peter Amstutz 6 months ago

  • Status changed from New to In Progress

#2 Updated by Peter Amstutz 6 months ago

  • Description updated (diff)

#3 Updated by Tom Morris 6 months ago

  • Status changed from In Progress to New

#4 Updated by Tom Morris 5 months ago

  • Related to Story #14374: Multi-site (federated) object search in controller added

#5 Updated by Peter Amstutz 5 months ago

  • Description updated (diff)

#6 Updated by Peter Amstutz 5 months ago

  • Description updated (diff)

#7 Updated by Peter Amstutz 5 months ago

  • Description updated (diff)
  • Story points set to 3.0

#8 Updated by Tom Morris 5 months ago

  • Target version changed from To Be Groomed to Arvados Future Sprints

#9 Updated by Peter Amstutz 12 days ago

  • Related to Story #15455: Outputs of workflow runs get put into a default location other than the user's home project added

#10 Updated by Peter Amstutz 12 days ago

  • Related to Feature #15278: [Workbench 2] Search for & execute workflows defined on federated clusters added

#11 Updated by Peter Amstutz 12 days ago

  • Related to deleted (Story #15455: Outputs of workflow runs get put into a default location other than the user's home project)

#12 Updated by Tom Clegg 12 days ago

  • Related to Feature #15457: [Controller] Delegate new container requests to other clusters based on location of input data added

Also available in: Atom PDF