Feature: "Allocations" Resource
- Dominant language
- Python
- Stars
- 407
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by reviewing the existing Protocol and Interface resources, then compare how VLAN, VRF, ASN, VNID, and DLCI would fit a generic allocation model. The issue is complete only when the resource scope, metadata, and supported allocation types are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100