Till Wegmueller 57186ebe68 Add pod networking: IPAM, per-pod VNICs, and zone IP configuration ... Each pod now gets a unique VNIC name and IP address from a configurable CIDR pool, with IPs released on pod deletion. This replaces the hardcoded single VNIC/IP that prevented multiple pods from running. - Add redb-backed IPAM module with allocate/release/idempotent semantics - Add prefix_len to EtherstubConfig and DirectNicConfig - Generate allowed-address and defrouter in zonecfg net blocks - Wire vnic_name_for_pod() into controller for unique VNIC names - Add --pod-cidr and --etherstub-name CLI flags to agent subcommand - Add StorageError and IpamPoolExhausted error variants with diagnostics Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-02-09 00:17:45 +01:00
..
reddwarf	Add pod networking: IPAM, per-pod VNICs, and zone IP configuration	2026-02-09 00:17:45 +01:00
reddwarf-apiserver	Close the control loop: versioned bind, event-driven controller, graceful shutdown	2026-02-08 23:21:53 +01:00
reddwarf-core	Close the control loop: versioned bind, event-driven controller, graceful shutdown	2026-02-08 23:21:53 +01:00
reddwarf-runtime	Add pod networking: IPAM, per-pod VNICs, and zone IP configuration	2026-02-09 00:17:45 +01:00
reddwarf-scheduler	Close the control loop: versioned bind, event-driven controller, graceful shutdown	2026-02-08 23:21:53 +01:00
reddwarf-storage	Format code	2026-01-28 23:17:19 +01:00
reddwarf-versioning	Format code	2026-01-28 23:17:19 +01:00