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).
Deployment #
| Attribute | Omada |
|---|---|
| Container runtime | Podman |
| Web UI port | 8043 (HTTPS) |
| Discovery | L2 discovery |
| systemd unit | omada-controller.service |
Air-Gapped Installation #
Container images are fetched as tarballs from the local artifacts server:
- Artifacts role downloads image from upstream, saves as tarball
- Controller role fetches tarball from
http://artifacts.<site>.deevnet.net/ podman loadimports the imagepodman createsets up the container- systemd manages the lifecycle
Relationship to Other Roles #
| Role | Relationship |
|---|---|
| artifacts | Provides container image tarballs |
| base | System prerequisites |
Details #
For full configuration details, managed devices, and API automation, see Network Controllers.