From ac5db685ec535b4bfa7076ce0998eac8364bc50d Mon Sep 17 00:00:00 2001 From: Stefan Majer Date: Fri, 18 Aug 2023 11:43:48 +0200 Subject: [PATCH] MEP-13 --- .../src/development/proposals/MEP13/README.md | 20 +++++++++++++++++++ docs/src/development/proposals/index.md | 3 ++- 2 files changed, 22 insertions(+), 1 deletion(-) create mode 100644 docs/src/development/proposals/MEP13/README.md diff --git a/docs/src/development/proposals/MEP13/README.md b/docs/src/development/proposals/MEP13/README.md new file mode 100644 index 0000000000..b290fa8aec --- /dev/null +++ b/docs/src/development/proposals/MEP13/README.md @@ -0,0 +1,20 @@ +# BGP data plane visibility + +Currently a operator can not identify if a certain IP, which is allocated, is actually announced to the outer world. +We want to gather information about the routes on the edge of the network of every partition and store them in the metal-api. + +This will bring more visibility to the network and ip address usage in the dataplane. + +To achieve this goal we need to implement a new microservice which collects these data and send them via grpc to the metal-api. +The metal-api will store them in a separate table. Later when a network or single IP is described +a lookup to that table is made to show when this ip was last announced. + +## metal-api + +TODO: describe the new grpc endpoint API and the table structure where the data is stored + +## new microservice on the border router + +TODO: decide name + +HINT: reuse the frr api logic from frr-monitor diff --git a/docs/src/development/proposals/index.md b/docs/src/development/proposals/index.md index 41a5bc2429..700c5b9b7c 100644 --- a/docs/src/development/proposals/index.md +++ b/docs/src/development/proposals/index.md @@ -18,7 +18,7 @@ Possible states are: Once a proposal was accepted, an issue should be raised and the implementation should be done in a separate PR. | Name | Description | State | -| :------------------------ | :--------------------------------------------- | :-------------: | +|:--------------------------|:-----------------------------------------------|:---------------:| | [MEP-1](MEP1/README.md) | Distributed Control Plane Deployment | `In Discussion` | | [MEP-2](MEP2/README.md) | Two Factor Authentication | `Aborted` | | [MEP-3](MEP3/README.md) | Machine Re-Installation to preserve local data | `Completed` | @@ -30,3 +30,4 @@ Once a proposal was accepted, an issue should be raised and the implementation s | [MEP-10](MEP10/README.md) | SONiC Support | `Completed` | | [MEP-11](MEP11/README.md) | Auditing of metal-stack resources | `Completed` | | [MEP-12](MEP12/README.md) | Rack Spreading | `Completed` | +| [MEP-13](MEP13/README.md) | BGP data plane Visibility | `In Discussion` |