LoginSign Up
← Back to all sparks
N

NetBox

INFRA · APIS
Velocity6.3

Infrastructure resource modeling and IPAM source of truth

netboxlabs.com ↗

NetBox adds a cooling data model — the first new infrastructure domain since power

dcimcoolingliquid-coolingbreaking-changespostgresqlgraphql
◆Current state
After a 4.6 patch cycle spent almost entirely on GraphQL query cost and permission correctness, NetBox has opened its 4.7 line with a beta that is the opposite kind of release. It introduces cooling infrastructure as a first-class modeling domain, migrates nested group models off django-mptt onto a PostgreSQL ltree column, replaces the Service protocol/ports fields with a unified port_mappings structure, and raises the floor to PostgreSQL 15 and Redis 6. The breaking-change list runs longer than most NetBox releases run in total.
◆Where it's heading
The cooling model is deliberately shaped as a mirror of the existing power model — CoolingSource and CoolingFeed parallel PowerPanel and PowerFeed, CoolingIntake and CoolingOutflow parallel PowerPort and PowerOutlet, with CDUs and manifolds modeled as ordinary devices carrying those components. That symmetry says NetBox intends liquid cooling to be documented with the same rigor as power distribution, not bolted on as attributes. Underneath it, the ltree migration and the deferred search-index rebuild continue the performance thread of 4.6 by other means: instead of trimming queries inside the ORM, 4.7 is changing what the ORM sits on.
◆Prediction
Expect at least one more 4.7 beta or release candidate before general availability, with the deprecated NestedGroupModel base class and the retained protocol/ports API fields the most likely sources of follow-up fixes as plugins migrate.

◆Recent moves

  1. 1d ago

    NetBox 4.7 beta models cooling plant the way it models power

    ⚡ SPARK

    This breaks the 4.6 pattern completely. Where every recent release trimmed GraphQL queries and tightened permissions, 4.7.0-beta1 adds an entire modeling domain and rewrites the foundations under nested groups, alongside a breaking-change list that drops PostgreSQL 14, drops Redis 5, and turns Service protocol and ports into read-only derivations of a new port_mappings field.

    View source ↗
  2. 7d ago

    GraphQL N+1 fixes and permission corrections in 4.6.8

    A pure maintenance patch with no enhancements section — four performance fixes, three of them GraphQL, plus eleven bug fixes. The N+1 fix for generic relations and the prefetch pagination fix are the same query-cost thread that has run through every 4.6 patch.

    View source ↗
  3. 15d ago

    4.6.8 release candidate refreshes translation strings

    A release candidate whose entire changelog is a translation-string refresh. Nothing here reaches users.

    View source ↗
  4. 19d ago

    4.6.7 trims GraphQL and scope-rebuild query overhead

    Four performance fixes, three of them cutting extraneous database queries in the GraphQL layer, plus a cached scope-rebuild skip for sites and locations. Two bug fixes, one correcting IP availability for permission-constrained users.

    View source ↗
  5. 21d ago

    Cluster-scoped VLANs, tag "any" lookup, audit-trail hardening

    The most substantial patch in this window: cluster-scoped VLAN selection on interfaces, colored custom-field choice badges, an "any" tag lookup, and a header-sanitizing Jinja2 filter. Two security-adjacent fixes stand out — immutable journal-entry authorship to block audit-trail spoofing, and redacted filesystem paths in debug tracebacks.

    View source ↗
  6. 1mo ago

    MDC connectors, script-module REST updates, Korean support

    Adds an MDC fiber connector type, a REST method for overwriting custom script modules, and Korean language support. The bug list is long and mostly REST and OpenAPI schema correctness — the kind of accumulation that follows a major API expansion.

    View source ↗