sam/obmp-docker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Roadmap: add E5 — L2VPN/EVPN needs platform work, not dashboards

Browse Source 
This OpenBMP deployment has no EVPN/L2VPN schema; supporting it
requires collector + psql-app + schema changes upstream, not a
Grafana dashboard. Captured as E5 with a research-spike first.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
sam 2026-05-19 08:01:59 -07:00
parent 6496b60311
commit 7766525787
1 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/ROADMAP.md
View File

@ -297,6 +297,23 @@ and the global feed carries none — so E4 is **built to the L3VPN schema and
unverifiable in this lab**; it validates only against production routers.
Keep E4 scope minimal until there's a real L3VPN source.
### E5. L2VPN / EVPN support — platform-level, not a dashboard task
L2VPN/EVPN was requested alongside L3VPN. **It cannot be done as a dashboard
change**: this OpenBMP deployment (collector 2.2.3, psql-app 2.2.2) has *no
EVPN/L2VPN schema* — the only RIB tables are `ip_rib` (unicast), `l3vpn_rib`
(VPNv4/6) and `ls_*` (BGP-LS). EVPN routes (Type-2 MAC/IP, Type-3 IMET,
Type-5 IP-prefix) have nowhere to land and are dropped by the consumer.
Supporting it means **upstream platform work**, not Grafana:
- EVPN parsing in the collector + psql-app (these are upstream `openbmp/*`
images — would need a fork or an upstream contribution).
- A new `evpn_rib` / `l2vpn_rib` table + history + stats.
- Only then: EVPN dashboards (per-EVI, MAC mobility, RT scoping).
Recommend treating E5 as a research spike first: confirm whether any current
OpenBMP release adds EVPN, versus the cost of carrying a fork.
### E-scale. PostgreSQL sizing for a full table
A full v4+v6 table is ~1.2M prefixes; with attributes and history this is a
@ -328,7 +345,8 @@ more valuable once real-Internet AS paths are present.
| 14 | E1 | Analytics | GoBGP full-table feed (AS57355 live + MRT fallback) |
| 15 | E2 | Analytics | Generic 4-router diff dashboard |
| 16 | E3 | Analytics | Global table exploration dashboard |
| 17 | E4 | Analytics | VRF/RD scoping (to schema, lab-unverifiable) |
| 17 | E4 | Analytics | VRF/RD scoping for L3VPN (to schema, lab-unverifiable) |
| 18 | E5 | Platform | L2VPN/EVPN support — research spike, then collector/schema work |
Steps 1-5 (Track A) unblock everything else. Steps 6-7 and 8-10 can proceed in parallel once the foundation is in place. Track E is independent of A-D: E1 is the foundation for E2/E3; E4 can proceed any time but is lab-unverifiable.