BGP on VPC private gateways so tenants can peer their own routers with the VR

Offen
  • Stimmt etwas nicht?
#14,687 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
8/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java
Bereich
cloud, networking

Rechercherichtung

This is a design-level feature: a BGP routing option on VPC private gateways, with the peer address taken from the gateway, prefix filtering, per-tier announcements and failover preference. The payload names no source files, so start by reading the linked issues #9964 (upstream route-maps) and #12811 (dynamic routing for NATTED IPv6) to see what is already decided. Done means an agreed design and a maintainer-approved plan, not a patch.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

The required feature described as a wish

As an operator I would like VPC owners to be able to run BGP between the VR and their own routers over a private gateway, so they can connect their on-prem networks with dynamic failover. As an example, we have two high-speed peering links into a cloud exchange (Megaport, in our case), and we carve out a VLAN on each for a customer's virtual cross connects. Each VLAN would attach to a private gateway on the customer's VPC, so the customer has two paths to their own routers. Today they need static routes per gateway, which can't fail over between the two links.

The idea is a routing option on the private gateway. Static would keep today's static routes. BGP would take the peer AS, a password, the prefixes they accept from the peer, which of the VPC tiers they announce to that peer, a max-prefix limit, timers or BFD, and a preference so one link can be primary and the other backup, with the peer address taken from the gateway itself. The VR would accept only the declared prefixes from that peer and announce only the selected VPC tiers to it. That keeps it separate from the operator peers and the upstream route-maps from #9964. It should work for NATTED VPCs as well as ROUTED ones, so I think it relates to #12811, which opens dynamic routing to NATTED offerings for IPv6.

Vorherrschende Sprache
Java
Sterne
3.1k
Forks
1.4k
Ø Merge
7 T. 16 Std.
Gemergte PRs (30 T.)
15

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/cloudstack

Alle Issues in apache/cloudstack

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.