From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ngillmann@runbox.com>
Cc: 24496@debbugs.gnu.org
Subject: bug#24496: offloading should fall back to local build after n tries
Date: Wed, 05 Oct 2016 13:36:20 +0200 [thread overview]
Message-ID: <87a8ej81u3.fsf@gnu.org> (raw)
In-Reply-To: <87vax8nis5.fsf@we.make.ritual.n0.is> (ng0's message of "Tue, 04 Oct 2016 17:08:58 +0000")
ng0 <ngillmann@runbox.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> Like you say, on Hydra-style setup this could be a problem: the
>> front-end machine may have --max-jobs=0, meaning that it cannot perform
>> builds on its own.
>>
>> So I guess we would need a command-line option to select a different
>> behavior. I’m not sure how to do that because ‘guix offload’ is
>> “hidden” behind ‘guix-daemon’, so there’s no obvious place for such an
>> option.
>
> Could the daemon run with --enable-hydra-style or --disable-hydra-style
> and --disable-hydra-style would allow falling back to local build if
> after a defined time - keeping slow connections in mind - the machine
> did not reply.
That would be too ad-hoc IMO, and the problem mentioned above remains.
>> In the meantime, you could also hack up your machines.scm: it would
>> return a list where unreachable machines have been filtered out.
>
> How can I achieve this?
Something like:
(define the-machine (build-machine …))
(if (managed-to-connect-timely the-machine)
(list the-machine)
'())
… where ‘managed-to-connect-timely’ would try to connect to the
machine with a timeout.
> And to append to this bug: it seems to me that offloading requires 1
> lsh-key for each
> build-machine.
The main machine needs to be able to connect to each build machine over
SSH, so indeed, that requires proper SSH key registration (host keys and
authorized user keys).
> (https://lists.gnu.org/archive/html/help-guix/2016-10/msg00007.html)
> and that you can not directly address them (say I want to create some
> system where I want to build on machine 1 AND machine 2. Having 2
> x86_64 in machines.scm only selects one of them (if 2 were working,
> see linked thread) and builds on the one which is accessible first. If
> however the first machine is somehow blocked and it fails, therefore
> terminates lsh connection, the build does not happen at all.
The code that selects machines is in (guix scripts offload),
specifically ‘choose-build-machine’. It tries to choose the “best”
machine, which means, roughly, the fastest and least loaded one.
HTH,
Ludo’.
next prev parent reply other threads:[~2016-10-05 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 9:39 bug#24496: offloading should fall back to local build after n tries ng0
2016-09-26 9:20 ` Ludovic Courtès
2016-10-04 17:08 ` ng0
2016-10-05 11:36 ` Ludovic Courtès [this message]
2021-12-16 12:52 ` zimoun
2021-12-17 15:33 ` Ludovic Courtès
2021-12-17 21:57 ` Maxim Cournoyer
2021-12-18 0:10 ` zimoun
2021-12-21 14:28 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8ej81u3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=24496@debbugs.gnu.org \
--cc=ngillmann@runbox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).