Autocreate device based on Rack Type config #761

New Issue

MrUnknownDE · 2026-04-05T17:29:39+02:00

MrUnknownDE commented

2026-04-05 17:29:39 +02:00

Originally created by @lschnetl on 12/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 12/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_

MrUnknownDE closed this issue

2026-04-05 17:29:39 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#761