-
Notifications
You must be signed in to change notification settings - Fork 18
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
redfishpower: add -x,--exclude-plugs option #175
Comments
My initial thought was "does it actually make the config easier?" It seems like a sideways move to me overall. |
What could go wrong :-) . Why is my misconfigured powerman daemon sending http requests to "unknown15"? |
per some offline thoughts / discussion implementation can get a little tricky, b/c of parenting. for example, if user does Hypothetically making it so exclude only works with "leaf" plugs makes things easier, but there's no way to know what a leaf is until all configuration is complete (which is in login script, well after command line parsing is done). |
A completely random, possibly bad idea. What if we made a certain keyword a special case for "unused". Like
and redfishpower would know "never send a message to UNPOPULATED"? |
Eh, that still feels pretty hacky for me. |
Problem: it's kind of janky to have to make up hostname placeholders like
unused[0-7]
for unused blade slots in the cray-ex chassis.I can't remember if we discussed this before and decided against it, but would it make sense to have a
redfishpower -x,--exclude-plugs
option so those placeholders would not be needed? For example ifBlade[4-7]
are unpopulated thusNode[8-15]
do not require host mappings, instead of:you could do:
The text was updated successfully, but these errors were encountered: