move work design under equinix
This commit is contained in:
17
equinix/design/vrf-bgp-routes.org
Normal file
17
equinix/design/vrf-bgp-routes.org
Normal file
@@ -0,0 +1,17 @@
|
||||
#+TITLE: Implementing endpoint to expose learned routes
|
||||
#+AUTHOR: Adam Mohammed
|
||||
#+DATE: October 30, 2023
|
||||
|
||||
I asked Tim about what the difference is between
|
||||
|
||||
https://deploy.equinix.com/developers/api/metal#tag/VRFs/operation/getBgpDynamicNeighbors
|
||||
and what's available in Trix.
|
||||
|
||||
The first is just data configured by the customer manually.
|
||||
|
||||
Trix exposes the learned routes from peers
|
||||
|
||||
I then asked if it made sense to expose the data as part of:
|
||||
https://deploy.equinix.com/developers/api/metal#tag/VRFs/operation/getVrfRoutes
|
||||
|
||||
and the answer I got was probaly
|
||||
Reference in New Issue
Block a user