[openstack-dev] Ocata - Networking OVN - option "neutron_sync_mode = repair" looks broken

Martinx - ジェームズ thiagocmartinsc at gmail.com
Wed May 10 14:49:53 UTC 2017


 I'm playing with Networking OVN, and planning to deploy it into production
in a couple weeks.

 After deploying everything and starting using OVN, with Floating IPs,
multiple compute nodes and everything else, I can say that it looks
awesome! Way better than "neutron-*-agents".

 However, I noted that after running:

 systemctl restart neutron-server

 Literally ALL my stacks, on all projects, becomes unreachable!!!

 After double checking everything, I did one single change in my
ml2_conf.ini, from:

neutron_sync_mode = repair


# neutron_sync_mode = off

 Then, problem solved!

 Now, I can restart the neutron-server without any problems!

 Deep inside me, I'm freaking out with this... Because this whole OVN
solution looks very, very delicate. I mean, what to do if this happens

 Ask ALL my customers to rebuild their stacks?!

 How to REALLY repair OVN?

 Now that the problem is solved, I'll keep trying to use and stress test it
even more but, I'm losing confidence on Networking OVN on its current state.

 I'm using Ubuntu 16.04 with Kernel 4.8 (HWE), plus Ocata from Cloud

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170510/fa00db02/attachment.html>

More information about the OpenStack-dev mailing list