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

Creating bulk VMs and Interfaces, new IP Addresses #11375

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

Originally created by @chromeronin on GitHub (Jul 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 GitHub (Jul 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_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:44:21 +01:00
adam closed this issue 2025-12-29 21:44:22 +01:00
adam commented 2025-12-29 21:44:22 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jul 14, 2025):

@chromeronin , thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jnovinger commented on GitHub (Jul 14, 2025): @chromeronin , thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 21:44:22 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 22, 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 (Jul 22, 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:44:22 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 29, 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.

@github-actions[bot] commented on GitHub (Jul 29, 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#11375
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?