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

Support for ipmievd. #2

Merged
merged 2 commits into from
Sep 10, 2013
Merged

Support for ipmievd. #2

merged 2 commits into from
Sep 10, 2013

Conversation

razorsedge
Copy link
Contributor

This initial PR adds basic ipmievd server support and defaults to running the service. I can provide another commit that adds a class parameter to selectively turn it on.

This tracks issue #1.

@jhoblitt
Copy link
Owner

Some how I missed the notification email for this PR. This looks great.

jhoblitt added a commit that referenced this pull request Sep 10, 2013
@jhoblitt jhoblitt merged commit 2b6de1a into jhoblitt:master Sep 10, 2013
@jhoblitt
Copy link
Owner

@razorsedge I added some validation of the $start_ipmievd param you introduced in this commit f76e51f

mojothemonkey added a commit to mojothemonkey/puppet-ipmi that referenced this pull request Aug 3, 2016
I find some of my servers have ipmi running on channel jhoblitt#2 only (plugged into different physical port maybe - who knows).
so the impi_ipaddress etc facts (which come from channel jhoblitt#1) are not set. as channel jhoblitt#1 is not configured.

instead of always taking channel jhoblitt#1 for these, could we take 'the first found LAN channel' instead? (asside: this is the behaviour when running 'ipmitool lan print' without picking a channel).

have put in a suggested change for this. think it would work to only set each of the ipmi_<name> facts if not set so far.

cheers,
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