<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
For comparison, I looked at how openstack-ansible was setting up OVN
and I don't see any major differences other than O-A configures a
manager for ovs:<br>
ovs-vsctl --id @manager create Manager "target=\ ....<br>
I don't believe this is the point of failure (but feel free to
correct me if I'm wrong ;) ).<br>
<br>
ovn-trace on both VM's inports shows the same trace for the working
VM and the non-working VM. ie:<br>
<br>
ovn-trace --db=$SB --ovs default_net 'inport ==
"f4cbc8c7-e7bf-47f3-9fea-a1663f6eb34d" &&
eth.src==fa:16:3e:a6:62:8e && ip4.src == 172.31.101.168
&& ip4.dst == <provider's gateway IP>'<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 2023-07-07 14:08, Gary Molenkamp
wrote:<br>
</div>
<blockquote type="cite" cite="mid:8511695f-443b-1593-fc20-04cb82cfc791@uwo.ca">
Happy Friday afternoon.<br>
<br>
I'm still pondering a lack of connectivity in an HA OVN with each
compute node acting as a potential gateway chassis.<br>
<br>
<blockquote type="cite" cite="mid:CALsEdxTjfZ_zoagupJQcXHWWpC=fNUNQsXA-Hna+8_duML-8sA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div>The problem is basically that the port of the
OVN LRP may not be in the same chassis as the VM
that failed (since the CR-LRP will be where the
first VM of that network will be created). The
suggestion is to remove the enable-chassis-as-gw
from the compute nodes to allow the VM to
forward traffic via tunneling/Geneve to the
chassis where the LRP resides.<br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<br>
I forced a similar VM onto the same chassis as the
working VM, and it was able to communicate out. If we
do want to keep multiple chassis' as gateways, would
that be addressed with the ovn-bridge-mappings?<br>
</div>
</blockquote>
<div><br>
</div>
</div>
</div>
</blockquote>
<br>
I built a small test cloud to explore this further as I continue
to see the same issue: A vm will only be able to use SNAT
outbound if it is on the same chassis as the CR-LRP.<br>
<br>
In my test cloud, I have one controller, and two compute nodes.
The controller only runs the north and southd in addition to the
neutron server. Each of the two compute nodes is configured as
below. On a tenent network I have three VMs:<br>
- #1: cirros VM with FIP<br>
- #2: cirros VM running on compute node 1<br>
- #3: cirros VM running on compute node 2<br>
<br>
E/W traffic between VMs in the same tenent network are fine. N/S
traffic is fine for the FIP. N/S traffic only works for the VM
whose CR-LRP is active on same chassis. Does anything jump out
as a mistake in my understanding at to how this should be working?<br>
<br>
Thanks as always,<br>
Gary<br>
<br>
<br>
on each hypervisor:<br>
<br>
/usr/bin/ovs-vsctl set open . external-ids:ovn-remote=tcp:{{
controllerip }}:6642<br>
/usr/bin/ovs-vsctl set open . external-ids:ovn-encap-type=geneve<br>
/usr/bin/ovs-vsctl set open . external-ids:ovn-encap-ip={{
overlaynetip }}<br>
/usr/bin/ovs-vsctl set open .
external-ids:ovn-cms-options=enable-chassis-as-gw<br>
/usr/bin/ovs-vsctl add-br br-provider -- set bridge br-provider
protocols=OpenFlow10,OpenFlow12,OpenFlow13,OpenFlow14,OpenFlow15<br>
/usr/bin/ovs-vsctl add-port br-provider {{ provider_nic }}<br>
/usr/bin/ovs-vsctl br-set-external-id provider bridge-id
br-provider<br>
/usr/bin/ovs-vsctl set open .
external-ids:ovn-bridge-mappings=provider:br-provider<br>
<br>
plugin.ini:<br>
[ml2]<br>
mechanism_drivers = ovn<br>
type_drivers = flat,geneve<br>
tenant_network_types = geneve<br>
extension_drivers = port_security<br>
overlay_ip_version = 4<br>
[ml2_type_flat]<br>
flat_networks = provider<br>
[ml2_type_geneve]<br>
vni_ranges = 1:65536<br>
max_header_size = 38<br>
[securitygroup]<br>
enable_security_group = True<br>
firewall_driver =
neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver<br>
[ovn]<br>
ovn_nb_connection = tcp:{{controllerip}}:6641<br>
ovn_sb_connection = tcp:{{controllerip}}:6642<br>
ovn_l3_scheduler = leastloaded<br>
ovn_metadata_enabled = True<br>
enable_distributed_floating_ip = true<br>
<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Gary Molenkamp Science Technology Services
Systems Administrator University of Western Ontario
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:molenkam@uwo.ca" moz-do-not-send="true">molenkam@uwo.ca</a> <a class="moz-txt-link-freetext" href="http://sts.sci.uwo.ca" moz-do-not-send="true">http://sts.sci.uwo.ca</a>
(519) 661-2111 x86882 (519) 661-3566</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Gary Molenkamp Science Technology Services
Systems Engineer University of Western Ontario
<a class="moz-txt-link-abbreviated" href="mailto:molenkam@uwo.ca">molenkam@uwo.ca</a> <a class="moz-txt-link-freetext" href="http://sts.sci.uwo.ca">http://sts.sci.uwo.ca</a>
(519) 661-2111 x86882 (519) 661-3566</pre>
</body>
</html>