Routing module (static/dynamic routing + BGP objects)

[deku-m]

Summary

Add a routing module to Danbyte covering static/dynamic routing and BGP-related
object documentation.

Background

Looked at how other IPAM/DCIM tooling in this space handles routing and BGP.
The common pattern splits into two overlapping approaches: a general routing
module (static routes, dynamic routing protocols, VRF/AF-aware) and a
BGP-specific object model (sessions, peer groups, policies, lists). Rather
than pick one approach, I'd like Danbyte to design one coherent routing/BGP
data model that takes the best ideas from both.

Rough scope (to be refined)

• Static routes (per device/VRF)
• Dynamic routing protocols: BGP, OSPF, EIGRP (BGP first)
• BGP objects: Sessions, Peer Groups, Communities, Routing Policies,
  Prefix Lists, AS Path Lists
• Template / group-level inheritance for BGP config (avoid repeating the
  same session params across many peers)
• VRF-aware, IPv4/IPv6 AF support
• Device detail page integration (surface routing/BGP info without leaving
  the device view, e.g. as a tab or side panel)

How do you see this?

[DenDanskeMine]

Yep, something I already have a note about.
How would you use this -would it be to feed Ansible or just for documentation purposes?

This might be a tricky one, as routing protocols are complex to model. For BGP, it would be ideal to also model MP-BGP EVPN (family-groups). Another feature I have noted is support for over/underlay modeling of BGP, IS-IS, VXLAN, and so on.

when you say VRF aware do you then apply that danbyte should be pooling info? or just an option to add a VRF? by default vrf would be included as this is 100% necessary to model this correctly

i have made a leaf/spine lab recently to prepare for this BGP/IS-IS/EVPN feature.

It also briefly covers SD-WAN documentation, and some path-shaping. please add more to this FR if you coem up with other routing related ideas, might as well keep it in here :)

[deku-m]

How would you use this -would it be to feed Ansible or just for documentation purposes?
I think it could be used for both. The goal is to standardize the network addressing, for example using 10..., where the 2nd octet identifies the location and the 3rd octet is VLAN-related.
Initially, this would provide documentation and a clear overview of which VRFs, VLANs, subnets, and routes are active at each location.
Eventually, the same data could also be used as the source for Ansible, allowing us to automate the rollout of new locations, including the required VLANs and VRFs

This might be a tricky one, as routing protocols are complex to model. For BGP, it would be ideal to also model MP-BGP EVPN (family-groups). Another feature I have noted is support for over/underlay modeling of BGP, IS-IS, VXLAN, and so on.

when you say VRF aware do you then apply that danbyte should be pooling info? or just an option to add a VRF? by default vrf would be included as this is 100% necessary to model this correctly
My thought is that we would have a consistent set of VRFs across locations, for example GUEST, FACTORY, and OFFICE. The VRF names would be the same at each location, while the actual subnets can differ per location.
For example, the guest subnet would always belong to the GUEST VRF, the printer subnet to the OFFICE VRF, etc. So the model should be VRF-aware and associate each subnet with its corresponding VRF.

Image

i have made a leaf/spine lab recently to prepare for this BGP/IS-IS/EVPN feature.

It also briefly covers SD-WAN documentation, and some path-shaping. please add more to this FR if you coem up with other routing related ideas, might as well keep it in here :)
SD-WAN is definitely useful to include as well. We’re using it here too, although I’m not completely sure yet what the best way is to model it.
If i come up with additionals i will add it for sure.