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

Change Virtualization Interfaces to not require being bound to Virtual Machines #10496

New Issue
Closed
opened 2025-12-29 21:32:15 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:32:15 +01:00
Owner
Copy Link

Originally created by @AskskwBv8T2nrm4Qnj on GitHub (Nov 20, 2024).

NetBox version

v4.1.6

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

When creating an Interface in the Netbox web-interface Virtualization section, a hard-requirement is associating said Interface with a Virtual Machine. I want to request that said requirement becomes optional rather than required.

A soft-consequence of this change would be swapping positions of the "Virtual Machine" and "Name" fields in the "Add a new interface" web-interface form, so that the only required field: "Name", would be on top of the form. In addition I suppose the same thing should happen in the "Import" page of Interfaces.

Use case

In AWS and OpenStack, Interfaces may be created without being attached to Virtual Machines. Said Interfaces are objects to which an IP-address is bound directly. The Interface object can, at any point, be attached to a Virtual Machine or detached from a Virtual Machine while keeping the associated IP-address bound to the Interface object. This maps well to the binding Netbox allows between Interfaces and IP-addresses, the only problem there being that Netbox Virtualization Interfaces require being bound to Virtual Machines...

Furthermore, in AWS and OpenStack there exist Interfaces which are never bound to "Virtual Machines", such as DHCP-agents. DHCP-agents live in a customers' subnet, while being bound to a non-Virtual Machine Interface. There are additional 'services/agents' similar to DHCP-agents, and an Interface may be in certain states such as 'Down' or 'Reserved'. To provide capability for defining such mappings, information and states, my suggestion is to loosen the requirement of having Netbox Virtualization Interfaces be bound to a Virtual Machines.

Database changes

No response

External dependencies

No response

Originally created by @AskskwBv8T2nrm4Qnj on GitHub (Nov 20, 2024). ### NetBox version v4.1.6 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality When creating an Interface in the Netbox web-interface Virtualization section, a hard-requirement is associating said Interface with a Virtual Machine. I want to request that said requirement becomes optional rather than required. A soft-consequence of this change would be swapping positions of the "Virtual Machine" and "Name" fields in the "Add a new interface" web-interface form, so that the only required field: "Name", would be on top of the form. In addition I suppose the same thing should happen in the "Import" page of Interfaces. ### Use case In AWS and OpenStack, Interfaces may be created without being attached to Virtual Machines. Said Interfaces are objects to which an IP-address is bound directly. The Interface object can, at any point, be attached to a Virtual Machine or detached from a Virtual Machine while keeping the associated IP-address bound to the Interface object. This maps well to the binding Netbox allows between Interfaces and IP-addresses, the only problem there being that Netbox Virtualization Interfaces require being bound to Virtual Machines... Furthermore, in AWS and OpenStack there exist Interfaces which are never bound to "Virtual Machines", such as DHCP-agents. DHCP-agents live in a customers' subnet, while being bound to a non-Virtual Machine Interface. There are additional 'services/agents' similar to DHCP-agents, and an Interface may be in certain states such as 'Down' or 'Reserved'. To provide capability for defining such mappings, information and states, my suggestion is to loosen the requirement of having Netbox Virtualization Interfaces be bound to a Virtual Machines. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:32:15 +01:00
adam closed this issue 2025-12-29 21:32:15 +01:00
adam commented 2025-12-29 21:32:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 20, 2024):

I'm sorry but it sounds like you're trying to use this model for something very different from its intended purpose. The proposed change is not tenable.

You might consider starting a discussion to source ideas for achieving what you're trying to do.

@jeremystretch commented on GitHub (Nov 20, 2024): I'm sorry but it sounds like you're trying to use this model for something very different from its intended purpose. The proposed change is not tenable. You might consider starting a [discussion](https://github.com/netbox-community/netbox/discussions/new?category=help-wanted) to source ideas for achieving what you're trying to do.
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 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#10496
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?