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

Aperta
  • Qualcosa non va?
#14,687 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
cloud, networking

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Java
Stelle
3.1k
Fork
1.4k
Merge medio
7g 16h
PR unite (30g)
15

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/cloudstack

Tutte le issue di apache/cloudstack

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.