pbulk.sh script supports running
unprivileged bulk build and helps configuring distributed bulk builds.
Distributed bulk builds support either building in worker chroots
(each node is a path to a different chroot)
that replicate the target system, including the pbulk prefix,
or remote machines (each node is
an IP address that must be accessible over SSH without a password).
====
This sounds .. a bit dangerous, considering all those ssh bruteforce bots living around ...
Is there chance someone mods this script so it will accept list of nodes and their passwords?
Or may be for exotic qemu builds just restrict accepting ssh connections from few configured IPs ?
master_ip to a public address, and add
the list of slave IP addresses to *_clients. They will need to be accessible
via SSH as root from the master, and will need to have their own installs of
/usr/pbulk as well as sharing the same /content mount as the master, most
likely over NFS.
autoswc’s results
aren’t impressive. The main problem is that it’s on you (the
administrator) to curate the list of checks to cache. This is a very
difficult task as it requires looking at what configure
scripts are doing throughout a bulk build and determining which checks
are safe to cache and which aren’t, and ain’t nobody have time for that.