Skip to content

Monitor BOINC hosts and update remote LEDs using REST calls to reflect their workload.

License

Notifications You must be signed in to change notification settings

WinterSnowfall/pi_boincmon

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

36 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

pi_boincmon

The third best thing after the invention of garlic bread and pi_wrestled. At least for BOINC users which want to leverage their pi_wrestled-powered LEDs array. Witten in python3, it provides a framework for querying BOINC hosts to analyze the number of running BOINC tasks and updating LEDs to reflect their status (expected amount of running tasks, below expected ammount, BOINC not running, etc).

What do I need to do to get it running on my Raspberry Pi?

Paramiko is used for implementing the ssh client connections to monitored hosts. You can install it manually on Debian/Ubuntu, as follows:

sudo apt-get install python3-paramiko

Do I need to run it on a Raspberry Pi?

No, not really. Any OS with a working python3.6+ installation will do.

Does this only work with pi_wrestled? Can I trigger other sort of REST calls?

There's some degree of flexibility in terms of payload, so yes, in theory you could even do that without any rewrites. A more likely scenario would still involve some code changes.

How do I configure this thing?

Look under the /conf folder for a sample config file. You can add as many host entries as you like, just number them incrementally, as per the sample.

What's with the wierd passwords?

I've written a separate module to encrypt the ssh user passwords of the monitored hosts using a master password. To generate the encrypted text that you need to add in the config file just run pi_password.py and follow the on-screen prompts.

Can't I use a ssh key to connect to my hosts, instead of passwords?

Why, yes. Why bother with passwords anyway, right? You'll need to set:

ssh_key_authentication = true

In the .conf file and provide the path to your private ssh key. Doing so will make pi_boincmon ignore all (if any) host password entries. Note that you'll have to take care of propagating the key yourself and configuring a working ssh setup between the local host and your BOINC hosts.

About

Monitor BOINC hosts and update remote LEDs using REST calls to reflect their workload.

Topics

Resources

License

Stars

Watchers

Forks

Languages