Kea first pass

.agent/memory-bank/activeContext.md

@@ -0,0 +1 @@
+Active context placeholder

.agent/memory-bank/productContext.md

@@ -0,0 +1 @@
+Product context placeholder

.agent/memory-bank/progress.md

@@ -0,0 +1 @@
+Progress placeholder

.agent/memory-bank/projectbrief.md

@@ -0,0 +1 @@
+DCops Memory Bank initialized on $(date)

.agent/memory-bank/systemPatterns.md

@@ -0,0 +1 @@
+System patterns placeholder

.agent/memory-bank/techContext.md

@@ -0,0 +1 @@
+Tech context placeholder

.agent/session.log

@@ -0,0 +1,14 @@
+
+
+========================================
+SESSION START: 2025-12-28 17:42:54
+========================================
+Project: DCops
+User: casibbald
+Shell: /bin/zsh
+Working Directory: /Users/casibbald/Workspace/microscaler/DCops
+Git Branch: main
+Git Status: 3 uncommitted changes
+Memory Bank Status: COMPLETE
+========================================
+

.gitignore

@@ -28,3 +28,5 @@ __pycache__/
 *.pyc
 
 reconciliation-differences.txt
+.nfs.*
+._*

AGENT.md → AGENTS.md

@@ -1,5 +1,38 @@
 # Agent Development Guidelines
 
+> **Desktop dev environment** — before doing anything in this repo, read the
+> Microscaler-wide topology brief. It explains that you are on a Mac but the
+> code lives on `ms02` (NFS), where commands execute for this environment, how
+> the Kind cluster and vLLM fit in, and the network constraints behind the SSH
+> tunneling. Do not duplicate its contents here — link to it. If reality drifts,
+> fix the canonical doc, not this copy.
+>
+> - GitHub: [`cylon-local-infra/docs/desktop-dev-environment.md`](https://github.com/microscaler/cylon-local-infra/blob/main/docs/desktop-dev-environment.md)
+> - On ms02 NFS: `~/Workspace/microscaler/cylon-local-infra/docs/desktop-dev-environment.md`
+
+---
+
+## Shared Kind cluster (local dev)
+
+DCops deploys to the **shared** Kind cluster (`kind-kind`), not a dedicated `kind-dcops` cluster.
+
+| Item | Value |
+|------|-------|
+| Cluster | `kind` → context **`kind-kind`** |
+| Registry | **`kind-registry`** on **`localhost:5001`** |
+| Prerequisite repo | **`../shared-kind-cluster`** — `just cluster-create` or `just dev-up` |
+| DCops namespaces | **`netbox`**, **`dcops-system`** |
+| Tilt UI port | **10354** (`tilt-dcops.service`) |
+| NetBox UI (Tilt forward) | **http://localhost:8011** |
+| Kea Control Agent (Tilt forward) | **http://localhost:8010** |
+| PXE HTTP (Tilt forward) | **http://localhost:8088** |
+
+**Workflow:** `just verify-shared-kind` → `just dev-up` (or `just tilt-up`). **`just dev-down`** stops Tilt only — it does **not** delete the shared cluster.
+
+Override checkout layout: `SHARED_KIND_CLUSTER_ROOT=/path/to/shared-kind-cluster`.
+
+---
+
 This document provides specific guidance for AI agents working on the DCops codebase, with **explicit modularization requirements** from the start.
 
 ## 🚨 CRITICAL: Check for Existing Helpers/Traits First

Cargo.toml

@@ -3,6 +3,7 @@ members = [
     "controllers/pxe-intent",
     "controllers/netbox",
     "controllers/routeros",
+    "controllers/dhcp",
     "crates/netbox-client",
     "crates/routeros-client",
     "crates/pxe-server",

README.md

@@ -41,6 +41,12 @@ DCops is a set of Kubernetes controllers that manage your physical infrastructur
 - Prevent infinite boot loops and accidental reinstallations
 - Safe cluster rebuilds without manual intervention
 
+**📡 DHCP-managed leases (Kea)**
+- Translate NetBox IP ranges and addresses into ISC Kea DHCP config
+- MAC-keyed host reservations for stable leases — powers the Aether hypervisor's
+  "recover a VM, keep its IP" story ([contract](docs/AETHER_DCOPS_IPAM_CONTRACT.md))
+- Populated ranges are managed by Kea, not tracked as individual NetBox IPs
+
 **📊 Single Source of Truth**
 - Git is your source of truth
 - NetBox is your authoritative database
@@ -154,8 +160,10 @@ The easiest way to get started with DCops development is using our pre-configure
 
 **What's Included:**
 - ✅ Full Rust toolchain (stable, rustfmt, clippy, musl target)
-- ✅ Docker-in-Docker for building images and running Kind clusters
-- ✅ Kubernetes tools (kubectl, kind, Tilt)
+- ✅ Docker-in-Docker for building images
+- ✅ Kubernetes tools (kubectl, Tilt) — DCops deploys to a shared **k3s** cluster
+  (`shared-k8s`), driven by the [`Tiltfile`](./Tiltfile); the older Kind setup has
+  been removed
 - ✅ Python 3 for project scripts
 - ✅ Development tools (Just, cargo-nextest, cargo-llvm-cov, cargo-audit)
 
@@ -165,12 +173,14 @@ The easiest way to get started with DCops development is using our pre-configure
 If you prefer a local development environment, ensure you have:
 - Rust toolchain (see `rust-toolchain.toml`)
 - Docker Desktop
-- kubectl, kind, and Tilt installed
+- kubectl and Tilt installed (NetBox runs against the shared cluster's Postgres/Redis in the `data` namespace)
 - Python 3 for running project scripts
 
 ## Learn More
 
 - **Contributing**: [CONTRIBUTING.md](CONTRIBUTING.md)
+- **Aether hypervisor integration** (MAC-keyed DHCP reservations, populated ranges): [docs/AETHER_DCOPS_IPAM_CONTRACT.md](docs/AETHER_DCOPS_IPAM_CONTRACT.md)
+- **Populated IP range handling** (NetBox constraint + implemented fix): [docs/NETBOX_IP_RANGE_ANALYSIS.md](docs/NETBOX_IP_RANGE_ANALYSIS.md)
 
 ---