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

"Nested" clusters #1571

New Issue
Closed
opened 2025-12-29 16:33:05 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:33:05 +01:00
Owner
Copy Link

Originally created by @darkstar on GitHub (Feb 26, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.2.10

Description

We are using lots of virtualized clusters (e.g. for test/dev) in our environment and it would be nice to be able to represent them in NetBox. Currently, a NetBox cluster can consist only of (physical) devices. We weould like to be able to create a cluster from VMs running in a different cluster.

Example use cases:

  • A physical cluster of ESX hosts, running VMs that make up a Kubernetes cluster
  • A physical cluster of ESX hosts, running VMs that make up a virtual Hyper-V cluster (for test/dev)
  • etc...

Bonus points if physical/virtual cluster members can be mixed, although that is not really necessary in our use-case.

This would (obviously) need a schema change in the database, so that clusters can consist of VMs in addition to devices. Also, a new view (or a new tab in the existing "create cluster" view) is needed, to be able to select VMs instead of devices. Other than that, no radical changes should be necessary.

Originally created by @darkstar on GitHub (Feb 26, 2018). ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) If you are submitting a bug report and have made any changes to the code base, please first validate that your bug can be recreated while running an official release. --> ### Environment * Python version: 3.5.2 * NetBox version: 2.2.10 <!-- BUG REPORTS must include: * A list of the steps needed for someone else to reproduce the bug * A description of the expected and observed behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description We are using lots of virtualized clusters (e.g. for test/dev) in our environment and it would be nice to be able to represent them in NetBox. Currently, a NetBox cluster can consist only of (physical) devices. We weould like to be able to create a cluster from VMs running in a different cluster. Example use cases: * A physical cluster of ESX hosts, running VMs that make up a Kubernetes cluster * A physical cluster of ESX hosts, running VMs that make up a virtual Hyper-V cluster (for test/dev) * etc... Bonus points if physical/virtual cluster members can be mixed, although that is not really necessary in our use-case. This would (obviously) need a schema change in the database, so that clusters can consist of VMs in addition to devices. Also, a new view (or a new tab in the existing "create cluster" view) is needed, to be able to select VMs instead of devices. Other than that, no radical changes should be necessary.
adam closed this issue 2025-12-29 16:33:05 +01:00
adam commented 2025-12-29 16:33:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 26, 2018):

This was discussed in #142 when virtualization support was first being developed. It was decided not to pursue nested clustering both because would greatly complicate the data model, and because orchestration of virtual machines is a bit outside NetBox's scope. You can still create one cluster for VMs and another cluster for containers running on those VMs; you just can't explicitly map one to the other.

@jeremystretch commented on GitHub (Feb 26, 2018): This was discussed in #142 when virtualization support was first being developed. It was decided not to pursue nested clustering both because would greatly complicate the data model, and because orchestration of virtual machines is a bit outside NetBox's scope. You can still create one cluster for VMs and another cluster for containers running on those VMs; you just can't explicitly map one to the other.
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#1571
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?