Basic Module Compatibility "Form Factor" #7749

Closed
opened 2025-12-29 20:27:47 +01:00 by adam · 2 comments
Owner

Originally created by @Nealtron on GitHub (Mar 12, 2023).

NetBox version

v3.4.4

Feature type

New functionality

Proposed functionality

Create a new data point for both device module slots and modules that would could be used to filter compatible modules based on form factor.

I understand that this can get wildly complicated, but I'd recommend limiting this iteration to some form of field or tag matching.

Use case

To filter out incompatible devices when attempting to assign a module to a device, especially when that device uses an industry standard spot and accepts modules form many manufacturers.

Ex1: Prevents an SFP from being "installed" into a PSU slot.
Ex2: Makes it easier to find all compatible LGX fiber optic modules that are manufactured by dozens of companies.

Database changes

No response

External dependencies

No response

Originally created by @Nealtron on GitHub (Mar 12, 2023). ### NetBox version v3.4.4 ### Feature type New functionality ### Proposed functionality Create a new data point for both device module slots and modules that would could be used to filter compatible modules based on form factor. I understand that this can get wildly complicated, but I'd recommend limiting this iteration to some form of field or tag matching. ### Use case To filter out incompatible devices when attempting to assign a module to a device, especially when that device uses an industry standard spot and accepts modules form many manufacturers. Ex1: Prevents an SFP from being "installed" into a PSU slot. Ex2: Makes it easier to find all compatible LGX fiber optic modules that are manufactured by dozens of companies. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:27:47 +01:00
adam closed this issue 2025-12-29 20:27:47 +01:00
Author
Owner

@jeremystretch commented on GitHub (Mar 16, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Mar 16, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
Author
Owner

@jeremystretch commented on GitHub (Apr 4, 2023):

Closing this as there's been no further response from OP.

@jeremystretch commented on GitHub (Apr 4, 2023): Closing this as there's been no further response from OP.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7749