all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, myglc2 <myglc2@gmail.com>
Subject: Re: Guix infrastructure
Date: Fri, 07 Jul 2017 14:19:23 +0200	[thread overview]
Message-ID: <87tw2o8mno.fsf@gnu.org> (raw)
In-Reply-To: <20170707030042.GD1280@jasmine.lan> (Leo Famulari's message of "Thu, 6 Jul 2017 23:00:42 -0400")

Hello Guix!

Leo Famulari <leo@famulari.name> skribis:

> On Thu, Jul 06, 2017 at 08:09:17PM -0400, myglc2 wrote:
>> On 07/01/2017 at 14:01 Leo Famulari writes:
>> > ... Bayfront is still not fully operational, so hydra.gnu.org is still
>> > serving as the front-end of the build farm. We are still relying on the
>> > Hydra software. That is, the situation is basically the same as before.
>> > Adding build machines will not help very much until the front-end
>> > hardware gets faster.
>> 
>> This leaves me wondering ...
>> 
>> Is the hydra/front-end hardware going to be upgraded?
>
> Yes...
>
>> Is bayfront/cuirass intended to replace hydra?
>
> ... and yes.
>
>> The bayfront hardware described here ...
>> 
>> https://www.gnu.org/software/guix/news/growing-our-build-farm.html
>> 
>> ... seems weak to me. Is there a plan to scale it up and make it redundant?
>
> It will be a lot more powerful than the current Hydra system. As for
> specific plans, I'll let those administering the system chime in.

That machine is super powerful… but alas, it has also been terribly
unstable.  Vikings has been kind enough to assist us; they’ve notably
provided us with CPU replacements once already.  Despite these efforts,
the machine is still crashing.  We’re investigating with them what to
do next.

On top of that, all the testing and all the back and forth takes an
awful lot of time, which is in part due to hardware problems being hard
to pinpoint and debug in general, and in part due to us here in Bordeaux
(where the machine is hosted) being unable to scale up.


Infrastructure has been the project’s Achilles’ heel since we run the
crowdfunding campaign in Dec. 2015 (!).  Now it’s becoming detrimental
to the project.  Our initial plan was to buy more Libreboot-based
machines like the one above once the first one has proved to work well.
However, given the situation, we’ve been discussing on guix-sysadmin a
change in strategy, at least in the short term; Ricardo has been working
on re-purposing used hardware for our needs, and that may well be our
short- to medium-term solution.

For now, we prefer not to entrust the binaries we deliver to commercial
VPS providers.  I think we owe it to our users, but it undoubtedly has a
cost in terms of system maintenance.

I not only sympathize with your frustration, ng0, I feel it even ten
times more.  ;-)  Several of us are determined to come up with a
solution quickly, so I hope that will materialize soon!

Thanks,
Ludo’.

  reply	other threads:[~2017-07-07 12:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01 17:36 stability of master - just QA and hydra is not enough ng0
2017-07-01 18:01 ` Leo Famulari
2017-07-01 19:24   ` ng0
2017-07-01 19:52     ` Leo Famulari
2017-07-07  0:09   ` myglc2
2017-07-07  3:00     ` Guix infrastructure Leo Famulari
2017-07-07 12:19       ` Ludovic Courtès [this message]
2017-07-08 23:50         ` ng0
2017-07-09  9:21           ` Ricardo Wurmus
2017-07-09 12:06             ` Liam Wigney
2017-07-09 22:57               ` ng0
2017-07-09  0:43         ` myglc2
2017-07-09  8:49           ` Ricardo Wurmus
2017-07-11 18:44             ` Catonano
2017-07-09  6:30       ` Efraim Flashner

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=87tw2o8mno.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=myglc2@gmail.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 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.