Problem
The lab needs to be more than a collection of VMs. It needs to show how a small physical environment can be designed, documented, and operated using patterns that resemble real infrastructure work.
FILE 01 · Active · Infrastructure architecture
Enterprise Homelab
A public-safe infrastructure lab used to practice and demonstrate network segmentation, Windows/Linux services, automation, monitoring, backups, documentation, and future multi-site design.
Design intent
Keep the public version safe while still showing architecture decisions: segmentation, routing boundaries, service ownership, monitoring, backups, and the path toward a second site.
Topology
Site 1 active, Site 2 planned.
VLAN file
Documented segmentation.
Server file
Service ownership.
Hardware file
Physical gear and Proxmox nodes.
Notes
Chronological build notes.
Dated notes record architecture decisions, troubleshooting findings, and the next work required to keep the lab documentation aligned with the running environment.
Refreshed the topology diagram with traditional network iconography and locked the Site 2 WAN decision: DMVPN runs edge-to-edge from EDGE-RTR01 (Cisco 1941) to a planned Cisco ISR 4331, with VyOS deferred to a much-later routing lab.
Confirm final core/access hardware ownership and keep server placement updated as roles move between Proxmox nodes.