Actions
Idea #15502
open
endpoint to show why container requests didn't reuse
Start date:
Due date:
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
Updated by Peter Amstutz over 5 years ago
- Related to Bug #13102: containers are not reused unless runtime constraints (including RAM) match exactly added
Updated by Peter Amstutz over 5 years ago
- Related to Bug #15499: job reuse didn't work? added
Updated by Peter Amstutz over 5 years ago
- Subject changed from API call or script to show why jobs didn't reuse to [API] API call or script to show why jobs didn't reuse
Updated by Peter Amstutz over 4 years ago
- Related to Idea #16011: CWL support, docs, training, website added
Updated by Peter Amstutz over 4 years ago
- Target version deleted (
To Be Groomed)
Updated by Peter Amstutz over 3 years ago
- Related to Idea #16517: Workflow resource usage, runtime, and cost visibility and forecasting added
Updated by Peter Amstutz over 3 years ago
- Related to deleted (Idea #16011: CWL support, docs, training, website)
Updated by Peter Amstutz over 3 years ago
- Target version set to 2021-09-01 sprint
Updated by Peter Amstutz over 3 years ago
- Description updated (diff)
- Subject changed from [API] API call or script to show why jobs didn't reuse to endpoint to show why container requests didn't reuse
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-09-01 sprint to 2021-09-15 sprint
Updated by Peter Amstutz about 3 years ago
- Target version deleted (
2021-09-15 sprint)
Actions