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

Abierto
  • ¿Algo no está bien?
#14,687 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
cloud, networking

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Java
Estrellas
3.1k
Forks
1.4k
Merge medio
7 d 16 h
PR fusionados (30 d)
15

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/cloudstack

Todos los issues de apache/cloudstack

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.