3162846a7b
In order to route traffic between the internal subnets and the external subnet that belong to the same address_scopes we need to create the gateway port and the fip namespace irrespective of the configured floatingips for the internal subnet. This will consume an additional IP from the external subnet on all nodes, but with the introduction of service_type networks, this will not be an issue any more. This patch is the first in series that creates the agent gateway port and the fip namespace on every node when the gateway is set for the router. For every router created it will connect the router namespace to the fip namespace. Partial-Bug: #1577488 DocImpact: Document the change in behavior for fip-agent-gw create Change-Id: I30c4f7fc250e486fe9a71b68540e783e90a6cf15
14 lines
553 B
YAML
14 lines
553 B
YAML
---
|
|
prelude: >
|
|
Add DVR Floating IP (FIP) Namespace creation event
|
|
on all nodes, based on the gateway configuration.
|
|
features:
|
|
- Proactively create Floating IP Namespace on all compute nodes
|
|
when a gateway is configured.
|
|
issues:
|
|
- This might consume public IP Address, but by using
|
|
subnet service-types as explained in the docs below
|
|
https://docs.openstack.org/networking-guide/config-service-subnets.html
|
|
consumers can use the private IPs for floating IP agent gateway ports
|
|
and need not consume any public IP addresses.
|