Ticket 6203

Summary:	Parsable output
Product:	Slurm	Reporter:	Jurij Pečar <jurij.pecar>
Component:	User Commands	Assignee:	Unassigned Developer <dev-unassigned>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	5 - Enhancement
Priority:	---
Version:	18.08.3
Hardware:	Linux
OS:	Linux
Site:	EMBL	Alineos Sites:	---
Atos/Eviden Sites:	---	Confidential Site:	---
Coreweave sites:	---	Cray Sites:	---
DS9 clusters:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Linux Distro:	---
Machine Name:		CLE Version:
Version Fixed:		Target Release:	---
DevPrio:	---	Emory-Cloud Sites:	---

Description Jurij Pečar 2018-12-10 03:36:25 MST

Related to #1424 and #2265, but slightly different.

In today's world of everything web it would be very helpful to provide output of various slurm commands in key:value form as well.

For example "sacct -j 24803343 -l -p --delimiter=\n" doesn't really do what I want, \n is not expanded to newline. And even if it would be, it still looks like default mysql column formatted output. Take a look at mysql -E, that's more what I would like to see. So above sacct should print something like:

JobID:24803343
JobIDRaw:24803343
JobName:MATLAB-2017a
Partition:htc
... etc.

Comment 1 Jason Booth 2018-12-10 11:15:53 MST

Hi Jurij Pečar,

 Thanks for the suggestion. I have moved your issue over to an enhancement. There has been some discussion going on internally related to this and other areas that could use a different way to view this information e.g. json so this is something we are aware of and are looking at improving.

Comment 2 Jurij Pečar 2018-12-11 02:36:01 MST

Yes, json is the obvious next step. Can I assume some of this work will land in 19.x ?

Comment 3 Jason Booth 2018-12-11 09:20:49 MST

This is still being discussed so we have not assigned the task to a specific release yet.

Comment 4 Tim Wickberg 2018-12-11 16:59:45 MST

I'm marking this closed as a duplicate of a new bug 6220. We've been tracking this as an internal private bug for a while, but I can't merge yours in with that due to privacy concerns.

We do not have a committed date for any of this work, and I cannot provide an estimate at this point in time.

If our support staff has not explain this before, these enhancement requests are a way for us to track outstanding requests only, and do not indicate whether we will develop anything related to that. If this is of specific importance to EMBL, this is something that we can under a custom development contract, but outside of that cannot commit to any timeframe, or even if the requested functionality will ever be provided. If you have any questions on that please let me know.

- Tim

*** This ticket has been marked as a duplicate of ticket 6220 ***