Project

General

Profile

Actions

Story #15502

open

endpoint to show why container requests didn't reuse

Added by Bryan Cosca over 5 years ago. Updated almost 2 years ago.

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

0%

Estimated time:
Story points:
-
Release:
Release relationship:
Auto

Description

Add a new API endpoint that, given two container requests:

  • Check that they are both readable by the user
  • Choose the container from the request that was submitted earlier
  • Choose the container request that was submitted later
  • Using the same logic (and ideally, the same code) try to match the later container request against the earlier container
  • Return a JSON object as a report listing which fields or other criteria prevented reuse.

Related issues 3 (2 open1 closed)

Related to Arvados - Bug #13102: containers are not reused unless runtime constraints (including RAM) match exactlyNew

Actions
Related to Arvados - Bug #15499: job reuse didn't work?ResolvedPeter Amstutz

Actions
Related to Arvados Epics - Story #16517: Workflow runtime/cost visibility and forecastingIn Progress10/01/202307/30/2024

Actions
Actions

Also available in: Atom PDF