unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: March update on bordeaux.guix.gnu.org
Date: Wed, 22 Mar 2023 15:27:57 +0100	[thread overview]
Message-ID: <87cz50dfo2.fsf@gnu.org> (raw)
In-Reply-To: <874jqjvwvt.fsf@cbaines.net> (Christopher Baines's message of "Thu, 16 Mar 2023 19:29:30 +0000")

Hi Chris,

Christopher Baines <mail@cbaines.net> skribis:

> ## Serving fixed output files by hash
>
> bordeaux.guix.gnu.org is now in the list of content addressed mirrors
> [2].

Yay!

> ## Referential integrity
>
> This is usually something I think about in the context of databases, but
> nars/narinfos have references, and I've been working to ensure that for
> any nar provided by bordeaux.guix.gnu.org, you're also able to fetch any
> nar it references.

Great that you looked into it.  That’s something we did not explicitly
address until now, on the grounds that ‘guix substitute’ would typically
look up both a store item and its dependencies, which in practice means
that the TTL of a store item and that of its dependencies would likely
be synchronized.  But clearly, it’s best to ensure that by construction.

> ## Offering zstd compressed nars

Yay!

> ## Next steps
>
> Last time I said that I thought the main blocking issue in making
> bordeaux.guix.gnu.org the default substitute server to try first was the
> lack of zstd nars. Some nars are now available with zstd compression, so
> there's progress been made on this at least. I think a good argument can
> be made for trying bordeaux.guix.gnu.org being better for users than
> trying ci.guix.gnu.org first, but it's not clear cut.

I think keeping both is ideal, notably from a fault-tolerance viewpoint.

> On the issue of expanding the storage for nars, I've submitted the
> request to purchase an additional hard drive for hatysa to expand the
> storage there. There is still a need to come up with a plan to replace
> bishan when it runs out of space (ideally before!).

Definitely; this should be high-priority for the project.

Thanks!

Ludo’.


  parent reply	other threads:[~2023-03-22 14:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 19:29 March update on bordeaux.guix.gnu.org Christopher Baines
2023-03-21  2:49 ` Maxim Cournoyer
2023-03-22 14:27 ` Ludovic Courtès [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-27 13:49 Christopher Baines
2024-03-29 10:21 ` Ludovic Courtès
2024-03-29 10:53   ` Christopher Baines
2024-04-09 15:37     ` 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=87cz50dfo2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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.
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).