Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MEP-15 Announced IP visibility #145

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

MEP-15 Announced IP visibility #145

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions docs/src/development/proposals/MEP13/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
3 changes: 2 additions & 1 deletion docs/src/development/proposals/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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` |
Expand All @@ -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` |