Ticket 8349 - consistent naming of env vars
Summary: consistent naming of env vars
Status: OPEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: User Commands (show other tickets)
Version: 19.05.5
Hardware: Linux Linux
: 5 - Enhancement
Assignee: Unassigned Developer
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2020-01-16 17:20 MST by Daniel Grimwood
Modified: 2020-01-17 09:31 MST (History)
0 users

See Also:
Site: Pawsey
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
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 Daniel Grimwood 2020-01-16 17:20:50 MST 
Hi,

it would help users and my memory if SBATCH_EXPORT, SLURM_EXPORT_ENV, and SRUN_EXPORT_ENV were all consistent in naming convention.  I am not fussed if _ENV is there or not, as long as it's consistent.

In the interim it might pay to deprecate and document whichever is not going forwards, so that nobody's config breaks for a few years.

With regards,
Daniel.
Comment 1 Jason Booth 2020-01-17 09:31:41 MST 
Daniel - Thanks for letting us know that this is causing an issue. We will look into this and see what we can do.