Summary: | Would like a way to rename Slurm accounts | ||
---|---|---|---|
Product: | Slurm | Reporter: | Ryan Novosielski <novosirj> |
Component: | Accounting | Assignee: | Unassigned Developer <dev-unassigned> |
Status: | OPEN --- | QA Contact: | |
Severity: | 5 - Enhancement | ||
Priority: | --- | CC: | nate, novosirj, serguei.mokhov, tmerritt |
Version: | 17.11.7 | ||
Hardware: | Linux | ||
OS: | Linux | ||
See Also: | https://bugs.schedmd.com/show_bug.cgi?id=9703 | ||
Site: | Rutgers | 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: | CentOS | Machine Name: | amarel |
CLE Version: | Version Fixed: | ||
Target Release: | --- | DevPrio: | --- |
Emory-Cloud Sites: | --- |
Description
Ryan Novosielski
2018-11-26 13:16:14 MST
Was Tim Wickberg who asked us to put this in, to be more accurate. Is this still active? I would like to +1 this. We delegate management of their groups to our PIs and we'll have to disable the ability for them to rename groups without this feature. Thanks, Todd I guess as active as it ever was, which is to say "not very." I agree, it's an ongoing problem, and to me it doesn't seem impossible to fix, but I'm told there are things that complicate it that are not immediately obvious. More votes helps, I think. The "Unassigned Developer" and lack of a target release are our hints that this isn't an active enhancement, and is simply an outstanding feature request. The rename, as Ryan notes, would be somewhat complicated with our current accounting database structure, especially in how to flag the transition. At this point I don't have any plan to address this. Please +1 for this. I guess it's a design flaw that the account name is a primary key, ON UPDATE CASCADE should work at the database level? Then just updating the name should propagate it to the referring tables? Thank you |