Tools for deploying and managing a BOINC compute farm using Ansible and Arch Linux.
Homefarm makes it easier and faster to install, reinstall, configure, and update all your BOINC crunchboxes. It also saves your bandwidth: all your compute nodes will install and update from a local repository that lives on the control node.
There are a few assumptions:
- One machine capable of running Docker, to host the controller
- One or more x86_64 or armv7h/l machines capable of running Arch
Linux, to become compute nodes
- It's further assumed that these machines will be used for no other purpose, and it is okay to wipe their drives
- You are aware of your local network configuration, and have IPs to assign to the nodes.
- All nodes are on a private network -- an SSH key with no passphrase will be generated for Ansible's use
- You're familiar with BOINC, projects, workunits, and so on
- 2021-01-11: v2.8.2: Fixes for control image builds
- 2020-12-26: v2.8.1:
updatenow runs per-arch. Various fixes.
- 2020-10-25: v2.8.0: Support for arm7h/arm7l. Admin can now add packages to the local repo.
- 2020-07-08: v2.7.1:
node-initsubcmd renamed to
boinc-config. Fixed deployment of cc_config.xml to nodes
- 2020-06-19: v2.7.0: Automated build/rebuild of control container. Improved initial setup experience. Initial work done to support multiple architectures
See the Release notes for all updates.
- Setting up a farm
- Managing and maintaining your farm
- Problems and troubleshooting
- Have homefarm? Want to install Arch on a machine that isn't
part of the farm? Follow the compute node install process, but
compute-setupafter the first reboot. You'll have a core install with a working network connection, ready for user creation and install of whatever packages you need.
- Have homefarm? Want to install Arch on a machine that isn't part of the farm? Follow the compute node install process, but don't run