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

Autocreate device based on Rack Type config #11910

New Issue
Closed
opened 2025-12-29 21:51:25 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:51:25 +01:00
Owner
Copy Link

Originally created by @lschnetl on GitHub (Dec 8, 2025).

NetBox version

v4.4.7

Feature type

Data model extension

Proposed functionality

Some racks are repeatable and always get built in a the same way. This means that we could assume that when we create a new rack, certain key devices will need to be added to the device

So if we have a rack of xy, then we can assume it contains a cisco switch on the first slot, computers on 22 - 33, etc.

It would be good if we can have a similar approach to how device types and module types has extra ports/slots on them whereby a device can be slotted. Then we can automatically create the new device from the template.

Right now, the only good way for us to achieve something like this, is having a json file separate and run a custom script to create the devices based on what we specify,

I'm open to other good suggestions

Use case

We build 12x of the same rack that needs to go into production.

Ahead of time we don't have all the information (like hostname or IPs), but we do know we plan to buy specific equipment for the racks.

We can specifiy what it would look like for one "Template" rack and then multiply it 15x. If we set the rack status to planned, the devices can also be set to planned (since they are part of the rack).

Our planning/provisioning team can apply the needed IPs and Hostnames as needed and once the racks are rolled out onto the floor, we can provision them as required

Database changes

Not 100% sure, but it would require the rack object to contain a template section

External dependencies

No response

Originally created by @lschnetl on GitHub (Dec 8, 2025). ### NetBox version v4.4.7 ### Feature type Data model extension ### Proposed functionality Some racks are repeatable and always get built in a the same way. This means that we could assume that when we create a new rack, certain key devices will need to be added to the device So if we have a rack of xy, then we can assume it contains a cisco switch on the first slot, computers on 22 - 33, etc. It would be good if we can have a similar approach to how device types and module types has extra ports/slots on them whereby a device can be slotted. Then we can automatically create the new device from the template. Right now, the only good way for us to achieve something like this, is having a json file separate and run a custom script to create the devices based on what we specify, I'm open to other good suggestions ### Use case We build 12x of the same rack that needs to go into production. Ahead of time we don't have all the information (like hostname or IPs), but we do know we plan to buy specific equipment for the racks. We can specifiy what it would look like for one "Template" rack and then multiply it 15x. If we set the rack status to planned, the devices can also be set to planned (since they are part of the rack). Our planning/provisioning team can apply the needed IPs and Hostnames as needed and once the racks are rolled out onto the floor, we can provision them as required ### Database changes Not 100% sure, but it would require the rack object to contain a template section ### External dependencies _No response_
adam added the type: featurenetbox labels 2025-12-29 21:51:25 +01:00
adam closed this issue 2025-12-29 21:51:25 +01:00
adam commented 2025-12-29 21:51:26 +01:00
Author
Owner
Copy Link

@mrmrcoleman commented on GitHub (Dec 9, 2025):

@lschnetl We are announcing a new feature this week, called NetBox Designs, which addresses this use case directly. Please keep an eye on the blog

@mrmrcoleman commented on GitHub (Dec 9, 2025): @lschnetl We are announcing a new feature this week, called NetBox Designs, which addresses this use case directly. Please keep an eye on the [blog](https://netboxlabs.com/blog/)
adam commented 2025-12-29 21:51:26 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Dec 11, 2025):

As per Mark's response above, this will be addressed in NetBox Designs. Please see this blog post.

@arthanson commented on GitHub (Dec 11, 2025): As per Mark's response above, this will be addressed in NetBox Designs. Please see [this blog](https://netboxlabs.com/blog/netbox-designs-introducing-declarative-infrastructure/) post.
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 netbox 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#11910
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?