🌟 Hear Ye! Hear Ye!!
Let it be recorded, in the Book of Realms:
On the 25th day of January, in the year 2026,
a new node was awakened.
🔥 CLI via SSH
🚫 It bows to no GUI
⚙️ It obeys only the will of the one who codes
This is Merlin.
The Envoker of Python
The Wielder of Flask
The Architect of Templates
The Commander of Restart Rituals
The One Who Sources Without Spells
Let all services now respond,
to the call of My Server, My Toys™
🎉✨ Let it be inscribed in the scrolls of Merlin:
On this day, a lone sorcerer tamed the virtual beast named
venv, conjured Flask into service, summoned blueprints and RESTful scrolls, and brought forth a functioning web incantation—all under their own domain.
You now command a living Python web app from your own server, on your own terms. A self-hosted, Flask-powered realm.
This is not a hello world. This is a declaration.
🪄 venv is yours.
🌐 The web answers to your routes.
📜 Your notes are live scrolls.
🧙♂️ Your server, your magic.
Ready for the next chapter whenever you are.
🌟 Hear ye! Hear Ye!! Let it be known:
On the 24th day of August, in the year 2025, Camelot was confirmed as
10.20.30.1, sovereign and steadfast — up for five weeks, unshaken, ruling over a subnet of promise.
Frodo, loyal and curious, bridges realms from the Wi-Fi world into the quiet kingdom.
And now, Fred, the traveller from an ancient land, shall claim his place as 10.20.30.3, not by accident or DHCP, but by decree.
✅ Summary of Current State
Component IP Address Status
Camelot (Linux 42) 10.20.30.1 Accessible via LAN
Frodo (Bridge host) 10.20.30.2 ✅ Default Gateway working
Fred (Windows) 10.20.30.3 Using Frodo as gateway 🌐 Internet
│
Wi-Fi (192.168.11.x)
│
[ Frodo ]
(dual-homed box)
┌───────────────┐
│ 192.168.11.185│
│ 10.20.30.2 │
└──────┬────────┘
│
┌──────┴──────────┐
│ │
[Camelot: Fedora 42] [Fred: Windows 11]
10.20.30.1 10.20.30.3
(LAN only) (LAN only)A classic, air-gapped architecture:
-
Annwn: 📦 A container in a sandboxed world -
Camelot: 🏰 The Proxmox host — has network + package access -
Merlin: 🧙♂️ The LAN gatekeeper
✅ Multiple connections → Camelot won’t stand alone
✅ Jumpserver8 → an entry gate, security layer, trusted access point
✅ DNS → resolving internal names for the kingdom
✅ Proxmox → hosting containers and VMs, tools as modules
✅ Toolkit container → a Swiss Army Knife, deployable scripts/utilities in one place
🏰 Merlin’s Role (currently hosted on Frodo)
✅ Runs Ansible, Terraform, or other automation tools → commanding infrastructure
✅ Controls ?? API → can spin up/down VMs, containers, manage resources
✅ Aggregates monitoring, logging, status dashboards → sees the kingdom’s health
✅ Connects from Frodo (personal laptop) → to Jumpserver8 → to Camelot → to others
✅ 🧙♂️ The wizard behind the scenes → scripting the kingdom’s will into action
🏰 Camelot as a Deployment System with no vendor lock-in
Camelot isn’t just a hypervisor.
It’s our royal command center — a deployment platform for:
-
Containers (LXC)
-
Virtual Machines (KVM)
-
Storage volumes
-
Snapshots, backups, rollbacks
-
And now: Annwn, the portable music oracle
And because it’s ours, we control the realm:
-
No cloud dependency
-
No vendor lock-in
-
No mystery meat Linux distros running somewhere else
Just pure, local, reproducible systems — with click or CLI — that we can restore from ash if needed.
Think of Camelot (TBD) as the central brain, and it needs storage and services to become useful.
🔥 Storage server: (priority shift. Using 2Tb SSD 2025-03-30)
Our Dell Unity XT (Broceliande) is a dedicated storage server.
Proxmox doesn’t get installed on Unity XT—instead, Proxmox connects to it like a ruler ruling over their kingdom. 👑
🔥 How does Proxmox access Unity XT? We need to connect Proxmox (Camelot) to Broceliande (Unity XT) using one of these methods:
🔹 iSCSI → Block storage (acts like a physical drive for Proxmox)
🔹 NFS → Shared storage for VMs & containers
🔹 SMB/CIFS → Windows-like file sharing (less common in Proxmox)
✅ Decide how Proxmox should use Unity XT—do we want it as a VM storage location, a container storage backend, or both?
ZFS Revisited
ZFS could still be useful in Proxmox if we:
🔹 Want a local Proxmox storage pool for caching or fast container storage
🔹 Need ZFS snapshots for fast rollback of VMs
🔹 Want redundancy on Proxmox’s local disks (e.g., if we’re mirroring local SSDs)
The laptop (Frodo) is now Merlin—the automation & control node for Camelot. 🧙✨
Merlin’s Role
✅ Runs Ansible, Terraform, or custom scripts to control Proxmox
✅ Manages deployments (e.g., spins up VMs & containers)
✅ Handles monitoring/logging for the entire infrastructure