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

オープン
#14,687 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
8/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
java
領域
cloud, networking

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Java
スター
3.1k
フォーク
1.4k
平均マージ
7日 16時間
マージ済み PR(30日)
15

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

apache/cloudstack のほかの issue

apache/cloudstack の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。