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

powerman: support status_ranged script #152

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

chu11
Copy link
Member

@chu11 chu11 commented Feb 29, 2024

per discussion in #128, I was going to punt on this till later, but my mini-hack prototype ended up working. I began to understand the code better, so figured ... why not.

Problem: in powerman.dev(5) the ranged scripts are typoed
as "range".

Correct the typoes.
Problem: Some text describing the selection of the status_all
vs status scripts is invalid.

Simply remove the offending text.
Problem: in the near future we would like to create a PlugList
from a List of Plugs.  It is currently inconvenient to create
such a list given the current PlugList API.

Add a function pluglist_copy_from_list() function to create a PlugList
from a List of Plugs.
Problem: "ranged" version of scripts (on_ranged, off_ranged, etc.)
were supported a long time ago.  A need was not there for a status_ranged
because it was never needed.  However, in the future there will
be scenarios where it may be needed.

Support a "status_ranged" script.
Problem: ipmipower supports passing ranged hosts to
check power status, but it is not utilized.

Use the status_range script over the status_all script in
ipmipower.dev.
Problem: The new status_ranged script is not documented.

Add documentation in powerman.dev(5)
@garlick
Copy link
Member

garlick commented Feb 29, 2024

OK to sit on this until we get everything else done and then decide if it's needed?

My feeling is it probably is not needed, and we should not further convolute device "API" if there's not a good reason.

@chu11
Copy link
Member Author

chu11 commented Feb 29, 2024

sounds good. I'll peel off some of the cleanup commits into #150

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

Successfully merging this pull request may close these issues.

2 participants