11:07 a.m.
On Tue, 10 Apr 2018 11:48:50 +0000
Vasily Lamykin <vasily.lamykin(a)MegaFon.ru> wrote:
Hi, all
I try to configure ovn in engine, what I do by step:
1.Created network test1 with external ovn provider on engine1
2.Created subnet for this network
3.Connect engine2 to engine1 ovn provider(through “add provider”)
4.Successfully imported network test1 on engine2
5.I see subnet’s on all engines
6.Created 2 VM with nic in network test1 on both engines
7.Assigned ips from one subnet(192.168.10.0/24) to all VMs
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.
Expected results: VM from engine1 can ping VM from engine2 in same
subnet in ovn network test1
Now, I don’t have ping ability between two VMs
ovn-nbctl show
switch 54beaa3c-de8f-435f-b132-8542ddeb4b4b (test-ovn-phys)
port b580d44d-e616-42dd-9e17-63983d0f91e5
addresses: ["00:1a:4a:16:01:01 dynamic"]
port cfd5f32c-00a7-419e-8bbe-27518a4c74dc
addresses: ["00:1a:4a:16:01:00 dynamic"]
node from engine1 with testVM
vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master ovs-system state UNKNOWN qlen 1000 link/ether
fe:1a:4a:16:01:01 brd ff:ff:ff:ff:ff:ff inet6
fe80::fc1a:4aff:fe16:101/64 scope link valid_lft forever
preferred_lft forever
node from engine2 with testVM
vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master ovs-system state UNKNOWN qlen 1000 link/ether
fe:1a:4a:16:01:00 brd ff:ff:ff:ff:ff:ff inet6
fe80::fc1a:4aff:fe16:100/64 scope link valid_lft forever
preferred_lft forever
How can I do ovn connection? What I did wrong?
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.
________________________________
Информация в этом сообщении предназначена исключительно для
конкретных лиц, которым она адресована. В сообщении может содержаться
конфиденциальная информация, которая не может быть раскрыта или
использована кем-либо, кроме адресатов. Если вы не адресат этого
сообщения, то использование, переадресация, копирование или
распространение содержания сообщения или его части незаконно и
запрещено. Если Вы получили это сообщение ошибочно, пожалуйста,
незамедлительно сообщите отправителю об этом и удалите со всем
содержимым само сообщение и любые возможные его копии и приложения.
The information contained in this communication is intended solely
for the use of the individual or entity to whom it is addressed and
others authorized to receive it. It may contain confidential or
legally privileged information. The contents may not be disclosed or
used by anyone other than the addressee. If you are not the intended
recipient(s), any use, disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it is prohibited
and may be unlawful. If you have received this communication in error
please notify us immediately by responding to this email and then
delete the e-mail and all attachments and any copies thereof.
-----