Project

General

Profile

Actions

Task #3239

closed

Feature #2881: [OPS] Basic node manager that can start/stop compute nodes based on demand

fix update_node_attributes script and/or merge its remaining functionality into crunch-dispatch

Added by Ward Vandewege almost 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
09/22/2014
Due date:
% Done:

100%

Estimated time:
(Total: 2.00 h)

Description

this script updates the node objects with information about what is running on them, which us information used by node manager


Subtasks 1 (0 open1 closed)

Task #3944: Review 2881-node-has-job-wipResolvedTom Clegg09/22/2014

Actions
Actions #1

Updated by Tim Pierce almost 8 years ago

  • Category set to Crunch
Actions #2

Updated by Brett Smith almost 8 years ago

update_node_attributes sets node.info[:running_job_uuid]. We would rather start expressing this as a relationship, each Node has one Job, so that querying Nodes will use the existing permission code to determine access to the Job UUID. Job queries can join with the Node table to return the full set of Nodes running it.

This seems to be the only functionality left that update_node_attributes currently does that crunch-dispatch doesn't.

Actions #3

Updated by Brett Smith almost 8 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF