v2.0.0 #5
dev-luigi
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
v2.0.0 is a full rewrite. v1 was one HTML page that pushed fan commands at a single Dell. v2 is a Python/FastAPI backend serving a React dashboard, talking to as many BMCs as you want over
ipmitool.Everything runs on your box. SQLite on disk, no cloud, no telemetry.
What it does
Fan safety
Above your critical threshold (85 °C by default) fans go to 100% and stay there until the temperature clears the hysteresis band. If a BMC stops answering, FanPilot fails safe instead of leaving the fans wherever they were. On shutdown it hands automatic fan control back to the BMC, including on Ctrl+C and
docker stop.Supported hardware
Sensors, power, event log and FRU work on any IPMI 2.0 BMC. Fan control is vendor-specific.
Monitoring-only boxes still get full sensors, power, event log and FRU. If you run Supermicro or IBM, reports are welcome. That is how they move to Tested.
Install
Docker:
On Windows and macOS use
-p 3000:3000instead of--network host.pip (needs
ipmitoolon the system):Open
http://<your-ip>:3000and the setup wizard takes over. No hardware around?ipmideck --demoseeds fake servers so you can click through everything.Coming from v1
There is no in-place upgrade. Different stack, different database, different config. Install fresh and re-add your servers through the wizard.
devluigi06/ipmi-fanpilotdevluigi06/ipmideck/app/dataIPMIDECK_*Port 3000 is unchanged.
Links
Docs · Docker Hub · PyPI · Issues
The docs have per-vendor guides for turning IPMI on: iDRAC, iLO, Supermicro, XCC and IMM.
Bad fan control can damage hardware. Test somewhere that is not production first. Apache-2.0, provided as-is.
Full Changelog: 84df472...v2.0.0
This discussion was created from the release v2.0.0.
All reactions