unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Christopher Baines <mail@cbaines.net>
Cc: help-guix@gnu.org
Subject: Re: How to create a substitute server with substitutes that failed?
Date: Thu, 27 Aug 2020 02:22:52 +0200	[thread overview]
Message-ID: <87r1rtuecj.fsf@web.de> (raw)
In-Reply-To: <87h7spw2wo.fsf@cbaines.net>

[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]


Christopher Baines <mail@cbaines.net> writes:

> Dr. Arne Babenhauserheide <arne_bab@web.de> writes:
>
>> I’d like to create a small server that provides substitutes for
>> packages for which I often have to build a fallback (mostly ungoogled
>> Chromium).
>>
>> How can I do that? Is there already a simply way?
>
> It's not simple (yet), but I'm hoping to get there eventually with the
> Guix Build Coordinator.
>
> 1: https://git.cbaines.net/guix/build-coordinator/about/
> I realise the promise of being able to do this more easily in the future
> isn't that helpful, but I still wanted to mention the Guix Build
> Coordinator in case it's something you're interested in.

It sounds promising and I’m not in so much of a hurry that I can’t wait
a bit more.

Thank you!

What I need is likely much simpler, though: I need a hook which triggers
whenever a package had to be built locally. That way we could have
dynamic substitute-servers.

And seeing guix publish run locally got me wishing more that I’d already
be finished with my download-mesh implementation, because guix would be
a perfect usecase for that: We can actually add headers and people have
long-running servers. Parts of the content-addressed storage and
chunk-assembly are already done, but I’m still missing the validation of
chunks and making currently running downloads available.

Conceptually it’s simple: Users could tell guix to serve all derivations
they downloaded and tell the server to mark their guix-daemon as
content-addressed alternate source (X-Alt), then when someone downloaded
something like the 828MiB chromium derivation, the original server would
hand out a list of X-Alts, the hash for content-addressed retrieval and
a merkle-tree of chunk hashes for chunk-validation, so clients could
download from other clients without having to trust them.

The current state of my implementation of such a server and downloader
is at https://hg.sr.ht/~arnebab/wispserve/browse/wispserve/serve.w?rev=tip

And while writing this message I implemented serving while downloading.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]

  reply	other threads:[~2020-08-27  0:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r1rtwtes.fsf@web.de>
2020-08-26 11:18 ` How to create a substitute server with substitutes that failed? Dr. Arne Babenhauserheide
2020-08-26 12:07   ` Julien Lepiller
2020-08-26 14:56     ` Dr. Arne Babenhauserheide
2020-08-26 15:26       ` Julien Lepiller
2020-08-26 16:12         ` Dr. Arne Babenhauserheide
2020-08-26 17:00           ` Julien Lepiller
2020-08-26 20:47   ` Christopher Baines
2020-08-27  0:22     ` Dr. Arne Babenhauserheide [this message]
2020-08-27 14:10   ` zimoun
2020-08-27 20:32     ` Dr. Arne Babenhauserheide

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=87r1rtuecj.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=help-guix@gnu.org \
    --cc=mail@cbaines.net \
    /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.
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).