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

Assign virtualization Clusters to a Location #5588

New Issue
Closed
opened 2025-12-29 19:29:48 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:29:48 +01:00
Owner
Copy Link

Originally created by @bluikko on GitHub (Oct 31, 2021).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.0.8

Feature type

Data model extension

Proposed functionality

Virtualization clusters should be assignable to locations.

When the location function was added, clusters missed this option.

The open issue #6429 is similar and is marked as blocked by #6440 for better handling of "multi-model parent assignments". The same issue may affect this feature but I feel the use case is quite strong.

Use case

Because Clusters are only assignable to Sites and not to Locations, the whole Locations feature is currently unusable for documentation that consist of both physical Devices and Virtual Machines.

It makes integrations very difficult if the physical location of Devices uses the Locations feature but location of Virtual Machines uses the Sites feature. So in practice both Devices and Virtual Machines then need to use Site for the physical location.

Adding Location for Clusters would allow to locate both Devices and Virtual Machines using Location.

Database changes

Virtualization Clusters would need a parent Location.

External dependencies

none

Originally created by @bluikko on GitHub (Oct 31, 2021). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.0.8 ### Feature type Data model extension ### Proposed functionality Virtualization clusters should be assignable to locations. When the location function was added, clusters missed this option. The open issue #6429 is similar and is marked as blocked by #6440 for better handling of "multi-model parent assignments". The same issue may affect this feature but I feel the use case is quite strong. ### Use case Because Clusters are only assignable to Sites and not to Locations, the whole Locations feature is currently unusable for documentation that consist of both physical Devices and Virtual Machines. It makes integrations very difficult if the physical location of Devices uses the Locations feature but location of Virtual Machines uses the Sites feature. So in practice both Devices and Virtual Machines then need to use Site for the physical location. Adding Location for Clusters would allow to locate both Devices and Virtual Machines using Location. ### Database changes Virtualization Clusters would need a parent Location. ### External dependencies none
adam added the status: acceptedtype: featurenetboxbreaking changecomplexity: low labels 2025-12-29 19:29:48 +01:00
adam closed this issue 2025-12-29 19:29:48 +01:00
adam commented 2025-12-29 19:29:49 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 11, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jan 11, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:29:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 2, 2023):

Similarly, #9969 proposes also extending cluster assignments to site groups.

@jeremystretch commented on GitHub (May 2, 2023): Similarly, #9969 proposes also extending cluster assignments to site groups.
adam commented 2025-12-29 19:29:49 +01:00
Author
Owner
Copy Link

@ocient-jlarson commented on GitHub (Aug 2, 2023):

This would be incredibly useful. Location shows up in Ansible hostvars very nicely for devices. After some poking I couldn't figure out how to get location passed in for VMs and then found this. In our use case "Site" is a datacenter and the "Location" could be separate locations within the datacenter "cages" between prod/nonprod. Was planning to use this for tagging on our monitoring to keep it consistent between devices/virtual machines.

@ocient-jlarson commented on GitHub (Aug 2, 2023): This would be incredibly useful. Location shows up in Ansible hostvars very nicely for devices. After some poking I couldn't figure out how to get location passed in for VMs and then found this. In our use case "Site" is a datacenter and the "Location" could be separate locations within the datacenter "cages" between prod/nonprod. Was planning to use this for tagging on our monitoring to keep it consistent between devices/virtual machines.
adam commented 2025-12-29 19:29:49 +01:00
Author
Owner
Copy Link

@ocient-cliimatta commented on GitHub (Aug 10, 2023):

Yes, this makes it very difficult to use a location's config context on a Virtual machine, even though "Cluster" is available.

I assume that location would need to be assignable to a cluster for this to work? Currently it looks like only Sites are supported at that level.

@ocient-cliimatta commented on GitHub (Aug 10, 2023): Yes, this makes it very difficult to use a location's config context on a Virtual machine, even though "Cluster" is available. I assume that location would need to be assignable to a cluster for this to work? Currently it looks like only Sites are supported at that level.
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 breaking change complexity: low netbox status: accepted 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#5588
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?