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

Roadmap E5: mark EVPN lab-testable scope complete

Browse Source 
evpn_rib table, gobgp-evpn injector, obmp-evpn-consumer and the EVPN
RIB dashboard are built and verified for type-2/type-3. type-5 and
real (non-synthetic) EVPN remain limited by collector 2.2.3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
sam 2026-05-19 09:31:08 -07:00
parent 4e0f3fb0ff
commit 565ebdbee0
1 changed files with 14 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/ROADMAP.md
View File

@ -325,15 +325,20 @@ Recommended: path 2 for fastest EVPN visibility; path 1 if a single unified
OpenBMP schema outweighs the extra effort. Either way, then build EVPN OpenBMP schema outweighs the extra effort. Either way, then build EVPN
dashboards (per-EVI, MAC mobility, RT scoping). dashboards (per-EVI, MAC mobility, RT scoping).
**Status / measured:** the `evpn_rib` table is in place **Status — lab-testable scope DONE (path 1, type-2/3):**
(`postgres/scripts/007_obmp_evpn.sql`) and a profile-gated `gobgp-evpn` - `evpn_rib` table — `postgres/scripts/007_obmp_evpn.sql`.
injector exercises the pipeline. Verified against the running collector - `gobgp-evpn` — profile-gated synthetic EVPN injector (`evpn-test` profile).
2.2.3: EVPN **type-2 (MAC/IP)** and **type-3 (inclusive multicast)** parse - `obmp-evpn-consumer` — standalone Python consumer, `openbmp.parsed.evpn`
cleanly onto `openbmp.parsed.evpn`; **type-5 (IP-prefix) is mis-decoded** (the → `evpn_rib` (the gap path 1 describes, done without forking the Java
prefix corrupts the RD field). So a path-1 fork inherits a collector that psql-app — a small isolated container instead).
only does type-2/3 reliably — another point in favour of path 2 (GoBMP) if - `EVPN RIB` Grafana dashboard (OBMP-L3VPN folder).
type-5 matters. Next: the `obmp-evpn-consumer` for type-2/3, then the - Verified end to end with synthetic type-2/type-3 routes.
dashboard.
**Known limitation:** collector 2.2.3 **mis-decodes EVPN type-5** (IP-prefix)
— the prefix corrupts the RD field — so type-5 is not ingested. Full type-5
support still needs path 2 (GoBMP) or a newer/fixed collector. Real EVPN
(vs the synthetic injector) also needs an EVPN-capable BMP source — the CML
IOS-XR lab has none.
### E-scale. PostgreSQL sizing for a full table ### E-scale. PostgreSQL sizing for a full table