[cfarm-users] Automated deployment across multiple cfarm hosts

[Jonathan Wakely]

On Mon, 9 Sept 2024 at 14:00, Simon Josefsson via cfarm-users
<cfarm-users at lists.tetaneutral.net> wrote:
>
> Peter Gutmann via cfarm-users <cfarm-users at lists.tetaneutral.net>
> writes:
>
> > Is anyone doing CI-style automated deployment across multiple cfarm hosts, or
> > more generally on systems where all you've got to play with are SSH, sh/bash,
> > and a compiler?  Conventional approaches seem to require installing CI agents
> > on each target system (and Docker, and cloud access, and ...), I was looking
> > for something that works purely through client-side SSH without requiring
> > system changes on a wide range of very different target systems (this is also
> > useful for testing on oddball SBCs on a local network running obsolete and
> > obscure OSes).  Pipelight looks like a promising candidate, is anyone using that
> > with cfarm hosts, or do you know of another solution?
>
> I thought this usage was against the recommended use of the cfarm, but I
> cannot find a reference now -- was the acceptable use policy modified?

I don't think so, I think it just wasn't formally documented that
people should farm responsibly.

On this mailing list Segher has said:

<quote>
You should never use more than 10% of a machine, and nor for more than
a few hours per day, for any automated task, on shared machines.

The machines are there to use.  That is their purpose.  But, there are
many users, and they should be able to use the machines as well.  And
interactive uses should get priority, always.
[...]
Just makes sure you do not run most of the day, and even then do not
take up a significant fraction of the machines.  You are very welcome
to use the cfarm, but *you have to share*.
</quote>