Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

scontrol CLI rewrite #6

Open
morrone opened this issue Apr 27, 2011 · 2 comments
Open

scontrol CLI rewrite #6

morrone opened this issue Apr 27, 2011 · 2 comments

Comments

@morrone
Copy link
Member

morrone commented Apr 27, 2011

It seems like the scontrol command line interface could be greatly improved. I think that the whole key=value model could be replaced with a more hierarchical command set like you see out of command like svn, git, etc.

For instance, instead of:

$ scontrol update nodename=foo[1-100] state=drain reason="They're broke"

it could be:

$ scontrol node drain -m "They're broke" foo[1-100]

Notice that the "-m" is an option. Just like with svn and git, if you leave that out it should prompt you for a reason (if reasons are required):

$ scontrol node drain foo[1-100]
reason> They're broke

I suspect that if we took an orderly approach to examining scontrol's current command set, we could design a user interface that is much nicer to use.

@jette
Copy link
Contributor

jette commented Apr 28, 2011

Since the scontrol output format is key=value, i find the current input format idea for using copy/paste to update records. Asking the user to input a specific missing field (the reason a node is being drained) is a good idea

@jette jette closed this as completed Apr 28, 2011
@jette jette reopened this Apr 28, 2011
@morrone
Copy link
Member Author

morrone commented Apr 28, 2011

To set individual flags/attributes:

$ scontrol node set <key>=<value> <nodelist>

lipari pushed a commit that referenced this issue Sep 13, 2011
Bug in selec/cons_res using tasks-per-node and cpus-per-task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants