[ovs-discuss] [OVN] New OVN website!

2020-03-16 Thread Daniel Alvarez Sanchez
Hi folks,

www.ovn.org is alive! Not really full of contents yet but PRs are welcome
[0].
Thanks Miguel (CC'ed) and everybody who helped.

As a second step it'd be awesome to have the manpages rendered there with
updated versions. IIUC from Ilya (CC'ed as well) we need to have
docs.ovn.org created and hosted at readthedocs.org. I'm not really familiar
with this process but I guess we can try to mimic what OVS was doing so far?

Thanks a lot,
Daniel

[0] https://github.com/ovn-org/ovn-website/pulls
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


Re: [ovs-discuss] Open-v-switch flow issue.

2020-03-16 Thread Numan Siddique
On Wed, Mar 11, 2020 at 2:08 AM Vadim M Basyrov  wrote:
>
> Hello!
>
> I write to you because I can’t solve one issue regarding open-v-switch.
>
> We have the OpenStack deployment – version Queens.
>

In the case of openstack, neutron ovs agent programs the flows right ?
I think you should investigate whether neutron ovs agent is
programming the required flows or not.

Thanks
Numan

> 11 nodes – 3 control nodes and 8 compute nodes.
>
> There are seven compute nodes with ovs-vswitchd (Open vSwitch) 2.9.0 and last 
> one compute node with ovs-vswitchd (Open vSwitch) 2.9.5 (from the start we 
> had ovs-vswitchd (Open vSwitch) 2.9.0 like as on other nodes).
>
> We upgraded ovs-vswitchd (Open vSwitch) 2.9.5 on the last compute node for 
> test and wanted to figure out that this problem will be persists or not.
>
>
> When we launch virtual machine on first seven nodes, virtual machine works 
> and gets ip-addresses from dhcp without problem.
>
> But when we launch virtual machine or migrate virtual machine on the last 
> compute node virtual machine does not get ip-addresses from dhcp.
>
>
> We investigated this problem and found one interesting moment.
>
> On the first seven nodes after creating virtual machine we can see correct 
> dump flow for private network of virtual machine.
>
>
> Correct dump:
>
> root@dc2-compute03:~# ovs-ofctl dump-flows br-tun | grep 0x10057
>
> cookie=0x7e0b101c14974b46, duration=8712088.227s, table=4, 
> n_packets=58210459, n_bytes=333529723572, idle_age=39, hard_age=65534, 
> priority=1,tun_id=0x10057 actions=mod_vlan_vid:3,resubmit(,9)
>
>  cookie=0x7e0b101c14974b46, duration=2305838.428s, table=20, n_packets=0, 
> n_bytes=0, idle_age=65534, hard_age=65534, 
> priority=2,dl_vlan=3,dl_dst=fa:16:3e:f7:e1:46 
> actions=strip_vlan,load:0x10057->NXM_NX_TUN_ID[],output:6
>
>  cookie=0x7e0b101c14974b46, duration=2305820.317s, table=20, n_packets=54, 
> n_bytes=6045, idle_age=65534, hard_age=65534, 
> priority=2,dl_vlan=3,dl_dst=fa:16:3e:10:65:23 
> actions=strip_vlan,load:0x10057->NXM_NX_TUN_ID[],output:3
>
>  cookie=0x7e0b101c14974b46, duration=2305811.544s, table=20, n_packets=0, 
> n_bytes=0, idle_age=65534, hard_age=65534, 
> priority=2,dl_vlan=3,dl_dst=fa:16:3e:2c:92:0d 
> actions=strip_vlan,load:0x10057->NXM_NX_TUN_ID[],output:10
>
>  cookie=0x7e0b101c14974b46, duration=2305795.834s, table=20, n_packets=45, 
> n_bytes=4175, idle_age=65534, hard_age=65534, 
> priority=2,dl_vlan=3,dl_dst=fa:16:3e:ea:d7:e4 
> actions=strip_vlan,load:0x10057->NXM_NX_TUN_ID[],output:4
>
>  cookie=0x7e0b101c14974b46, duration=2305795.238s, table=20, n_packets=36, 
> n_bytes=1865, idle_age=65534, hard_age=65534, 
> priority=2,dl_vlan=3,dl_dst=fa:16:3e:65:23:5d 
> actions=strip_vlan,load:0x10057->NXM_NX_TUN_ID[],output:5
>
>  cookie=0x7e0b101c14974b46, duration=1027284.390s, table=20, n_packets=0, 
> n_bytes=0, idle_age=65534, hard_age=65534, 
> priority=2,dl_vlan=3,dl_dst=fa:16:3e:90:b8:73 
> actions=strip_vlan,load:0x10057->NXM_NX_TUN_ID[],output:8
>
>  cookie=0x7e0b101c14974b46, duration=1027268.690s, table=20, n_packets=0, 
> n_bytes=0, hard_timeout=300, idle_age=65534, hard_age=38, 
> priority=1,vlan_tci=0x0003/0x0fff,dl_dst=fa:16:3e:90:b8:73 
> actions=load:0->NXM_OF_VLAN_TCI[],load:0x10057->NXM_NX_TUN_ID[],output:8
>
>  cookie=0x7e0b101c14974b46, duration=23829.098s, table=20, n_packets=220, 
> n_bytes=14712, hard_timeout=300, idle_age=166, hard_age=124, 
> priority=1,vlan_tci=0x0003/0x0fff,dl_dst=fa:16:3e:b6:4d:f1 
> actions=load:0->NXM_OF_VLAN_TCI[],load:0x10057->NXM_NX_TUN_ID[],output:3
>
>  cookie=0x7e0b101c14974b46, duration=131.880s, table=20, n_packets=0, 
> n_bytes=0, hard_timeout=300, idle_age=131, 
> priority=1,vlan_tci=0x0003/0x0fff,dl_dst=fa:16:3e:10:65:23 
> actions=load:0->NXM_OF_VLAN_TCI[],load:0x10057->NXM_NX_TUN_ID[],output:3
>
>  cookie=0x7e0b101c14974b46, duration=131.880s, table=20, n_packets=0, 
> n_bytes=0, hard_timeout=300, idle_age=131, 
> priority=1,vlan_tci=0x0003/0x0fff,dl_dst=fa:16:3e:65:23:5d 
> actions=load:0->NXM_OF_VLAN_TCI[],load:0x10057->NXM_NX_TUN_ID[],output:5
>
>  cookie=0x7e0b101c14974b46, duration=131.880s, table=20, n_packets=0, 
> n_bytes=0, hard_timeout=300, idle_age=131, 
> priority=1,vlan_tci=0x0003/0x0fff,dl_dst=fa:16:3e:ea:d7:e4 
> actions=load:0->NXM_OF_VLAN_TCI[],load:0x10057->NXM_NX_TUN_ID[],output:4
>
>  cookie=0x7e0b101c14974b46, duration=2305817.320s, table=22, n_packets=27156, 
> n_bytes=3159361, idle_age=24888, hard_age=65534, priority=1,dl_vlan=3 
> actions=strip_vlan,load:0x10057->NXM_NX_TUN_ID[],output:3,output:4,output:5,output:6,output:8,output:10
>
>
> On the last compute node after creating virtual machine we have incorrect 
> dump flow or incomplete. In this case we don’t see any “NXM_OF_VLAN_TCI” 
> output strings to MAC-addresses of DHCP.
>
>
> Incorrect dump:
>
> root@dc2-compute09:~# ovs-ofctl dump-flows br-tun | grep 0x10057
>
>  cookie=0x189ebcbc0bc4a360, duration=3006.464s, table=4, n_packets=124, 
> n_bytes=24219, idle_age=21,