starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Module type profile filter on module bays #11155

New Issue
Closed
opened 2025-12-29 21:41:06 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:41:06 +01:00
Owner
Copy Link

Originally created by @ananace on GitHub (May 10, 2025).

NetBox version

v4.3.0

Feature type

Data model extension

Proposed functionality

With the added Module Type Profile functionality in 4.3.0, it'd be nice to also have a way to set filters for acceptable module types on module bays, like limiting a Power Supply bay to only allowing Module Types that have the Module Type Profile "Power supply".

Use case

With the improved module functionality, the list of available module types is starting to grow exponentially in our systems, and that makes it cumbersome to select the correct modules for certain bays.
Having a filter in place so that the UI/API can make better decisions on what to show/allow when attaching would improve the user experience tremendously.

Database changes

Will likely require adding a filter column to the dcim_modulebay[template] tables

External dependencies

No response

Originally created by @ananace on GitHub (May 10, 2025). ### NetBox version v4.3.0 ### Feature type Data model extension ### Proposed functionality With the added Module Type Profile functionality in 4.3.0, it'd be nice to also have a way to set filters for acceptable module types on module bays, like limiting a Power Supply bay to only allowing Module Types that have the Module Type Profile "Power supply". ### Use case With the improved module functionality, the list of available module types is starting to grow exponentially in our systems, and that makes it cumbersome to select the correct modules for certain bays. Having a filter in place so that the UI/API can make better decisions on what to show/allow when attaching would improve the user experience tremendously. ### Database changes Will likely require adding a filter column to the dcim_modulebay[template] tables ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:41:06 +01:00
adam closed this issue 2025-12-29 21:41:06 +01:00
adam commented 2025-12-29 21:41:07 +01:00
Author
Owner
Copy Link

@neuro42 commented on GitHub (May 12, 2025):

This quickly gets more complicated -- take the example default of a Memory module, that has 3 different classes of RAM, all of which have a different connector. It's not possible to put DDR3 ram in a DDR4 slot, so ideally the module bays can also check against the extra attributes of the module type. You have a similar thing involving the connectors of all the module types (cpu sockets, disk connectors, card slots....) and it would be really nice from a UX perspective that only things that can actually plug in are listed.

@neuro42 commented on GitHub (May 12, 2025): This quickly gets more complicated -- take the example default of a Memory module, that has 3 different classes of RAM, all of which have a different connector. It's not possible to put DDR3 ram in a DDR4 slot, so ideally the module bays can also check against the extra attributes of the module type. You have a similar thing involving the connectors of all the module types (cpu sockets, disk connectors, card slots....) and it would be really nice from a UX perspective that only things that can actually plug in are listed.
adam commented 2025-12-29 21:41:07 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (May 15, 2025):

This is potentially a good idea but we need to flesh out the specs of this FR considerably.

@bctiemann commented on GitHub (May 15, 2025): This is potentially a good idea but we need to flesh out the specs of this FR considerably.
adam commented 2025-12-29 21:41:07 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 23, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (May 23, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:41:07 +01:00
Author
Owner
Copy Link

@neuro42 commented on GitHub (May 23, 2025):

As spec'd would be the first step towards this. Once the types are done, then the more detailed interactions can be added. Right now you get every module in the system to pick from. Matching on types makes it much smaller, and then matching on the details of those types would make it smaller still.

@neuro42 commented on GitHub (May 23, 2025): As spec'd would be the first step towards this. Once the types are done, then the more detailed interactions can be added. Right now you get every module in the system to pick from. Matching on types makes it much smaller, and then matching on the details of those types would make it smaller still.
adam commented 2025-12-29 21:41:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 2, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Jun 2, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure status: revisions needed type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11155
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?