Merge "Set correct gateway for the bifrost provision network"
This commit is contained in:
commit
36e9332674
@ -9,7 +9,7 @@
|
||||
# Network configuration.
|
||||
kolla_bifrost_dhcp_pool_start: "{{ provision_oc_net_name | net_inspection_allocation_pool_start }}"
|
||||
kolla_bifrost_dhcp_pool_end: "{{ provision_oc_net_name | net_inspection_allocation_pool_end }}"
|
||||
kolla_bifrost_dnsmasq_router: "{{ provision_oc_net_name | net_gateway }}"
|
||||
kolla_bifrost_dnsmasq_router: "{{ provision_oc_net_name | net_inspection_gateway or provision_oc_net_name | net_gateway }}"
|
||||
kolla_bifrost_dnsmasq_dns_servers: "{{ resolv_nameservers | default([]) }}"
|
||||
kolla_bifrost_domain: "{{ resolv_domain | default }}"
|
||||
kolla_bifrost_download_ipa: "{{ not ipa_build_images | bool }}"
|
||||
|
@ -0,0 +1,9 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
In production environments, the provision network may be separated from the
|
||||
other networks, so in this case, if you want Bifrost's DHCP service provides
|
||||
the correct gateway for the clients the ``inspection_gateway`` should be
|
||||
used instead of the ``gateway`` attribute for the provision network. This
|
||||
also avoids configuring the multiple IP gateways on a single host which
|
||||
leads to unpredictable results.
|
Loading…
x
Reference in New Issue
Block a user