Feature: "Allocations" Resource

[coxley]

There have been issues raised about tracking VRFs, VLANs, ASNs, etc. Talking through implementation of Protocol brought this up again w.r.t ASNs.

We should have a generic resource for "Allocations" or whatever you want to call them. These are lighter-weight objects that don't need much, but not tracking metadata at all would suck.

• VLAN
• VRF
• ASN
• VNID (VXLAN / GENEVE)
• DLCI

Worth noting that I don't think is a requirement for Protocol. We obviously already have VLAN ID on Interface. Will be nice to have though.

[jathanism]

I'm glad you thought of that. And it just occurred to me that we already have that in progress, but they're currently called Iterable.

Check out this PR from @termlen0 #218

@coxley Take a look at that PR and let's see if it fits the bill. I think it does. I had already been tossing around the idea that something like ASN is super specific and maybe doesn't need its own first-class resource.

[termlen0]

YES! This is exactly what the Iterables is trying to address :)

[mpenning]

I'm curious... did the iterables idea die on the vine, or did the idea get implemented under another name?

A simple string for "iterable" turns up nothing; searching for "allocation" gives more results, but it doesn't seem to be implemented as a general feature.