unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dftxbs3e <dftxbs3e@free.fr>
To: Tobias Geerinckx-Rice <me@tobias.gr>, Guix Devel <guix-devel@gnu.org>
Subject: Re: New POWER9 machines for the Guix build farm?
Date: Fri, 29 Nov 2019 09:25:12 +0100	[thread overview]
Message-ID: <9aeb5196-0b37-e4f0-c3f7-91ac2c10e976@free.fr> (raw)
In-Reply-To: <871rtsakoq.fsf@nckx>

Hello,

I'm really happy to hear this! I also do own a POWER9 machine.

I have a Talos II with 2x 8 SMT4 cores POWER9 DD2.2 CPUs (64 threads), 
64GB of RAM and an AMD WX7100 GPU (amdgpu libre driver).

I run Fedora on it since more than a year now, it's been my main 
workstation without any major issue.

I'm happy to provide assistance, I encourage GNU Guix developers to join 
#talos-workstation on Freenode's IRC, we have a friendly active 
community that is always happy to help on POWER9 matters.

dftxbs3e

On 11/28/19 1:50 AM, Tobias Geerinckx-Rice wrote:
> Fellow Guix,
>
> The Guix sysadmins are considering buying shiny hardware for the 
> ci.guix.gnu.org build farm, and it would be awesome if that included 
> our first POWER9 machine(s)!
>
> However, few (if any) Guixers have any hands-on experience with this 
> architecture, let alone buying and installing whole systems. Some 
> remember a bad experience with a prominent vendor, and it would appear 
> that they're not alone[0].
>
> There's also some concern that getting these machines up and running 
> will take significant effort.
>
> So please, share your expertise and experience in this area! Ideally, 
> we need someone to volunteer to (help) set up any new POWER9 boxes and 
> later take care of them when needed.  It would certainly help justify 
> the multi-thousand-euro bill.
>
> Kind regards,
>
> T G-R
>
> PS: For the shorter term, I've applied for an 8-core POWER9 LE 
> instance (with 16 GiB of RAM) for Guix at OSUOSL[1].  Assuming that 
> it's accepted, it should be available within a week.
>
> [0]: 
> https://drewdevault.com/2019/09/23/RaptorCS-Blackbird-a-horror-story.html, 
> but read https://drewdevault.com/2019/10/10/RaptorCS-redemption.html 
> as well :-)
> [1]: https://osuosl.org/services/powerdev/

  parent reply	other threads:[~2019-11-29  8:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  0:50 New POWER9 machines for the Guix build farm? Tobias Geerinckx-Rice
2019-11-28  4:01 ` Brett Gilio
2019-11-28 10:57 ` Jonathan Brielmaier
2019-11-28 16:52   ` Leo Famulari
2019-11-29  8:25 ` dftxbs3e [this message]
2019-11-29 12:50   ` Marco van Hulten
2019-12-01 20:35     ` dftxbs3e
2019-12-09  0:19 ` Chris Marusich
2019-12-09  1:22   ` dftxbs3e
2019-12-13 18:55 ` Fwd: GNU Guix POWER9 OpenStack application (was: New POWER9 machines for the Guix build farm?) Tobias Geerinckx-Rice

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=9aeb5196-0b37-e4f0-c3f7-91ac2c10e976@free.fr \
    --to=dftxbs3e@free.fr \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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).