From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Subject: What ARM hardware should we buy and where should we host it?
Date: Mon, 03 Sep 2018 13:37:54 +0200 [thread overview]
Message-ID: <87lg8izu99.fsf@elephly.net> (raw)
Hi Guix,
currently, we have a very small number of ARM build machines that
provide some substitutes for armhf and aarch64 systems. (See
https://www.gnu.org/software/guix/donate/ for details.)
We would like to increase this number by purchasing more systems, but we
need your help to get this right.
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.
We are looking for volunteers who could either host a machine at home or
in a data centre that they could get emergency access to.
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. If you know of other
machines that would be suitable for our purposes, please let us know!
(The cost for the machines and for hosting them in a data centre would
be covered by the Guix project, but we are also willing to accept
machine donations if we can also find a volunteer to provide hosting.)
--
Ricardo
next reply other threads:[~2018-09-03 11:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 11:37 Ricardo Wurmus [this message]
2018-09-03 16:28 ` What ARM hardware should we buy and where should we host it? 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
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=87lg8izu99.fsf@elephly.net \
--to=rekado@elephly.net \
--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).