starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Virtualization: include IP address in VM listing #1233

New Issue
Closed
opened 2025-12-29 16:30:26 +01:00 by adam · 0 comments
adam commented 2025-12-29 16:30:26 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Sep 15, 2017).

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: v2.2-beta1

Description

Would it be possible to find space for primary IP Address(es) in the default Virtual Machines listing?

At the moment, the Devices list shows primary IP Address(es):

Name Status Tenant Site Rack Role Type IP Address

But the Virtual Machines list does not. It shows:

Name Status Cluster Tenant vCPUs Memory (MB) Disk (GB)

Use case

  • Same as for Device: scanning listing, quickly identify primary IPv4 and/or IPv6 addresses for VM

Suggestions

One option which I'd happily accept is to trade vCPUs/Memory/Disk for IP Address (and Role - see #1493). Swapping Tenant and Cluster would also make this more consistent with Device, so it could become:

Name Status Tenant Cluster Role IP Address

That has two fewer columns than Device (i.e. Site/Rack/Type replaced by Cluster)

Hence it might be possible to add back the other columns if they are kept narrow, e.g. use label "RAM" instead of "Memory (GB)", "CPU" instead of "vCPUs"

Name Status Tenant Cluster Role CPU RAM Disk IP Address
foo.example.com Active --- lxd1 Database 2 1024 20 100.64.0.1

Or combined into one column:

Name Status Tenant Cluster Role Size IP Address
foo.example.com Active --- lxd1 Database 2 / 1024M / 20G 100.64.0.1
Originally created by @candlerb on GitHub (Sep 15, 2017). ### Issue type [X] Feature request <!-- Requesting the implementation of a new feature --> [ ] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> ### Environment * Python version: 3.5.2 * NetBox version: v2.2-beta1 ### Description Would it be possible to find space for primary IP Address(es) in the default Virtual Machines listing? At the moment, the Devices list shows primary IP Address(es): Name | Status | Tenant | Site | Rack | Role | Type | IP Address ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- But the Virtual Machines list does not. It shows: Name | Status | Cluster | Tenant | vCPUs | Memory (MB) | Disk (GB) ---- | ---- | ---- | ---- | ---- | ---- | ---- ### Use case * Same as for Device: scanning listing, quickly identify primary IPv4 and/or IPv6 addresses for VM ### Suggestions One option which I'd happily accept is to trade vCPUs/Memory/Disk for IP Address (and Role - see #1493). Swapping Tenant and Cluster would also make this more consistent with Device, so it could become: Name | Status | Tenant | Cluster | Role | IP Address ---- | ---- | ---- | ---- | ---- | ---- That has two fewer columns than Device (i.e. Site/Rack/Type replaced by Cluster) Hence it might be possible to add back the other columns if they are kept narrow, e.g. use label "RAM" instead of "Memory (GB)", "CPU" instead of "vCPUs" Name | Status | Tenant | Cluster | Role | CPU | RAM | Disk | IP Address ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- foo.example.com | Active | --- | lxd1 | Database | 2 | 1024 | 20 | 100.64.0.1 Or combined into one column: Name | Status | Tenant | Cluster | Role | Size | IP Address ---- | ---- | ---- | ---- | ---- | ---- | ---- foo.example.com | Active | --- | lxd1 | Database | 2 / 1024M / 20G | 100.64.0.1
adam added the type: feature label 2025-12-29 16:30:26 +01:00
adam closed this issue 2025-12-29 16:30:26 +01:00
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#1233
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?