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

Allow for overlapping Aggregates #1087

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

Originally created by @eacheach on GitHub (Jul 10, 2017).

Issue type:

Feature Request

Python version:
NetBox version:

We would like to see support for overlapping Aggregates. We use Aggregates to show available subnets within the defined Aggregate. We allocate address space hierarchically so we'd like the flexibility of scoping our output so the most appropriate aggregate for the task. For instance:

10.0.0.0/8 is used for customer networks
10.0.0.0/9 is used in DC1
10.128.0.0/9 is used in DC2
10.1.0.0/16 is allocated to Customer X in DC1
etc...

If I need a new /16 for a new customer in DC1 we'd like to look at the 10/9 Aggregate.
If we need to allocate a new /24 network to Customer X in DC1 we'd like to look at the 10.1/16 Aggregate.

Originally created by @eacheach on GitHub (Jul 10, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: Feature Request <!-- If filing a bug, please indicate the version of Python and NetBox you are running. (This is not necessary for feature requests.) --> **Python version:** **NetBox version:** <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> We would like to see support for overlapping Aggregates. We use Aggregates to show available subnets within the defined Aggregate. We allocate address space hierarchically so we'd like the flexibility of scoping our output so the most appropriate aggregate for the task. For instance: 10.0.0.0/8 is used for customer networks 10.0.0.0/9 is used in DC1 10.128.0.0/9 is used in DC2 10.1.0.0/16 is allocated to Customer X in DC1 etc... If I need a new /16 for a new customer in DC1 we'd like to look at the 10/9 Aggregate. If we need to allocate a new /24 network to Customer X in DC1 we'd like to look at the 10.1/16 Aggregate.
adam closed this issue 2025-12-29 16:28:41 +01:00
adam commented 2025-12-29 16:28:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 10, 2017):

This would defeat the purpose of aggregates. Aggregates define the top level of your IP space hierarchy. Use prefixes to organize space within aggregates.

@jeremystretch commented on GitHub (Jul 10, 2017): This would defeat the purpose of aggregates. Aggregates define the top level of your IP space hierarchy. Use prefixes to organize space within aggregates.
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
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#1087
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?