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

Aberta
  • Algo errado?
#14,687 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java
Domínio
cloud, networking

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Java
Estrelas
3.1k
Forks
1.4k
Merge médio
7d 16h
PRs com merge (30d)
15

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de apache/cloudstack

Todas as issues de apache/cloudstack

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.