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

Optionally Assigning a Site to a VM Cluster #1243

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

Originally created by @cimnine on GitHub (Sep 19, 2017).

Issue type

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

Environment

  • Python version: 2.7
  • NetBox version: 2.2-beta1

Description

Each of our clusters is restricted to a certain site. Therefore I would like to optionally assign a site to a cluster.

Originally created by @cimnine on GitHub (Sep 19, 2017). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. If none of the below apply, please raise your issue for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. ---> ### 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 --> <!-- 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.) --> ### Environment * Python version: 2.7 * NetBox version: 2.2-beta1 <!-- BUG REPORTS must include: * A list of the steps needed to reproduce the bug * A description of the expected 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 Each of our clusters is restricted to a certain site. Therefore I would like to optionally assign a site to a cluster.
adam added the type: feature label 2025-12-29 16:30:33 +01:00
adam closed this issue 2025-12-29 16:30:33 +01:00
adam commented 2025-12-29 16:30:34 +01:00
Author
Owner
Copy Link

@cimnine commented on GitHub (Sep 19, 2017):

If set, this could also be used to restrict which host devices can be selected for the cluster.

@cimnine commented on GitHub (Sep 19, 2017): If set, this could also be used to restrict which host devices can be selected for the cluster.
adam commented 2025-12-29 16:30:34 +01:00
Author
Owner
Copy Link

@darkstar commented on GitHub (Sep 19, 2017):

Just to clarify: This is for clusters that don't consist of physical devices, right? Like AWS or Azure clusters?

Because if you assign a device to a cluster, that device has a physical location in a certain rack, and that rack is located in a site.

@darkstar commented on GitHub (Sep 19, 2017): Just to clarify: This is for clusters that don't consist of physical devices, right? Like AWS or Azure clusters? Because if you assign a device to a cluster, that device has a physical location in a certain rack, and that rack is located in a site.
adam commented 2025-12-29 16:30:34 +01:00
Author
Owner
Copy Link

@cimnine commented on GitHub (Sep 19, 2017):

I had physical devices in mind. You could also build a cluster across sites. Ultimately I want to be able to filter the clusters by site and ideally also to restrict it to devices of that site.

@cimnine commented on GitHub (Sep 19, 2017): I had physical devices in mind. You could also build a cluster across sites. Ultimately I want to be able to filter the clusters by site and ideally also to restrict it to devices of that site.
adam commented 2025-12-29 16:30:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 22, 2017):

Implemented in 2ca161f

@jeremystretch commented on GitHub (Sep 22, 2017): Implemented in 2ca161f
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#1243
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?