README.infrastructure 3.62 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12
About the nodes used for
:Author:           Holger Levsen
:Authorinitials:   holger
:Status:           working, in progress
:lang:             en
:Doctype:          article
:License:          GPLv2

== Scope

13 14 15 16
This README is about all the nodes used for and

All nodes run Debian stable, except for the amd64 moonshot nodes, which run Ubuntu 16.04.

17 18
Mattia and Holger have root access to all nodes, including jenkins. Additionally Vagrant has
root access to all armhf nodes.
19 20 21 22 23 24

=== amd64 and i386 nodes

amd64 and i386 nodes run as VMs in the Profitbricks cloud. Mattia and Holger have "physical"
access including remote console and BIOS access.

25 26 27 28 29
The VMs for jenkins.d.n and rb-mail1.r-b.o have a statically allocated IP address, as well
as PTR records for them.  IONOS asked us to inform them ( in case
at some point we will decommission them and the reserved IPs won't be needed anymore, so they
can remove the PTR records and unblock the IP addresses.

30 31 32 33 34
==== nodes at

We now also have 8 nodes running at Contact via #osuosl on freenode or mail to mentioning the machine name in the subject.

Holger Levsen's avatar
Holger Levsen committed
Please note that the machines are called gcc167-174 at

37 38 39
=== arm64 nodes

We have 8 arm64 nodes running on moonshot hardware kindly given access to us by Codethink.
40 41
Holger and Mattia have access to a 9th node acting as console server, reachable as

43 44 45
The process of setting up 8 LeMaker HiKey960 boards is currently stalled, because the setup 
turned out to be more complicated than expected. These boards 
( were sponsored by Hewlett Packard Enterprise
46 47
( and will be hosted by the students association
SOSETH ( at ETH Zurich (
Currently the are located with Axel Beckert.

50 51 52
=== armhf nodes

Vagrant hosts a fantastic zoo of over 23 armhf boards in his basement, to which besides him also
Mattia and Holger have access via a console server. (Technically some of these armhf nodes are also arm64 systems.)

55 56 57 58 59 60 61 62
There'a script to trigger the power on/off/cycle if needed, from hbi1 on Vagrant's local network:

  localhost$ ssh -p 2227
	# ssh key fingerprints:
	# 2048 f5:03:59:fa:a9:f6:97:b0:80:9c:0c:3c:dc:9e:38:59 /etc/ssh/ (RSA)
	# 256 38:e8:16:bb:13:d1:5b:28:39:85:73:11:f2:1f:29:81 /etc/ssh/ (ECDSA)
	# 256 16:cc:1f:0e:39:80:37:64:f7:23:dc:18:3f:58:d3:52 /etc/ssh/ (ED25519)
	# It's advertising an ipv6 address, but it's actually only ipv4 for the
	# foreseeable future and I just need to fix DNS.
64 65 66 67

  hbi1$ cd /srv/rb/ ; ./remote-power NAME on|off|ccl
	# ccl means powercycling…

There are at least three machines, bbx15, jtk1a, and jtk1b that don't tend to
69 70 71 72 73
come up after power cycling, but sometimes even those work too, so it's
worth a try.

A small number of the names listed in cereal differ slightly from
the names used natively... partly due to bugs in cereal. They should be
fairly obvious (e.g. bpi0a vs. bpi0, hb0a vs. hb0).
75 76 77 78 79 80

The serial console access is still read-only, not actually interacting
with the console; think this is a limitation of the way "cereal"
interacts with screen. "cereal l" lists the available systems, and
"cereal f XXX" would connect to "XXX" and tail it's console logs.

81 82
There's a pad too, where we maintain notes about the stati of the nodes. The URL
for this pad is available upon request.

// vim: set filetype=asciidoc: