Assign virtualization Clusters to a Location

[bluikko]

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

[github-actions]

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.

[jeremystretch]

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

[ocient-jlarson]

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-cliimatta]

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.