Re: [ovirt-users] OVN between two different datacenters with different networks

Very big thanks, In your solution I want fix only one... " tunneling-IP is IP-of-host-of-engine-2" For me - works variant is IP of host2 , which can provides access to engine1 Василий Ламыкин Старший инженер по эксплуатации сетевых сервисов Центра управления сетью Столица Единый Центр управления сетью +7 (925) 696-1032 -----Original Message----- From: Dominik Holler [mailto:dholler@redhat.com] Sent: Tuesday, April 10, 2018 6:08 PM To: Vasily Lamykin (GNOC) <vasily.lamykin(a)MegaFon.ru&gt; Cc: users(a)ovirt.org Subject: Re: [ovirt-users] OVN between two different datacenters with different networks On Tue, 10 Apr 2018 11:48:50 +0000 Vasily Lamykin <vasily.lamykin(a)MegaFon.ru&gt; wrote: The subnet is used to configure OVN's internal DHCP server. This means you use DHCP to assign IPs to the vNICs, which is already a good test if the VM is connected as expected. Please note that per host only a single OVN central is supported! Please check via sudo ovn-sbctl show on engine1 if both hosts are connected to OVN central engine1. Probably the host of engine2 is configured to use engine2 as it's OVN central. Probable the host of engine2 has to be connected to OVN central engine1 and the tunneling interface might require some configuration. Both is handled by executing /usr/libexec/ovirt-provider-ovn/setup_ovn_controller.sh \ IP-central tunneling-IP key_file cert_file ca_file on the host. Probably IP-central is IP-of-engine1 tunneling-IP is IP-of-host-of-engine-2 and key_file cert_file ca_file has to be stolen from host of engine1 and copied in a new location on host2 and configured on host2.