Project

General

Profile

Actions

Bug #4427

closed

[Workbench] Each active job/pipeline on the dashboard should show how many worker nodes are allocated to it.

Added by Ward Vandewege over 9 years ago. Updated 8 days ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
-
Story points:
1.0

Description

"Local jobs" will be easy to spot: they will have no worker nodes are allocated.

This answers the question "are these jobs actually consuming compute node resources?"

Distinguishing local jobs from batch jobs later, after they have completed, is a separate story.

Actions #1

Updated by Tom Clegg over 9 years ago

  • Subject changed from [Workbench] Jobs and pipelines that are running in local mode show show up on the dashboard page under 'currently running jobs/pipelines' to [Workbench] Jobs and pipelines that are running in local mode should be marked as such on the dashboard page under 'currently running jobs/pipelines' (and elsewhere in Workbench)
Actions #2

Updated by Tom Clegg over 9 years ago

  • Description updated (diff)
  • Category set to Workbench
Actions #3

Updated by Tom Clegg over 9 years ago

  • Subject changed from [Workbench] Jobs and pipelines that are running in local mode should be marked as such on the dashboard page under 'currently running jobs/pipelines' (and elsewhere in Workbench) to [Workbench] Each active job/pipeline on the dashboard should show how many worker nodes are allocated to it.
  • Description updated (diff)
Actions #4

Updated by Ward Vandewege almost 3 years ago

  • Target version deleted (Arvados Future Sprints)
Actions #5

Updated by Peter Amstutz about 1 year ago

  • Release set to 60
Actions #6

Updated by Peter Amstutz about 2 months ago

  • Target version set to Future
Actions #7

Updated by Peter Amstutz about 2 months ago

  • Status changed from New to Closed
Actions #8

Updated by Peter Amstutz 8 days ago

  • Release deleted (60)
  • Target version deleted (Future)
Actions

Also available in: Atom PDF