Multiple CIDRs per block and API

[whizzer929]

Hello,

We're evaluating your IPAM and so far it's working well. However, we have a use case where we have multiple CIDR subnets that would make up a block. I.E. space = dev, block = private, CIDRs = 10.40.0.0/18 AND 10.40.64.0/19. Our only work around is too create multiple blocks with index number. private_1, private_2. However, this now dictates the use of multiple API URLs and choosing which one to use is problematic.

How can we have multiple associated blocks and a single API URL?

Thanks.

[DCMattyG]

Hi @whizzer929, appreciate you reaching out!

The important thing to keep in mind is that a Block represents a CIDR space, and any vNET's (subnets) that are a part of that block must fit within the Block's CIDR.

In the above example, I believe you were stating that you have two different CIDR's applied to a vNET (10.40.0.0/18 and 10.40.64.0/19), correct? What was the Block CIDR you assigned (if I may ask)?

P.S. If I misunderstood anything, please keep me honest. Thanks!

[whizzer929]

Yeah, we work together. lol. I never imagined you'd be speaking with him.

[DCMattyG]

After discussing this @amitjattan, it seems like the only path forward would be a feature request to have multiple, non-summarize-able CIDR's as part of a Block. I'm still not quite sure what that will look like in my head hahaha, but the only other option I can think of is perhaps some kind of "Batch" API where you can provide multiple Blocks and get back the first new CIDR of the target/requested size.

I have a feeling the latter would be far easier to implement as it wouldn't require core changes in the design, but I'm always open to your thoughts on if this would completely meet your needs if that's the path we go down.

Looking forward to your feedback!

[whizzer929]

"some kind of "Batch" API where you can provide multiple Blocks and get back the first new CIDR of the target/requested size." That should work.

[DCMattyG]

I'm on it!

[DCMattyG]

Good morning @whizzer929, I have the draft of this feature built and added to the IPAMDEV containers. Please give it a try and let me know if you have any feedback/improvements.

Assuming you are using the standard Full deployment, you can switch to the DEV containers by updating the Deployment Settings in your App Service as follows:

Once you have that saved & restarted, you'll find the new API in the Swagger Docs:

This API will be called at the Space level, and is essentially the same as the reservations API at the Block level, except this takes a list (array) of Blocks from within the Space as a parameter, and will evaluate them in the order they are provided.

EXAMPLE BODY

{
    "blocks": ['TestBlock01', 'TestBlock02'],
    "size": 24
}

Hope you enjoy, please let me know how you like it!

[whizzer929]

Hi DCMattyG, we just got the new code and will start testing. So far, it looks good. Thanks for the update! Your responsiveness is much appreciated.