From 364c01a2d76d2b1af2be897f2d8146de3bb2b412 Mon Sep 17 00:00:00 2001 From: Konrad Gube Date: Tue, 27 Aug 2024 15:15:22 +0200 Subject: [PATCH] Add reference to ovn-bgp-agent Signed-off-by: Konrad Gube --- Standards/scs-xxxx-v1-provider-network-standard.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Standards/scs-xxxx-v1-provider-network-standard.md b/Standards/scs-xxxx-v1-provider-network-standard.md index cd757a935..9361d3f44 100644 --- a/Standards/scs-xxxx-v1-provider-network-standard.md +++ b/Standards/scs-xxxx-v1-provider-network-standard.md @@ -67,7 +67,7 @@ This works well for shared networks, where servers can be attached directly, but Making servers in a project-internal network externally accessible through a virtual router is a bit more complicated, though. One option is for the user to create a subnet with an external IP range for the internal network, and then ask the CSP to configure a static route to the subnet via the gateway IP of a virtual router. -This is cumbersome to set up manually, but can be automated using the `bgp` extension of the Network API, which is implemented by the `neutron-dynamic-routing` project [^bgp]. +This is cumbersome to set up manually, but can be automated using the `bgp` extension of the Network API, which is currently implemented both by the `neutron-dynamic-routing` project [^bgp] and by the `ovn` mechanism driver when used with the `ovn-bgp-agent` [^ovn-bgp]. For users, this takes the form of a CSP-managed shared subnet pool, which they can use to create externally routable subnets, limited by a per-project quota. For IPv6, there is also the option of prefix delegation, where a DHCPv6 server automatically assigns an IPv6 prefix to a subnet when it connects to the external provider network [^pd]. @@ -207,6 +207,7 @@ By default, users **SHOULD** be prohibited by policy from creating RBAC rules fo ## References [^bgp]: +[^bgp-ovn]: [^pd]: [^pf]: [^ds]: