https://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-fabric/Recent content in Tenant Fabric on Deevnet IoTaaSHugoen-ushttps://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-fabric/plan/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-fabric/plan/<h1 id="tenant-fabric-project-plan"> Tenant Fabric: Project Plan <a class="anchor" href="#tenant-fabric-project-plan">#</a> </h1> <p>The network tenants run on, from its architecture to DNS publication, one of three plans for the tenant platform with <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-lifecycle/plan/">Tenant Lifecycle</a> and <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/roadmap/infrastructure/tenant-services/platform-services/plan/">Tenant Platform Services</a>.</p> <p><strong>Roadmap item:</strong> <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-fabric/">Tenant Fabric</a></p> <div class="progress-container"> <div class="progress-bar"><div class="progress-segment-completed" style="width: 88.88888888888889%;" title="8 completed"></div><div class="progress-segment-planned" style="width: 11.11111111111111%;" title="1 planned"></div></div> <div class="progress-legend"> <span class="progress-legend-completed">&#x2713; 8</span> | <span class="progress-legend-in-progress">&#x21bb; 0</span> | <span class="progress-legend-planned">&#x23f3; 1</span> (9 total) </div> </div> <p><strong>Legend:</strong> ✅ Complete | 🔄 In Progress | ⏳ Planned</p> <hr> <h2 id="design-tenant-network-architecture-"> Design tenant network architecture ✅ <a class="anchor" href="#design-tenant-network-architecture-">#</a> </h2> <p>How tenant traffic is isolated, routed, and addressed.</p> <ul> <li><strong>Decided:</strong> the fabric model — an EVPN overlay owned by the tenant compute domain, self-contained per hypervisor, single-member now and expandable to a cluster ( <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/architecture/decisions/tenant-networking/0001-tenant-network-fabric/">ADR-0001</a>).</li> <li><strong>Decided:</strong> the numbering scheme — the site <code>/16</code> split so tenant overlays live at <code>10.20.128.0/18</code> and fabric loopbacks at <code>10.20.255.0/24</code>, with every tenant identifier derived from a single allocated index ( <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/architecture/decisions/tenant-networking/0002-tenant-fabric-numbering/">ADR-0002</a>).</li> <li><strong>Deferred — DNS:</strong> how tenant records are authored and published into the substrate zone is still undecided, and is tracked as its own thread below rather than holding this milestone open. Proxmox&rsquo;s SDN DNS integration targets a PowerDNS API; the core router runs Unbound, so it does not fit as-is.</li> </ul> <hr> <h2 id="build-the-tenant-fabric-phase-1-"> Build the tenant fabric (Phase 1) 🔄 <a class="anchor" href="#build-the-tenant-fabric-phase-1-">#</a> </h2> <p>Stand up the single-member fabric on dv02hyp002p02.</p>