Block availability and creation of IPs in IP Ranges

[iamjla]

NetBox version

v3.4.2

Feature type

Change to existing functionality

Proposed functionality

We would suggest "IP Ranges" gets the following 2 new booleans:

• "Exclude from Available IPs"
  This still allows creation of IPs of this IP Range but prohibits them from being used in available ip logic (API&UI)

• "Block creation of IPs in this Range"
  As the name suggests, any IP creation in this range should be blocked

Use case

General IP Ranges for DHCP
or
Exclude ranges for automatic short lived DHCP deployments to avoid collisions which later get proper IPs assigned
and
To avoid blocking e.g. 2000 (or IPv6-scale amounts of) IPs in the database manually

Something similar came up in #7516 though it was about utilization and making them unavailable for other uses.

#9763 captures a possible UI solution

Database changes

No response

External dependencies

No response

[do9xe]

We're also looking into how we could leverage the ranges to define DHCP-Pools for our deployments. I also thought about using the "is a pool" flag, but it has another purpose. I'd love to see a possibility to model DHCP-Ranges in NetBox.
After reading through #7516 and #9763 I think a combination of all three could be a viable solution. Having the ranges blocking the utilization, showing up in the IP address list and having the possibility to block the creation of IPs would be a good combination. Especially making the "block creation" option optional for DHCP-Ranges so one could create static DHCP-bindings within a pool.

[jsenecal]

Thinking this should be handled by what would be done in #9763.

Feel free to discuss your booleans in there, or, any additional requirements.