Builder Node on Deevnet IoTaaS

Workstation Role

Mon, 01 Jan 0001 00:00:00 +0000

Workstation Role #

Purpose #

The workstation role configures a host as a developer/admin workstation with users, development tools, and infrastructure automation tooling.

Capabilities #

User Management #

Creates dev users with configurable primary/extra groups
Fetches SSH public keys from GitHub
Sets up home directories and shell preferences

Development Tools #

Category	Packages
Core	git, vim, tmux, golang
ISO/Image	Tools for working with disk images
X11	Display support for GUI tools

HashiCorp Tools #

Configures the HashiCorp RPM repository and installs:

Artifacts Role

Mon, 01 Jan 0001 00:00:00 +0000

Artifacts Role #

Serves the builder’s artifacts: everything a substrate host installs from. What is in scope for the air gap, and why, is in Builder → Air-Gap Scope.

Current Capabilities #

The artifacts server provides:

Artifact Type	Description
Kickstart files	OS installation automation scripts
PXE boot artifacts	Kernel, initrd, boot configuration
Custom scripts	Post-install automation payloads
OS images	ISO images or extracted install trees
Container images	Service image tarballs, loaded by the roles that run them

Artifacts are served via HTTP at artifacts.<site>.deevnet.net.

Bootstrap Role

Mon, 01 Jan 0001 00:00:00 +0000

Bootstrap Role #

The bootstrap role in deevnet.builder makes the Builder the thing new hosts boot from. It works in two modes ( Builder → Authority Transition):

Mode	The Builder provides	Switched by
Core-authoritative (normal)	PXE boot files over TFTP (`in.tftpd`); the core router answers DNS and DHCP	`make core-auth`
Bootstrap-authoritative	DNS, DHCP and TFTP from dnsmasq, and the site’s gateway, with records and reservations from inventory	`make bootstrap-auth`

The rest of this page is the PXE side, which is the same in both modes. How to switch is Authority Transition.

Network Controller Role

Mon, 01 Jan 0001 00:00:00 +0000

Network Controller Role #

Purpose #

The network controller role deploys centralized management software for switches and access points as Podman containers managed by systemd.

Controllers #

Controller	Managed Devices
TP-Link Omada SDN	EAP650-Outdoor AP (adopted); the SG2218 switch is standalone until CHG-0009

Since CHG-0008 the controller runs on dv02nms001v01, and the Builder keeps a stopped cold spare for when that VM is down. The pre-VLAN substrate is built without it ( Management Plane → Network management).