Storage1
IPMI
| Name | Value |
|---|---|
| URL | https://storage1-ipmi.mgmt.zentralwerk.org |
| Credentials | see vaultwarden |
RAID controller
To access the disks via smartctl use: smartctl -a -d megaraid,5 /dev/sdp.
ISM
Website https://linux.dell.com/repo/hardware/ism/
- Get current Dockerfile:
wget https://linux.dell.com/repo/hardware/ISM_5400/os_dependent/ism_docker/Dockerfile -O Dockerfile - Re-apply our patches to reduce layer sizes
- Update aliases file:
echo -e "$(curl https://linux.dell.com/repo/hardware/ISM_5400/os_dependent/ism_docker/dellism_aliases.sh)" | sed -e 's|dell_ism_$ISM_VERSION|gitea.c3d2.de/c3d2/ism_5400:latest|g' -e 's|$PLATFORM|podman|g' > dellism_aliases.sh podman build -t gitea.c3d2.de/c3d2/ism_5400 .podman push gitea.c3d2.de/c3d2/ism_5400
libvirtd
The connection string for virsh is: qemu+ssh://root@storage1.cluster.zentralwerk.org/system.
If you want to use a GUI instead, virt-manager is a good option. You can connect under File > Add Connection.
Then choose QEMU/KVM as the Hypervisor, connect via ssh, root as username and storage1.cluster.zentralwerk.org as host and click Connect.
VMs and their payload must be configured to be reboot safe. The host will reboot from time to time and no special attention will be paid to libvirt VMs. This means using encrypted volumes inside the VM is not feasible as it conflicts with being reboot safe, but it also has worse performance as the host level disks are already encrypted with LUKS and us on top of that ZFS. Also ISOs should be unmounted after the host installation is done as they might be garbage collected later and VMs referencing ISOs paths that do not exist prevent the boot of the VM.