Enable recursive nesting for platforms

[0lini]

NetBox version

v4.3.2

Feature type

Data model extension

Proposed functionality

I would like to propose a new feature to extend the Platform model in NetBox to support multiple associated versions. This would allow tracking specific software or firmware versions for each platform, creating a 1:N relationship where:
• One Platform can have multiple PlatformVersion entries
• Each PlatformVersion would store version metadata (e.g., version string, release date, etc.)

Use case

Managing network infrastructure often involves not just knowing what platform a device runs on (e.g., Cisco IOS, Juniper JunOS, Arista EOS), but also which version of that platform is in use. Platform versions can significantly impact:
• Feature availability
• Configuration syntax
• Security vulnerabilities
• Lifecycle status (EoL/EoS)

Currently, NetBox allows setting the platform for a device, but does not support tracking version information in a structured and reusable way.

By introducing a PlatformVersion model, NetBox users would gain the ability to:
• Associate specific software/firmware versions with a platform
• Enforce consistency across devices using the same version
• Query all devices running a given version of a platform
• Integrate version data into config management workflows and compliance reports
• Avoid repeated entry of version strings or messy freeform notes/custom fields

This is especially beneficial in environments with:
• Strict change control and upgrade procedures
• Vulnerability management requirements (e.g., CVE patching)
• Automated configuration templates that vary based on software version

Ultimately, this feature would enable better data integrity, auditing, and automation across device lifecycle and configuration management processes.

Database changes

This feature would require the addition of a new model, PlatformVersion, to support a one-to-many relationship between Platform and its associated versions.

External dependencies

No response

[jnovinger]

Per the Platform model documentation:

A platform defines the type of software running on a device or virtual machine. This can be helpful to model when it is necessary to distinguish between different versions or feature sets. Note that two devices of the same type may be assigned different platforms: For example, one Juniper MX240 might run Junos 14 while another runs Junos 15.

There are a few ways this could be tackled given the tools already in NetBox: tags, custom fields, or even a plugin.

[jeremystretch]

This has been proposed in the past, and the sticking point was that declaring a specific release for each platform could force too much granularity on the user. For example, the user might want to differentiate between major releases of an OS, but not between patch releases.

Maybe we could take the same approach here as in #18245, by implementing the ability to nest platforms recursively. This would allow users to declare e.g. Cisco IOS 15 at the root level, with versions 15.1, 15.2, and so on beneath it.

[rcon-git]

Maybe we could take the same approach here as in #18245, by implementing the ability to nest platforms recursively. This would allow users to declare e.g. Cisco IOS 15 at the root level, with versions 15.1, 15.2, and so on beneath it.

I like this approach, but why make the root "Cisco IOS 15"? The root could just be "Cisco IOS", or "Cisco IOS-XE", or "Cisco IOS-XR" then just have nested major and minor versions underneath that.

[jeremystretch]

It was just an example for illustration. You could arrange the hierarchy into as many tiers as makes sense for your use case.

[0lini]

Jup, a hierarchical structure would work for this.