Ticket 4629 - Additional information request for reservation accounting
Summary: Additional information request for reservation accounting
Status: OPEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: Accounting (show other tickets)
Version: 17.02.9
Hardware: Linux Linux
: 5 - Enhancement
Assignee: Unassigned Developer
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2018-01-16 06:30 MST by Nicholas Cardo
Modified: 2018-01-19 07:36 MST (History)
2 users (show)

See Also:
Site: CSCS - Swiss National Supercomputing Centre
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: 18.08
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description Nicholas Cardo 2018-01-16 06:30:07 MST 
The data stored in the <host>_resv_table is insufficient to reconstruct a past reservation.  This is a request to enhance the record with the following additional data:

1. Add timestamp representing when the request was made. (The reservation start time is already there)
2. Add details for reserved licenses
3. Add sufficient fields to determine what unit was reserved and how many.  For example, a unit may be node count or core count and then how many of these were reserved.

Thanks
Comment 1 Nicholas Cardo 2018-01-16 06:46:47 MST 
Apologies, missed one item.  The reservation record should indicate what was requested.  For example, where specific nodes requested or was a node count requested and Slurm chose the nodes.  We are interested in being able to distinguish between these.

Thanks again
Comment 2 Tim Wickberg 2018-01-16 19:29:52 MST 
Hey Nicholas -

I'm tagging this an an enhancement request for 18.08; we can't add those fields to one of the current releases.