BorborProjects / Virtual infrastructure laboratory with Proxmox
PROJECT BRIEF / INDEPENDENT INFRASTRUCTURE LABORATORY
From problem to verifiable outcome.
My independent lab is a space to practice infrastructure design, virtual server administration, remote access and troubleshooting.
Public case study · Sensitive operational specifics intentionally withheldHIGH-LEVEL SYSTEM VIEW — NOT AN AS-BUILT DIAGRAM
Proxmox host → Linux VM / network simulator → isolated lab networks
What needed to change
Build a safe and affordable environment for practical learning in virtualization, Linux operations and enterprise network design.
Constraints & decisions
- Limited home-host compute resources require careful virtual machine allocation.
- Experiments must be isolated from personal devices and public services.
- Repeatable notes matter more than simply starting a virtual machine.
Implementation approach
- Installed and administered a Proxmox VE host on small-form-factor hardware.
- Provisioned an Ubuntu virtual machine and explored remote access through Apache Guacamole.
- Used Cisco Modeling Labs and EVE-NG for routing, switching and service simulations.
- Recorded planned improvements around VLANs, secure remote access and backups.
Validation & evidence
- Confirmed guest installation and console access.
- Tested network settings and remote-access behavior in the laboratory.
- Used repeatable exercises to identify new learning goals.
Lessons learned
- Snapshot and backup are different recovery tools.
- Lab repeatability requires IP plan, resource plan and verification checklist.
- Virtualization is a useful bridge between networking and server operations.
Responsible disclosure: This writeup is a generalized description based on professional or independent project work. It is not an employer-approved as-built diagram. Do not infer production addressing, exact architecture, vendor secrets or customer data from this page.