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

Add "device template" function for device types that uses module types #7763

New Issue
Closed
opened 2025-12-29 20:27:55 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:27:55 +01:00
Owner
Copy Link

Originally created by @muppaduppa on GitHub (Mar 16, 2023).

NetBox version

v3.4.6

Feature type

New functionality

Proposed functionality

Add a device template function. Device template would exist of a device type and a set of module types that that device types uses that are predefined.

As an example a device type could have 10 module bays. But standard device that gets deployed, always has a specific line card in one bay/power supply in one bay/Route Proccessor in the same bay and so on.
Example picture below
image
This standard device would be saved as an device template that you can add/remove/edit as with other device functions.

When adding a new device in UI you would then use this device template and have the standard device added with the correct set of modules directly. Instead of adding device and then add modules one by one.

You could create this standard device today as a device type but then you would loose the ability to change modules and if you need to change something you would need to delete/add device again.

Use case

Would save alot of time when adding new devices in UI and reduce errors when creating a new device. Instead of adding the device and then adding modules to the right bay this would be defined in device template.

Database changes

"Device template" need to be stored in database

External dependencies

none

Originally created by @muppaduppa on GitHub (Mar 16, 2023). ### NetBox version v3.4.6 ### Feature type New functionality ### Proposed functionality Add a device template function. Device template would exist of a device type and a set of module types that that device types uses that are predefined. As an example a device type could have 10 module bays. But standard device that gets deployed, always has a specific line card in one bay/power supply in one bay/Route Proccessor in the same bay and so on. Example picture below <img width="1005" alt="image" src="https://user-images.githubusercontent.com/26269494/225542637-d5490d9d-9e4b-4a63-9af3-ebc737047e0d.png"> This standard device would be saved as an device template that you can add/remove/edit as with other device functions. When adding a new device in UI you would then use this device template and have the standard device added with the correct set of modules directly. Instead of adding device and then add modules one by one. You could create this standard device today as a device type but then you would loose the ability to change modules and if you need to change something you would need to delete/add device again. ### Use case Would save alot of time when adding new devices in UI and reduce errors when creating a new device. Instead of adding the device and then adding modules to the right bay this would be defined in device template. ### Database changes "Device template" need to be stored in database ### External dependencies none
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:27:56 +01:00
adam closed this issue 2025-12-29 20:27:56 +01:00
adam commented 2025-12-29 20:27:57 +01:00
Author
Owner
Copy Link

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

This sounds like a subset of the "deployment template" functionality proposed back in #1364. It's something worth exploring further, but needs a lot more detail around the proposed implementation. @muppaduppa would you like to flesh this out some?

@jeremystretch commented on GitHub (May 4, 2023): This sounds like a subset of the "deployment template" functionality proposed back in #1364. It's something worth exploring further, but needs a lot more detail around the proposed implementation. @muppaduppa would you like to flesh this out some?
adam commented 2025-12-29 20:27:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 25, 2023):

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 (May 25, 2023): 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 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#7763
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?