Creating bulk VMs and Interfaces, new IP Addresses #1650

New Issue

MrUnknownDE · 2026-04-06T05:45:38+02:00

MrUnknownDE commented

2026-04-06 05:45:38 +02:00

Originally created by @chromeronin on 7/13/2025

NetBox version

v4.3.3

Feature type

Change to existing functionality

Proposed functionality

Using Netbox 4.3.3, just having to create a nwe environment for a customer. Overall the VM section is great apart from creating 100 or more VM entries is an absolute chore. Creating Each VM obnect, cloding it and then after creating all of those, going back and creating interfaces on each one, then going back and assigning IP addresses or creating new ones.
If creating a NEW VM, could there possibly be a tickbox to automatically create an interface object filled in with the same VM names, tenants and descriptions? Or have those for the interface automatically filled in with the parent VMs details?
When looking at the interface UI, there is only an option to create a NEW IP address, but no way in that dialog to pick a free one in the range you want, you have to go look it up. And no option thre to pick an IP address object that may have already been created, you have to go through the IP addresses UI and assign the VM interface. Creating these VMs took about 2 days to work out how everything linked together and setup a workflow to optimise adding them all in.

Use case

Improve bulk creation processes through the UI or improve default field settings to reduce chances of data entry error or missing information.

Database changes

No response

External dependencies

No response

*Originally created by @chromeronin on 7/13/2025* ### NetBox version v4.3.3 ### Feature type Change to existing functionality ### Proposed functionality Using Netbox 4.3.3, just having to create a nwe environment for a customer. Overall the VM section is great apart from creating 100 or more VM entries is an absolute chore. Creating Each VM obnect, cloding it and then after creating all of those, going back and creating interfaces on each one, then going back and assigning IP addresses or creating new ones. If creating a NEW VM, could there possibly be a tickbox to automatically create an interface object filled in with the same VM names, tenants and descriptions? Or have those for the interface automatically filled in with the parent VMs details? When looking at the interface UI, there is only an option to create a NEW IP address, but no way in that dialog to pick a free one in the range you want, you have to go look it up. And no option thre to pick an IP address object that may have already been created, you have to go through the IP addresses UI and assign the VM interface. Creating these VMs took about 2 days to work out how everything linked together and setup a workflow to optimise adding them all in. ### Use case Improve bulk creation processes through the UI or improve default field settings to reduce chances of data entry error or missing information. ### Database changes _No response_ ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-06 05:45:38 +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 pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed 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 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 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#1650