openstack/tripleo-heat-templates
Code Issues Proposed changes

Use 'NeutronTenantNetwork' instead of 'NeutronApiNetwork' for ovn-encap-ip

Browse Source 
ovn::controller:ovn-encap-ip is used by OVN Controllers as Geneve tunnel
end points. Presently this is configured with 'NeutronApiNetwork'. Since
the VM traffic is forwarded through the geneve end points, it makes more
sense to use 'NeutronTenantNetwork'. In the case of ML2OVS deployments,
'NeutronTenantNetwork' is used as VxLAN/GRE endpoints. Hence reusing the
same param.

Change-Id: I8b8d8c2bf20697cfb5df6a9cadadc965ae03bbb4
Closes-bug: #1731892
This commit is contained in:
Numan Siddique 2017-11-13 17:53:42 +05:30
parent 23a710ac3c
commit 0b3932ae26
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
puppet/services/ovn-controller.yaml
View File

@ -63,7 +63,7 @@ outputs:
config_settings:
ovn::southbound::port: {get_param: OVNSouthboundServerPort}
ovn::controller::ovn_encap_type: {get_param: OVNTunnelEncapType}
ovn::controller::ovn_encap_ip: {get_param: [ServiceNetMap, NeutronApiNetwork]}
ovn::controller::ovn_encap_ip: {get_param: [ServiceNetMap, NeutronTenantNetwork]}
ovn::controller::ovn_bridge_mappings: {get_param: NeutronBridgeMappings}
ovn::controller::ovn_bridge: {get_param: OVNIntegrationBridge}
nova::compute::force_config_drive: true