unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: What ARM hardware should we buy and where should we host it?
Date: Fri, 14 Sep 2018 23:37:25 +0200	[thread overview]
Message-ID: <877ejn69re.fsf@elephly.net> (raw)
In-Reply-To: <20180911213331.GA13582@jurong>


Hi Andreas,

> On Mon, Sep 03, 2018 at 01:37:54PM +0200, Ricardo Wurmus wrote:
>> The first question is what ARM hardware to buy; the second is where to
>> host that hardware.  Here are some considerations:
>
> concerning hosting, I could easily host one smaller machine (like the
> Overdrive 1000) in my living room, Tobias has stepped up, and I suppose
> other members of the Guix community could do so as well. So we would end
> up with a somewhat distributed effort, which would be nice for resilience
> and spreading system administration load.

Yes, this is good.

Close to the end of this year I could probably also start hosting one
Overdrive 1000 at my home.  (After moving to a new place.)

> For more centralised options, we could host machines at Aquilenet; in
> addition to the rack in the datacentre where they host bayfront, they
> just opened a "free form hosting option". Prices are here:
>    https://atelier.aquilenet.fr/projects/services/wiki/Hergementlibre/7/diff

Thanks for sharing this.  In my opinion, it would be good if we could
increase the number of build machines first before we allow too much of
the funds to be regularly consumed by hosting costs.

--
Ricardo

  reply	other threads:[~2018-09-14 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 11:37 What ARM hardware should we buy and where should we host it? Ricardo Wurmus
2018-09-03 16:28 ` Tobias Geerinckx-Rice
2018-09-14 21:26   ` Ricardo Wurmus
2018-09-14 22:02     ` Tobias Geerinckx-Rice
2018-09-03 17:59 ` Vagrant Cascadian
2018-09-03 18:11   ` Steve McIntyre
2018-09-04 18:03   ` Leo Famulari
2018-09-05  0:05     ` Steve McIntyre
2018-09-11 21:33 ` Andreas Enge
2018-09-14 21:37   ` Ricardo Wurmus [this message]
2018-09-15 13:42     ` Andreas Enge
2018-09-14 20:22 ` Vagrant Cascadian
2018-09-14 21:28   ` Ricardo Wurmus

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=877ejn69re.fsf@elephly.net \
    --to=rekado@elephly.net \
    --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 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).