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

Site: Add possibilits for Sub-Locations / Nested sites #4649

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

Originally created by @c-po on GitHub (Mar 11, 2021).

NetBox version

v2.10.3

Feature type

New functionality

Proposed functionality

Currently a site is assigned to a region and or tenent. It would be very good to also support site-in-site or nesting of sites, called a sublocation.

Use case

Imagine several large campus networks on the globe where region is EMEA, and the site name would be Munich.

Now the Munich campus network will have several buildings all associated with the particular site, but they run their own AS numbers, may have different contact persons but in the greater good are all managed by the Munich site.

By adding the possibility to specify a sublocation which is bound to a larger site one can also only list "per building" IP addresses or the IP addresses for the entire site.

Database changes

Probably yes

External dependencies

No

Originally created by @c-po on GitHub (Mar 11, 2021). ### NetBox version v2.10.3 ### Feature type New functionality ### Proposed functionality Currently a site is assigned to a region and or tenent. It would be very good to also support site-in-site or nesting of sites, called a sublocation. ### Use case Imagine several large campus networks on the globe where region is `EMEA`, and the site name would be `Munich`. Now the Munich campus network will have several buildings all associated with the particular site, but they run their own AS numbers, may have different contact persons but in the greater good are all managed by the Munich site. By adding the possibility to specify a sublocation which is bound to a larger site one can also only list "per building" IP addresses or the IP addresses for the entire site. ### Database changes Probably yes ### External dependencies No
adam added the type: feature label 2025-12-29 19:19:08 +01:00
adam closed this issue 2025-12-29 19:19:08 +01:00
adam commented 2025-12-29 19:19:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 11, 2021):

NetBox v2.11 repurposes the RackGroup model (now named Location) for this purpose (#5895) and allows devices to be assigned to locations within a site (#4971). These changes, along with extended support for custom fields, are likely to address your needs. If not, we can consider revisiting the topic after the final v2.11.0 release.

@jeremystretch commented on GitHub (Mar 11, 2021): NetBox v2.11 repurposes the RackGroup model (now named Location) for this purpose (#5895) and allows devices to be assigned to locations within a site (#4971). These changes, along with extended support for custom fields, are likely to address your needs. If not, we can consider revisiting the topic after the final v2.11.0 release.
adam commented 2025-12-29 19:19:09 +01:00
Author
Owner
Copy Link

@c-po commented on GitHub (Mar 11, 2021):

Does this also apply to IP prefixes and not only devices? This is definately something we will try with the v2.11 release when it's out.

@c-po commented on GitHub (Mar 11, 2021): Does this also apply to IP prefixes and not only devices? This is definately something we will try with the v2.11 release when it's out.
adam commented 2025-12-29 19:19:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 11, 2021):

There's no plan for that at this time, no.

Now the Munich campus network will have several buildings all associated with the particular site, but they run their own AS numbers, may have different contact persons but in the greater good are all managed by the Munich site.

I have to say it really sounds like you'd be better offer designating each building as its own site, within a region representing the campus.

@jeremystretch commented on GitHub (Mar 11, 2021): There's no plan for that at this time, no. > Now the Munich campus network will have several buildings all associated with the particular site, but they run their own AS numbers, may have different contact persons but in the greater good are all managed by the Munich site. I have to say it really sounds like you'd be better offer designating each building as its own site, within a region representing the campus.
adam commented 2025-12-29 19:19:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 17, 2021):

Closing this as it's likely addressed by #4971 as mentioned above.

@jeremystretch commented on GitHub (Mar 17, 2021): Closing this as it's likely addressed by #4971 as mentioned above.
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#4649
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?