Ticket 6174 - Job categories for reporting
Summary: Job categories for reporting
Status: RESOLVED INFOGIVEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: Other (show other tickets)
Version: 17.11.5
Hardware: Linux Linux
: 4 - Minor Issue
Assignee: Nate Rini
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2018-12-05 09:57 MST by Daniel P Davis
Modified: 2018-12-05 14:06 MST (History)
0 users

See Also:
Site: EM
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
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: ---
DevPrio: ---
Emory-Cloud Sites: ---


Attachments

Note You need to log in before you can comment on or make changes to this ticket.
Description Daniel P Davis 2018-12-05 09:57:31 MST
What options or best practices are there around tagging jobs with additional metadata?  We are interested in reporting on types of jobs rather than just user/account/org info (e.g. machine learning vs computational chemistry).  I didn't see anything obvious in the documentation, but I may not have been looking in the right place.

I could see requiring the user to supply a category as part of their job submission and validating it in the LUA job submit plugin.  But I am unclear how to get this info into the accounting database for later reporting.

We are using XDMoD for reporting in case it matters.
Comment 1 Nate Rini 2018-12-05 13:10:03 MST
(In reply to Daniel P Davis from comment #0)
> What options or best practices are there around tagging jobs with additional
> metadata?  We are interested in reporting on types of jobs rather than just
> user/account/org info (e.g. machine learning vs computational chemistry).  I
> didn't see anything obvious in the documentation, but I may not have been
> looking in the right place.

Have you tried specifying a wckey with each job?
Comment 2 Daniel P Davis 2018-12-05 14:06:18 MST
Nope.  But that looks perfect.