rgoncalves.se ~~ ansible
Peronal infrastructure, network mess and homelab. Every critical node such as routers and hypervisor are/will be powered by BSD systems.
For now, the principal hypervisor is
bhyve on FreeBSD, and the domain
controller is a mix of
wireguard on OpenBSD latest.
- OpenBSD first! Playbooks, roles and tasks are aimed to be deployed on OpenBSD instance first. Because we also need a fallback system, AlpineLinux is the next system to be targeted.
- domain controller :
wireguard. Checkout https://bsd.plumbing for the first two components.
acme-clientis also needed for providing https. Note: https is provided from the domain controller level. The traffic from the domain controller host and source host is http only, but secured via the wireguard tunnel.
- ws: workstation
- dc: domain controller
- st: stack server
- sw: switch
- rt: router
- st[x][role][number]: virtual machine
dc0 : OPENBSD domain-controller
- wireguard (exit-node)
rt0 : DDWRT router
stack0 : FREEBSD hypervisor
st0dev0 : OPENBSD development
st0cld0 : OPENBSD cloud
st0gme0 : ALPINE games
ST0SBX-0 : OPENBSD
ST0SBX-1 : ALPINE
ST0SBX-2 : 9FRONT
A subdirectory in
roles for workstations setup. It targets development
machine where these playbooks are launched.
It currently supports bootstrapping for:
- voidlinux (referred as
It setups main user, development packages, power scripts, services, system wide configuration files.
good to know
In various roles, the term
httpd is used. For this particular infrastructure,
it is NOT the apache web server, but instead the OpenBSD web server