From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [GSoC] Rewrite Hydra to be more integrated with Guix.
Date: Wed, 23 Mar 2016 15:08:40 +0100 [thread overview]
Message-ID: <87io0duw0n.fsf@gnu.org> (raw)
In-Reply-To: <20160322213124.GB2135@solar> (Andreas Enge's message of "Tue, 22 Mar 2016 22:31:24 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> In the end, I think it would be interesting to not use the offload approach,
> where the offloading machine sends all inputs to the build machine, which
> returns the result, so that more or less the complete set of binary packages
> flows along the tree of build machines to the root and the other way round.
> (As I recently understood during discussions with Ludovic, currently we have
> a tree of height one: hydra is the root and all build machines are the leaves;
> but the offloading mechanism could transparently work with trees of bigger
> height, where hydra offloads to a root of a smaller build cluster, which
> itself offloads to one of its subordinate build machines. And so on. The same
> thing would also work in the Debian setting, assuming that build requests
> come from the leaves and are forwarded towards the root, while a work package
> is handed down the other way.) Now it would be interesting if machines just
> got build jobs (or made requests) and looked for the necessary inputs inside
> a big magma/cloud/gnunet/ipfs/mirror network, compiled the package, and
> dropped the result into the same magma. Already in our current set-up, it
> would be useful if hydra need not send the build inputs, but build machines
> could just fetch them from an arbitrary nginx mirror, where they are cached.
I agree. However, I think there are a lot of unknowns, which makes it
unsuitable for a GSoC project.
That’s why I was suggesting that Mathieu do not consider workload
distribution (meaning we would keep using the existing offload
mechanism) as part of this project.
Ludo’.
prev parent reply other threads:[~2016-03-23 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 21:38 [GSoC] Rewrite Hydra to be more integrated with Guix Mathieu Lirzin
2016-03-18 8:29 ` Alex Kost
2016-03-18 20:55 ` Ludovic Courtès
2016-03-19 7:48 ` Alex Kost
2016-03-19 20:59 ` Ludovic Courtès
2016-03-18 21:02 ` Ludovic Courtès
2016-03-22 21:31 ` Andreas Enge
2016-03-23 14:08 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io0duw0n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.