Infrastructure

End-to-end automation of Proxmox ISO customization and VM provisioning using Docker and libvirt with support for dual QCOW2 disks.

💽 RAID Explained Modern infrastructure demands resilience, speed, and data integrity. Whether you’re managing a homelab, a Proxmox cluster, or a full-scale data center, RAID (Redundant Array of Independent Disks) is foundational. In this blog, I break down what RAID is, how each level works, when to use them, and the trade-offs involved. We’ll also explore how RAID fits into virtualized environments like QEMU and how to use it responsibly even with modern filesystems like ZFS. ...

This document describes how to use the Dockerized Proxmox Auto Installer image to generate unattended Proxmox VE installation ISOs for multiple profiles (e.g., pve-1, pve-2). Overview The proxmox-auto-installer Docker image wraps the official proxmox-auto-install-assistant tool to convert a standard Proxmox VE ISO into an unattended-install ISO using profile-specific answer.toml files. By specifying a profile name, you can maintain multiple configurations and generate distinct custom ISOs in a reproducible manner. Prerequisites Docker installed (version 20.10+). A Proxmox VE ISO (e.g., proxmox-ve_8.4-1.iso). Profile directories each containing an answer.toml file. Write permissions for the output directory. Directory Structure Scripts/ ├── iso/ │ ├── proxmox-ve_8.4-1.iso # Base ISO │ └── output/ # Generated ISOs ├── secrets/ │ ├── pve-1/ │ │ └── answer.toml # Profile pve-1 settings │ └── pve-2/ │ └── answer.toml # Profile pve-2 settings ├── Dockerfile # Build definition └── entrypoint.sh # Profile-aware entrypoint Building the Docker Image Run the following command from the directory containing the Dockerfile and entrypoint.sh: ...

📡 Full Network Addressing Architecture for Hybrid Infrastructure 1. 🎯 Concept Overview This document defines a highly structured, hierarchical IP addressing and hostname convention for a multi-environment infrastructure that includes: Baremetal systems (e.g., Arch Linux on sitar-1-arch) Virtualized systems (e.g., Proxmox VMs, OPNsense appliances) Containerized services (e.g., Docker networks) Mobile-edge systems (e.g., Termux-based clients or gateways) Future cloud or experimental research subnets The network design is hierarchical, incremental, and self-documenting, using a w.x.y.z IP structure and FQDN conventions for every entity on the network. ...