Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Prefix Utilization and Aggregate Utilization available via API #7292

Open
emallette opened this issue Sep 17, 2021 · 3 comments
Open

Make Prefix Utilization and Aggregate Utilization available via API #7292

emallette opened this issue Sep 17, 2021 · 3 comments
Labels
netbox status: blocked Another issue or external requirement is preventing implementation type: feature Introduction of new functionality to the application

Comments

@emallette
Copy link

NetBox version

v2.11.12

Feature type

Data model extension

Proposed functionality

Currently, the UI displays the utilization for prefixes and aggregates - like that functionality. We would like to obtain the utilization via API as well. It appears that the utilization is being calculated on the fly to display in the API. Could you expose that to the API ?

Use case

There are a number of cases where it would be helpful:

  1. We are programmatically allocating prefixes as part of our ordering system and today we are simply attempting to allocate prefix size FOO from block A, on failure we move to block B. We would like to be able to see the utilization of a block and quickly determine whether or not to attempt to allocate from that prefix or container.

  2. We would like to be able to quickly generate our own utilization reports using the calculations already performed in Netbox rather than re-writing the same allocation logic and this would be helpful.

Database changes

No response

External dependencies

No response

@emallette emallette added the type: feature Introduction of new functionality to the application label Sep 17, 2021
@jeremystretch
Copy link
Member

This was recently proposed under #6606 and did not seem to generate any interest. Please see my comment here on the likely avenues for implementation.

@emallette are you interested in owning this work?

@jeremystretch
Copy link
Member

As I commented here, implementing this elegantly will probably require that we first pre-render utilization data for all aggregates, prefixes, and ranges. I've opened #7451 to explore the idea. This proposal should be considered blocked until a decision has been made on #7451.

@jeremystretch jeremystretch added the status: blocked Another issue or external requirement is preventing implementation label Oct 5, 2021
@jeremystretch
Copy link
Member

Also related to #7845

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
netbox status: blocked Another issue or external requirement is preventing implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants