Add possibility to assign cluster to Site Group #4915

Closed
opened 2025-12-29 19:22:14 +01:00 by adam · 4 comments
Owner

Originally created by @ziggekatten on GitHub (May 17, 2021).

NetBox version

v2.11.3

Feature type

Change to existing functionality

Proposed functionality

Currently a cluster is always tied to a Site. For stretched clusters (nodes in more than one data center) it would make sense to assign the cluster to a site group.

Use case

We are running VMware clusters with vSAN over stretched L2 networks between sites. We also run Fortigate FW clusters with nodes in each DC. Being able to model this on site group level would enable us to use the new features on 2.11(Site Groups) that we today can't use, and are today modeling by using one site for both sites, and Rack Groups(Location in 2.11) to distinguish the physical site.

Database changes

Probably a relation to Site Group instead of SIte, so I'm not sure any DB-changes are needed

External dependencies

No response

Originally created by @ziggekatten on GitHub (May 17, 2021). ### NetBox version v2.11.3 ### Feature type Change to existing functionality ### Proposed functionality Currently a cluster is always tied to a Site. For stretched clusters (nodes in more than one data center) it would make sense to assign the cluster to a site group. ### Use case We are running VMware clusters with vSAN over stretched L2 networks between sites. We also run Fortigate FW clusters with nodes in each DC. Being able to model this on site group level would enable us to use the new features on 2.11(Site Groups) that we today can't use, and are today modeling by using one site for both sites, and Rack Groups(Location in 2.11) to distinguish the physical site. ### Database changes Probably a relation to Site Group instead of SIte, so I'm not sure any DB-changes are needed ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:22:14 +01:00
adam closed this issue 2025-12-29 19:22:14 +01:00
Author
Owner

@jeremystretch commented on GitHub (May 18, 2021):

Marking as blocked until we figure out whether there's a more optimal way to track multi-model parent assignments (see #6440).

@jeremystretch commented on GitHub (May 18, 2021): Marking as blocked until we figure out whether there's a more optimal way to track multi-model parent assignments (see #6440).
Author
Owner

@mazhead commented on GitHub (Nov 5, 2021):

@jeremystretch #6440 got closed, can we maybe revisit this one?

@mazhead commented on GitHub (Nov 5, 2021): @jeremystretch #6440 got closed, can we maybe revisit this one?
Author
Owner

@github-actions[bot] commented on GitHub (Jul 1, 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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jul 1, 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Aug 1, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Aug 1, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4915