https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/management-plane/Recent content in Management Plane on Deevnet Infrastructure PlatformHugoen-ushttps://deevnet.github.io/deevnet-docs/docs/architecture/substrate/management-plane/core-services/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/management-plane/core-services/<h1 id="core-services-architecture"> Core Services Architecture <a class="anchor" href="#core-services-architecture">#</a> </h1> <h3 id="purpose"> Purpose <a class="anchor" href="#purpose">#</a> </h3> <p>This document defines the <strong>foundational platform services</strong> of the management plane—DNS, DHCP, NAT, routing, firewall, and the naming/authority model that underpins all substrate operations.</p> <p>These services must remain operational even if all extended services are lost.</p> <p>For the builder that provisions these services, see <a href="https://deevnet.github.io/deevnet-docs/docs/architecture/builder/">Builder</a>.</p> <hr> <h2 id="1-core-services"> 1. Core Services <a class="anchor" href="#1-core-services">#</a> </h2> <p>The Core Services provides foundational management services:</p> <table> <thead> <tr> <th>Service</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td><strong>DNS</strong></td> <td>Authoritative for substrate zones, forwarding for external</td> </tr> <tr> <td><strong>DHCP</strong></td> <td>Static mappings for known hosts, dynamic pools</td> </tr> <tr> <td><strong>NAT</strong></td> <td>Outbound gateway for all segments</td> </tr> <tr> <td><strong>Routing</strong></td> <td>Inter-segment and gateway routing</td> </tr> <tr> <td><strong>Firewall</strong></td> <td>Inter-segment and egress rules</td> </tr> </tbody> </table> <p>In production, these services are provided by dedicated network infrastructure. The <a href="https://deevnet.github.io/deevnet-docs/docs/architecture/builder/">Builder</a> complements with provisioning, artifact hosting, and PXE/TFTP services.</p>https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/management-plane/extended-services/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/architecture/substrate/management-plane/extended-services/<h1 id="extended-services-architecture"> Extended Services Architecture <a class="anchor" href="#extended-services-architecture">#</a> </h1> <h3 id="purpose"> Purpose <a class="anchor" href="#purpose">#</a> </h3> <p>This document defines the <strong>extended management services</strong> layer within the Deevnet management plane.</p> <p>Extended management services provide observability, automation, and access tooling. They are <strong>additive</strong> to <a href="../core-services/">Core Services</a>—the minimal set of services required for the substrate to function on its own.</p> <p>These services may be rebuilt entirely from the builder and core services. If the extended services tier is lost, core provisioning and network services remain operational.</p>