... | ... | @@ -267,6 +267,49 @@ Finally, the following steps need to be performed to populate `/srv`: |
|
|
|
|
|
<!-- e.g. web APIs, commandline clients, etc -->
|
|
|
|
|
|
### Serial console
|
|
|
|
|
|
The APU should provide a serial console access over the DB-9 serial
|
|
|
port, standard 115200 baud. The install is configured to offer the
|
|
|
bootloader and a login prompt over the serial console, and a basic
|
|
|
[BIOS](#bios) is also available.
|
|
|
|
|
|
### LEDs
|
|
|
|
|
|
The APU has no graphical interface (only serial, see above), but there
|
|
|
are LEDs in the front that have been configured from Puppet to make
|
|
|
systemd light them up in a certain way.
|
|
|
|
|
|
From left to right, when looking at the front panel of the APU (not
|
|
|
the one with the power outlets and RJ-45 jacks):
|
|
|
|
|
|
1. The first LED lights up as soon as systemd starts
|
|
|
(`DefaultDependencies=no`)
|
|
|
2. The second LED lights up when systemd has booted (more or less,
|
|
|
`After=multi-user.target` and `Type=idle`)
|
|
|
3. The third LED should blink according to the "activity" trigger
|
|
|
which is defined in [ledtrig_activity](https://github.com/torvalds/linux/blob/0bcc4025550403ae28d2984bddacafbca0a2f112/drivers/leds/trigger/ledtrig-activity.c) kernel module
|
|
|
|
|
|
### Network
|
|
|
|
|
|
The three network ports should be labeled according to which VLAN they
|
|
|
are supposed to be configured for, see the [Quintex network layout](howto/quintex#network-topology)
|
|
|
for details on that configuration.
|
|
|
|
|
|
From left to right, when looking at the *back* panel of the APU (the
|
|
|
one with the network ports, after the DB-9 serial port):
|
|
|
|
|
|
1. `eth0 public`: public network interface, to be hooked up to the
|
|
|
`public` VLAN, mapped to `eth0` in Linux
|
|
|
|
|
|
2. `eth1 storage`: private network interface, to be hooked up to the
|
|
|
`storage` VLAN and where DHCP and TFTP is offered, mapped to
|
|
|
`eth1` in Linux
|
|
|
|
|
|
3. `eth2 OOB`: private network interface, to be hooked up to the
|
|
|
`OOB` ("Out Of Band" management) VLAN, to allow operators to
|
|
|
access the OOB interfaces of the other servers
|
|
|
|
|
|
## Authentication
|
|
|
|
|
|
<!-- SSH? LDAP? standalone? -->
|
... | ... | |