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

Ability to assign IP address to virtualization/clusters/[entity] #2858

New Issue
Closed
opened 2025-12-29 18:22:51 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:22:51 +01:00
Owner
Copy Link

Originally created by @kdhlab on GitHub (Sep 5, 2019).

Environment

  • Python version: 3.6.6
  • NetBox version: v2.6.2

Proposed Functionality

I would like the ability to assign IP addresses and virtual interfaces to a virtual cluster.

Use Case

Some virtualization environments, such as Nutanix AHV have a cluster management IP on a virtual interface that is floating across the cluster members. I would like to be able to add the IP of the cluster to the cluster object itself. Currently as a work-around I am just assigning the IP with the cluster name in the description which does not actually associate it with the cluster which does not model the cluster accurately.

Utilizing virtual chassis does not model this correctly either since there is no Master in a virtualization cluster and the members are still distinct entities with distinct interfaces.

Database Changes

N/A

External Dependencies

N/A

Originally created by @kdhlab on GitHub (Sep 5, 2019). ### Environment * Python version: 3.6.6 * NetBox version: v2.6.2 ### Proposed Functionality I would like the ability to assign IP addresses and virtual interfaces to a virtual cluster. ### Use Case Some virtualization environments, such as Nutanix AHV have a cluster management IP on a virtual interface that is floating across the cluster members. I would like to be able to add the IP of the cluster to the cluster object itself. Currently as a work-around I am just assigning the IP with the cluster name in the description which does not actually associate it with the cluster which does not model the cluster accurately. Utilizing virtual chassis does not model this correctly either since there is no Master in a virtualization cluster and the members are still distinct entities with distinct interfaces. ### Database Changes N/A ### External Dependencies N/A
adam closed this issue 2025-12-29 18:22:51 +01:00
adam commented 2025-12-29 18:22:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 6, 2019):

This might partially be addressed by #2456, but we won't be making any modifications to the IP model beyond that due to development constraints.

@jeremystretch commented on GitHub (Sep 6, 2019): This might partially be addressed by #2456, but we won't be making any modifications to the IP model beyond that due to development constraints.
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
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#2858
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?