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
add support for UPS #595
Comments
Thanks for filing the issue. If you can experiment with Network UPS Tools and provide some insight, it could speed up development. Thanks! |
Ok I will try to install it on some linux setup during the weekend and see how it works. |
Ok so things are really easy. I just followd this guide: I want to add that is seems that most of the current UPS support HID and thus usbhid-ups is the most important driver. |
There is also the EPEL package nut-cgi, which adds some GSI scripts for monitoring. I would guess these are not the top priority though. |
I have set myself the task of integrating/adding nut into Rockstor as a getting started exercise, but I struggle for time. I am quite familiar with NUT and linux though. I am however unfamiliar with many of Rockstor's technologies / languages. So fingers crossed. I hope not to duplicating anyone's efforts but I have only just found this issue and just now getting setup / started. Please comment with any pointers. @erazortt yes usbhid-ups is a good first bet and I intended to offer it as a first suggestion but the nut package comes with them all anyway and they are each only tiny. For my own itch / requirement I first have to implement netclient mode to a nut server (even easier to setup) so hoping that should help ease me in. |
I am currently working on this issue and have the following proposal:- |
Placeholder for another dropdown on monitor mode
Placeholder for another dropdown on monitor mode
Add a couple more required fields
Was trying for a shortcut but broke a few other things.
Might be nice to have user feedback of no detection or ups model and load.
Had to add a hack to cope with multi word options as parser only dealt with single word option entries as that was the format for the majority of options.
Pre-configured nut AT options to match our upssched-cmd. Also contains config for pipe and lock files.
Contains pre-configured filters to act on events as defined in upsched.conf via custom AT commands.
…#595 Addresses the comment by phil on github.
To simplify config entry I origianlly disabled entries but better to hide them. Thanks @suman for guidance on this one.
Thanks @suman for guidance on this one.
Initially only check if nut-monitor is working as that should always be on / up when the service is up. However we might want to revisit this as may not be enough.
Tried puttin epel-release repo installer package before nut and nut-xml but this didn't work so leaving epel in rpm-deps and then add a section to be executed after rpm-deps (with its epel-release) that can now install nut and nut-xml from the epel that should now be registered as a repo.
Also throw exception if config is empty at this point. Improve comments.
…ockstor#595 When the nut service is switched on without a prior config we have a json type error in base_service.py. With this catch we present a user friendly check config suggestion and do the same when other config errors are encountered that stop the service from starting. The underlying error is still logged.
@erazortt Thanks for opening this issue, as of release 3.8-8 we now have at least a beta implementation of a nut configuration component in place. In time it is planned to improve on this feature and improve especially on the ups status info but going forward I think it's best that individual issues for nut be raised for problems as they are defined. I you are not comfortable with closing this issue or finding it closed then please comment and or reopen. |
Very happy to close this issue! There will be improvements no doubt, but thanks for contributing this feature @phillxnet |
This is quite an important topic for serious NAS. I do not know much about it, but other projects use the Network UPS Tools, which should very easily be integrable.
The text was updated successfully, but these errors were encountered: