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

Regional Grouping of Sites #476

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

Originally created by @martink2 on GitHub (Oct 14, 2016).

Current State

Currently we have the Site Object which references a physical DC location
with Address etc. For some objects like VLAN's we have a mandatory site
relationship, for others it is optional like IP Prefixes. Once the Site attribute is set
on an object i can only use it in that site.

Problem

We are managing a large number of DC Sites, some of them don't have any relationship with
each other fitting the current implementation very well. But we also have a larger number of DC's
which are located in the same metro area. Those have different buildings and addresses, so for the rack locations etc they are very much different sites but since they are closely interconnected from the network side they are more behaving like one (Vlans are Spanning Sites, so are IP Networks). So currently I have double the VLAN's and I cant assign Subnets to them since once
assigned I can no longer use it on both sides.

Proposal

Proposal is to implement a new object which represents a cluster of Sites (I would call it a region)
which are different physical locations (For Racks / Groups / Equipment ) but behave like one entity in regards to networking objects (VLAN, Subnets etc.).
For all objects that can currently be assigned or have to be assigned to a site the logic would be to assign them either to a site or a region making it available in all sites of the region.

Region 1 = Site A, Site B
VLAN 100 = Region 1
Prefix 10.0.0.0/24 Wtih Vlan 100

--> Results in I can use the Prefix in Site A and B like i could now with a prefix assigned directly to the site.

Originally created by @martink2 on GitHub (Oct 14, 2016). ### Current State Currently we have the Site Object which references a physical DC location with Address etc. For some objects like VLAN's we have a mandatory site relationship, for others it is optional like IP Prefixes. Once the Site attribute is set on an object i can only use it in that site. ### Problem We are managing a large number of DC Sites, some of them don't have any relationship with each other fitting the current implementation very well. But we also have a larger number of DC's which are located in the same metro area. Those have different buildings and addresses, so for the rack locations etc they are very much different sites but since they are closely interconnected from the network side they are more behaving like one (Vlans are Spanning Sites, so are IP Networks). So currently I have double the VLAN's and I cant assign Subnets to them since once assigned I can no longer use it on both sides. ### Proposal Proposal is to implement a new object which represents a cluster of Sites (I would call it a region) which are different physical locations (For Racks / Groups / Equipment ) but behave like one entity in regards to networking objects (VLAN, Subnets etc.). For all objects that can currently be assigned or have to be assigned to a site the logic would be to assign them either to a site or a region making it available in all sites of the region. Region 1 = Site A, Site B VLAN 100 = Region 1 Prefix 10.0.0.0/24 Wtih Vlan 100 --> Results in I can use the Prefix in Site A and B like i could now with a prefix assigned directly to the site.
adam added the status: duplicate label 2025-12-29 16:22:31 +01:00
adam closed this issue 2025-12-29 16:22:32 +01:00
adam commented 2025-12-29 16:22:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 14, 2016):

Duplicate of #164

@jeremystretch commented on GitHub (Oct 14, 2016): Duplicate of #164
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 status: duplicate
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#476
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?