https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/Recent content in Substrate on Deevnet Infrastructure PlatformHugoen-ushttps://deevnet.github.io/deevnet-docs/docs/architecture/substrate/networking/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/networking/<h1 id="substrate-networking-services"> Substrate Networking Services <a class="anchor" href="#substrate-networking-services">#</a> </h1> <p>The substrate networking layer provides foundational network services for each site. The core router serves as the segment router, firewall, and service gateway for all segments within a substrate.</p> <p>For the segment model (nine segment types, trust hierarchy, and routing policy), see <a href="https://deevnet.github.io/deevnet-docs/docs/architecture/network-segmentation/">Network Segmentation</a>.</p> <hr> <h2 id="core-router-role"> Core Router Role <a class="anchor" href="#core-router-role">#</a> </h2> <p>Each substrate has a single core router that provides all networking services:</p> <table> <thead> <tr> <th>Function</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td>Segment routing</td> <td>Inter-segment routing via VLAN interfaces</td> </tr> <tr> <td>Firewall</td> <td>Zone-based policy enforcement per segment</td> </tr> <tr> <td>DNS</td> <td>Authoritative for substrate zone, forwarding for external</td> </tr> <tr> <td>DHCP</td> <td>Static mappings for known hosts, dynamic pools per segment</td> </tr> <tr> <td>NAT</td> <td>Outbound gateway for all segments</td> </tr> <tr> <td>Switching integration</td> <td>VLAN trunking to access switch</td> </tr> <tr> <td>Wireless integration</td> <td>SSID-to-VLAN mapping via wireless AP</td> </tr> </tbody> </table> <hr> <h2 id="vlan-routing"> VLAN Routing <a class="anchor" href="#vlan-routing">#</a> </h2> <p>The core router maintains one interface per segment, each on its own VLAN:</p>https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/compute/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/compute/<h1 id="substrate-compute"> Substrate Compute <a class="anchor" href="#substrate-compute">#</a> </h1> <p>Defines the virtualization and compute model for Deevnet sites.</p> <hr> <h2 id="overview"> Overview <a class="anchor" href="#overview">#</a> </h2> <p>Compute infrastructure provides virtualization hosts for management-plane and tenant workloads. Hypervisors run within the substrate and host:</p> <ul> <li><strong>Extended services</strong> — Observability, automation, and access tooling VMs</li> <li><strong>Tenant application VMs</strong> — Workloads deployed by tenants</li> </ul> <hr> <h2 id="compute-hosts"> Compute Hosts <a class="anchor" href="#compute-hosts">#</a> </h2> <p>Each site includes one or more hypervisors that provide the virtualization layer. Compute hosts are provisioned through the builder and managed via the management plane.</p>https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/storage/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/storage/<h1 id="substrate-storage"> Substrate Storage <a class="anchor" href="#substrate-storage">#</a> </h1> <p>Defines the shared and persistent storage model for Deevnet sites.</p> <hr> <h2 id="status"> Status <a class="anchor" href="#status">#</a> </h2> <p>Storage is a <strong>planned future addition</strong> to core services. This document will be expanded as the storage architecture is defined.</p> <hr> <h2 id="intent"> Intent <a class="anchor" href="#intent">#</a> </h2> <p>Shared storage will provide persistent volumes for substrate consumers — both management-plane services and tenant workloads — independent of any single compute host.</p>