unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Ricardo Wurmus <rekado@elephly.net>, guix-devel@gnu.org
Cc: Steve McIntyre <steve@einval.com>
Subject: Re: What ARM hardware should we buy and where should we host it?
Date: Mon, 03 Sep 2018 10:59:38 -0700	[thread overview]
Message-ID: <87tvn65unp.fsf@aikidev.net> (raw)
In-Reply-To: <87lg8izu99.fsf@elephly.net>

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

On 2018-09-03, Ricardo Wurmus wrote:
> The first question is what ARM hardware to buy; the second is where to
> host that hardware.  Here are some considerations:
>
> - The new systems should be easy to host in a data centre; this might
>   mean that we need rack-mounted servers, or that we need a co-location
>   data centre that accepts machines with unusual form factors.
>
> - The system should be able to build substitutes for both armhf and
>   aarch64.  Not all aarch64 CPUs support building for armhf, for
>   example.
>
> - We need to be able to restart the machine remotely.  If members of the
>   Guix project have no physical access to the hosting site, this can be
>   done via remote-controlled power supply or similar.

Debian also has similar needs for build machines and is currently
exploring new hardware. There was a pretty good summary a few months
back:

  https://lists.debian.org/debian-arm/2018/06/msg00062.html


One of the most promising seems to be the SynQuacer:

  https://www.96boards.org/product/developerbox/

With a 24-core processor, SATA, PCIe, USB 3.0, micro-atx form-factor,
and 4 ram slots (up to 64GB, in theory, but may be picky about
ram).

Sounds like they're working with Debian's 4.17.x kernels, so should have
reasonable mainline linux support.

Steve McIntyre (CCed) has been rebuilding debian with them to test them
out, and my impression is it's been going pretty well. Might be more
details in the Debian ARM ports BoF video:

  https://debconf18.debconf.org/talks/93-arm-ports-bof/


> One system that looks promising for co-location is the Softiron
> Overdrive 3000 (a rack-mounted ARM server.)  A system suitable for
> hosting at home is the Softiron Overdrive 1000.

It does sound like the processors used in the Overdrive systems are
officially EOL, but maybe there are still enough of them that SoftIron
will continue to support them for a while. I'll see if I can follow-up
on that, too.


live well,
  vagrant

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

  parent reply	other threads:[~2018-09-03 18:00 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 [this message]
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
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=87tvn65unp.fsf@aikidev.net \
    --to=vagrant@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    --cc=steve@einval.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 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).