Re: [ovs-discuss] Unable to hotplug interface with DPDK initialized
Hi Ian I am using Intel i350 PCIe NIC. I have attached entire ovs-vswitchd.log which shows both error and success. After attaching the interface, I restarted openvswitch service and it was able to attach the interface. Regards Shriroop On 5/16/19, 7:35 AM, "Ian Stokes" wrote: On 5/15/2019 10:37 PM, Shriroop Joshi (shrirjos) via discuss wrote: > Hello ovs community > > I am trying to attach an interface (eth4-4) to a bridge (svc-br) with netdev datapath_type. Here are the steps which I follow: > 1. Load vfio-pci driver > 2. Bind vfio-pci driver to interface eth4-4 > (following steps as mentioned here: http://docs.openvswitch.org/en/latest/topics/dpdk/phy/#dpdk-binding-nics) > 3. Hotplug this interface to DPDK bridge: > # ovs-vsctl add-port svc-br eth4-4 -- set interface eth4-4 type=dpdk options:dpdk-devargs=:af:00.3 > (following steps as mentioned here: http://docs.openvswitch.org/en/latest/topics/dpdk/phy/#hotplugging) > > After completing these steps, I see that it shows 'Error attaching device ':af:00.3' to DPDK' error. > Here are the error logs: > 2019-05-15T21:11:20.663Z|00227|dpdk|INFO|EAL: PCI device :af:00.3 on NUMA socket 1 > 2019-05-15T21:11:20.663Z|00228|dpdk|INFO|EAL: probe driver: 8086:1521 net_e1000_igb > 2019-05-15T21:11:20.663Z|00229|dpdk|ERR|EAL: Driver cannot attach the device (:af:00.3) > 2019-05-15T21:11:20.663Z|00230|netdev_dpdk|WARN|Error attaching device ':af:00.3' to DPDK > 2019-05-15T21:11:20.663Z|00231|netdev|WARN|eth4-4: could not set configuration (Invalid argument) > I tried to reproduce this on my local system but could not. What model HW NIC are you attempting to hotplug out of interest? Also could you provide the full log for when OVS fails to hotplug as well as when it succeeds? I'd be interested in seeing the OVS configuration commands passed for DPDK. Ian > I noticed that restarting openvswitch solves this issue, and I can see the interface attached to bridge after restart. > Here is the snippet from logs during restart: > 2019-05-15T21:14:54.172Z|00078|dpdk|INFO|EAL: PCI device :af:00.3 on NUMA socket 1 > 2019-05-15T21:14:54.172Z|00079|dpdk|INFO|EAL: probe driver: 8086:1521 net_e1000_igb > 2019-05-15T21:14:54.174Z|00080|dpdk|INFO|EAL: using IOMMU type 1 (Type 1) > > Am I missing any step? Openvswitch documentation does not specify anything else. > > # ovs-vswitchd --version > ovs-vswitchd (Open vSwitch) 2.9.3 > DPDK 17.11.0 > > Regards, > Shriroop > > > > > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > ovs-vswitchd.log Description: ovs-vswitchd.log ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] OVS - QEMU unable to create vhostuserclient socket at /var/run/openvswitch
Hi Ian,
Upgraded QEMU version to 2.10.0(qemu-kvm-ev-2.10.0-21.el7_5.7.1)
Changed /etc/libvirt/qemu.conf
user = "root"
group = "root"
And added following lines to guest XML definition:
Still getting same error:
2019-05-16T16:07:27.921191Z qemu-kvm: -chardev
socket,id=charnet2,path=/var/run/openvswitch/vhost0,server: Failed to bind
socket to /var/run/openvswitch/vhost0: Permission denied
2019-05-16 16:07:28.140+: shutting down, reason=failed
*Joan Vidal*
*OmniAccess*
-Mensaje original-
De: Ian Stokes
Enviado el: 16 May 2019 16:33
Para: Joan Vidal ; ovs-discuss@openvswitch.org
Asunto: Re: [ovs-discuss] OVS - QEMU unable to create vhostuserclient socket at
/var/run/openvswitch
On 5/16/2019 3:04 PM, Joan Vidal wrote:
> Hi,
>
> I'm trying to use OVS-DPDK vhostuserclient ports with a qemu guest on
> a CentOS host.
>
> QEMU guest fails to start with the following error:
>
> error: internal error: process exited while connecting to monitor:
> 2019-05-16T13:15:27.481680Z qemu-kvm: -chardev
> socket,id=charnet2,path=/var/run/openvswitch/vhost0,server: Failed to
> bind socket: Permission denied 2019-05-16T13:15:27.482078Z qemu-kvm:
> -chardev
> socket,id=charnet2,path=/var/run/openvswitch/vhost0,server: chardev:
> opening backend "socket" failed
>
>
> Seems to be an issue with qemu-kvm permission to create the sockets in
> /var/run/openvswitch Followed this article
> https://www.redhat.com/en/blog/ovs-dpdk-migrating-vhostuser-socket-mod
> e-red-hat-openstack
>
> But is showing same error. Even running qemu-kvm and openvswitch with
> root is still returning Permission denied.
>
>
> This is the system configuration:
>
> --
> Software versions:
>
> (Host) CentOS Linux release 7.6.1810 (Core)
> (Guest) CentOS Linux release 7.4.1708 (Core) QEMU emulator version
> 1.5.3 (qemu-kvm-1.5.3-160.el7_6.1)
The minimum QEMU version recommended for use with vhostuserclient is QEMU 2.7
(See OVS Documentation below).
http://docs.openvswitch.org/en/latest/topics/dpdk/vhost-user/#vhost-user-vs-vhost-user-client
Do you see the same issue when using QEMU 2.7?
Also from below it looks like you are using libvirt to configure QEMU?
If so have you followed the steps outlined in the link below
http://docs.openvswitch.org/en/latest/topics/dpdk/vhost-user/#adding-vhost-user-ports-to-the-guest-libvirt
Ian
> ovs-vswitchd (Open vSwitch) 2.11.1
> DPDK 18.11.0
>
>
> --
> OVS configuration
>
>
> #ovs-vsctl show
> 462375d2-8f6a-4a72-ad49-af8c00720da9
> Bridge br-subscriber
> Port br-subscriber
> Interface br-subscriber
> type: internal
> Port "ens1f0"
> Interface "ens1f0"
> type: dpdk
> options: {dpdk-devargs=":81:00.0"}
> Port "vhost0"
> Interface "vhost0"
> type: dpdkvhostuserclient
> options:
> {vhost-server-path="/var/run/openvswitch/vhost0"}
> Bridge br-internet
> Port br-internet
> Interface br-internet
> type: internal
> Port "vhost1"
> Interface "vhost1"
> type: dpdkvhostuserclient
> options:
> {vhost-server-path="/var/run/openvswitch/vhost1"}
> Port "ens1f1"
> Interface "ens1f1"
> type: dpdk
> options: {dpdk-devargs=":81:00.1"}
> ovs_version: "2.11.1"
>
> #ovs-vsctl get Open_vSwitch . other_config {dpdk-init="true",
> dpdk-socket-mem="0,2048", pmd-cpu-mask="0x02000200"}
>
>
> #cat /etc/sysconfig/openvswitch
> OPTIONS=""
> OVS_USER_ID="openvswitch:hugetlbfs"
>
>
> # ls -la /var/run/openvswitch/
> total 12
> drwxrwsr-x. 3 openvswitch hugetlbfs 260 May 16 12:00 .
> drwxr-xr-x. 29 root root 920 May 16 12:14 ..
> srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 br-internet.mgmt
> srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00
> br-internet.snoop srwxr-x---. 1 openvswitch hugetlbfs 0 May 16
> 12:00 br-subscriber.mgmt srwxr-x---. 1 openvswitch hugetlbfs 0 May
> 16 12:00 br-subscriber.snoop srwxr-x---. 1 openvswitch hugetlbfs 0
> May 16 12:00 db.sock drwx--. 3 openvswitch hugetlbfs 60 May 16
> 12:00 dpdk srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00
> ovsdb-server.21194.ctl -rw-r--r--. 1 openvswitch hugetlbfs 6 May 16
> 12:00 ovsdb-server.pid srwxr-x---. 1 openvswitch hugetlbfs 0 May 16
> 12:00 ovs-vswitchd.21250.ctl -rw-r--r--. 1 openvswitch hugetlbfs 6
> May 16 12:00 ovs-vswitchd.pid -rw-r--r--. 1 root root 41
> May 16 12:00 useropts
>
>
> --
> qemu configuration
>
> #cat /etc/libvirt/qemu.conf
> user = "qemu"
>
Re: [ovs-discuss] Unable to hotplug interface with DPDK initialized
On 5/15/2019 10:37 PM, Shriroop Joshi (shrirjos) via discuss wrote: Hello ovs community I am trying to attach an interface (eth4-4) to a bridge (svc-br) with netdev datapath_type. Here are the steps which I follow: 1. Load vfio-pci driver 2. Bind vfio-pci driver to interface eth4-4 (following steps as mentioned here: http://docs.openvswitch.org/en/latest/topics/dpdk/phy/#dpdk-binding-nics) 3. Hotplug this interface to DPDK bridge: # ovs-vsctl add-port svc-br eth4-4 -- set interface eth4-4 type=dpdk options:dpdk-devargs=:af:00.3 (following steps as mentioned here: http://docs.openvswitch.org/en/latest/topics/dpdk/phy/#hotplugging) After completing these steps, I see that it shows 'Error attaching device ':af:00.3' to DPDK' error. Here are the error logs: 2019-05-15T21:11:20.663Z|00227|dpdk|INFO|EAL: PCI device :af:00.3 on NUMA socket 1 2019-05-15T21:11:20.663Z|00228|dpdk|INFO|EAL: probe driver: 8086:1521 net_e1000_igb 2019-05-15T21:11:20.663Z|00229|dpdk|ERR|EAL: Driver cannot attach the device (:af:00.3) 2019-05-15T21:11:20.663Z|00230|netdev_dpdk|WARN|Error attaching device ':af:00.3' to DPDK 2019-05-15T21:11:20.663Z|00231|netdev|WARN|eth4-4: could not set configuration (Invalid argument) I tried to reproduce this on my local system but could not. What model HW NIC are you attempting to hotplug out of interest? Also could you provide the full log for when OVS fails to hotplug as well as when it succeeds? I'd be interested in seeing the OVS configuration commands passed for DPDK. Ian I noticed that restarting openvswitch solves this issue, and I can see the interface attached to bridge after restart. Here is the snippet from logs during restart: 2019-05-15T21:14:54.172Z|00078|dpdk|INFO|EAL: PCI device :af:00.3 on NUMA socket 1 2019-05-15T21:14:54.172Z|00079|dpdk|INFO|EAL: probe driver: 8086:1521 net_e1000_igb 2019-05-15T21:14:54.174Z|00080|dpdk|INFO|EAL: using IOMMU type 1 (Type 1) Am I missing any step? Openvswitch documentation does not specify anything else. # ovs-vswitchd --version ovs-vswitchd (Open vSwitch) 2.9.3 DPDK 17.11.0 Regards, Shriroop ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] OVS - QEMU unable to create vhostuserclient socket at /var/run/openvswitch
On 5/16/2019 3:04 PM, Joan Vidal wrote:
Hi,
I'm trying to use OVS-DPDK vhostuserclient ports with a qemu guest on a
CentOS host.
QEMU guest fails to start with the following error:
error: internal error: process exited while connecting to monitor:
2019-05-16T13:15:27.481680Z qemu-kvm: -chardev
socket,id=charnet2,path=/var/run/openvswitch/vhost0,server: Failed to
bind socket: Permission denied
2019-05-16T13:15:27.482078Z qemu-kvm: -chardev
socket,id=charnet2,path=/var/run/openvswitch/vhost0,server: chardev:
opening backend "socket" failed
Seems to be an issue with qemu-kvm permission to create the sockets in
/var/run/openvswitch
Followed this article
https://www.redhat.com/en/blog/ovs-dpdk-migrating-vhostuser-socket-mode-red-hat-openstack
But is showing same error. Even running qemu-kvm and openvswitch with
root is still returning Permission denied.
This is the system configuration:
--
Software versions:
(Host) CentOS Linux release 7.6.1810 (Core)
(Guest) CentOS Linux release 7.4.1708 (Core)
QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-160.el7_6.1)
The minimum QEMU version recommended for use with vhostuserclient is
QEMU 2.7 (See OVS Documentation below).
http://docs.openvswitch.org/en/latest/topics/dpdk/vhost-user/#vhost-user-vs-vhost-user-client
Do you see the same issue when using QEMU 2.7?
Also from below it looks like you are using libvirt to configure QEMU?
If so have you followed the steps outlined in the link below
http://docs.openvswitch.org/en/latest/topics/dpdk/vhost-user/#adding-vhost-user-ports-to-the-guest-libvirt
Ian
ovs-vswitchd (Open vSwitch) 2.11.1
DPDK 18.11.0
--
OVS configuration
#ovs-vsctl show
462375d2-8f6a-4a72-ad49-af8c00720da9
Bridge br-subscriber
Port br-subscriber
Interface br-subscriber
type: internal
Port "ens1f0"
Interface "ens1f0"
type: dpdk
options: {dpdk-devargs=":81:00.0"}
Port "vhost0"
Interface "vhost0"
type: dpdkvhostuserclient
options: {vhost-server-path="/var/run/openvswitch/vhost0"}
Bridge br-internet
Port br-internet
Interface br-internet
type: internal
Port "vhost1"
Interface "vhost1"
type: dpdkvhostuserclient
options: {vhost-server-path="/var/run/openvswitch/vhost1"}
Port "ens1f1"
Interface "ens1f1"
type: dpdk
options: {dpdk-devargs=":81:00.1"}
ovs_version: "2.11.1"
#ovs-vsctl get Open_vSwitch . other_config
{dpdk-init="true", dpdk-socket-mem="0,2048", pmd-cpu-mask="0x02000200"}
#cat /etc/sysconfig/openvswitch
OPTIONS=""
OVS_USER_ID="openvswitch:hugetlbfs"
# ls -la /var/run/openvswitch/
total 12
drwxrwsr-x. 3 openvswitch hugetlbfs 260 May 16 12:00 .
drwxr-xr-x. 29 root root 920 May 16 12:14 ..
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 br-internet.mgmt
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 br-internet.snoop
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 br-subscriber.mgmt
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 br-subscriber.snoop
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 db.sock
drwx--. 3 openvswitch hugetlbfs 60 May 16 12:00 dpdk
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 ovsdb-server.21194.ctl
-rw-r--r--. 1 openvswitch hugetlbfs 6 May 16 12:00 ovsdb-server.pid
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 ovs-vswitchd.21250.ctl
-rw-r--r--. 1 openvswitch hugetlbfs 6 May 16 12:00 ovs-vswitchd.pid
-rw-r--r--. 1 root root 41 May 16 12:00 useropts
--
qemu configuration
#cat /etc/libvirt/qemu.conf
user = "qemu"
group = "hugetlbfs"
Vhostuser parameters used when starting guest with /usr/libexec/qemu-kvm
-chardev socket,id=charnet2,path=/var/run/openvswitch/vhost0,server
-netdev vhost-user,chardev=charnet2,id=hostnet2 -device
virtio-net-pci,netdev=hostnet2,id=net2,mac=0c:c4:7a:ea:4b:b2,bus=pci.0,addr=0x5
-chardev socket,id=charnet3,path=/var/run/openvswitch/vhost1,server
-netdev vhost-user,chardev=charnet3,id=hostnet3 -device
virtio-net-pci,netdev=hostnet3,id=net3,mac=0c:c4:7a:ea:4b:b3,bus=pci.0,addr=0x6
--
Logs
/var/log/openvswitch/ovs-vswitchd.log
2019-05-16T13:05:23.421Z|00142|dpdk|INFO|VHOST_CONFIG: vhost-user
client: socket created, fd: 62
2019-05-16T13:05:23.421Z|00143|netdev_dpdk|INFO|vHost User device
'vhost0' created in 'client' mode, using client socket
'/var/run/openvswitch/vhost0'
2019-05-16T13:05:23.421Z|00144|dpdk|WARN|VHOST_CONFIG: failed to connect
to /var/run/openvswitch/vhost0: No such file or directory
2019-05-16T13:05:23.421Z|00145|dpdk|INFO|VHOST_CONFIG:
/var/run/openvswitch/vhost0: reconnecting...
2019-05-16T13:05:23.421Z|00146|dpif_netdev|INFO|Core 9 on
[ovs-discuss] OVS - QEMU unable to create vhostuserclient socket at /var/run/openvswitch
Hi,
I'm trying to use OVS-DPDK vhostuserclient ports with a qemu guest on a CentOS
host.
QEMU guest fails to start with the following error:
error: internal error: process exited while connecting to monitor:
2019-05-16T13:15:27.481680Z qemu-kvm: -chardev
socket,id=charnet2,path=/var/run/openvswitch/vhost0,server: Failed to bind
socket: Permission denied
2019-05-16T13:15:27.482078Z qemu-kvm: -chardev
socket,id=charnet2,path=/var/run/openvswitch/vhost0,server: chardev: opening
backend "socket" failed
Seems to be an issue with qemu-kvm permission to create the sockets in
/var/run/openvswitch
Followed this article
https://www.redhat.com/en/blog/ovs-dpdk-migrating-vhostuser-socket-mode-red-hat-openstack
But is showing same error. Even running qemu-kvm and openvswitch with root is
still returning Permission denied.
This is the system configuration:
--
Software versions:
(Host) CentOS Linux release 7.6.1810 (Core)
(Guest) CentOS Linux release 7.4.1708 (Core)
QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-160.el7_6.1)
ovs-vswitchd (Open vSwitch) 2.11.1
DPDK 18.11.0
--
OVS configuration
#ovs-vsctl show
462375d2-8f6a-4a72-ad49-af8c00720da9
Bridge br-subscriber
Port br-subscriber
Interface br-subscriber
type: internal
Port "ens1f0"
Interface "ens1f0"
type: dpdk
options: {dpdk-devargs=":81:00.0"}
Port "vhost0"
Interface "vhost0"
type: dpdkvhostuserclient
options: {vhost-server-path="/var/run/openvswitch/vhost0"}
Bridge br-internet
Port br-internet
Interface br-internet
type: internal
Port "vhost1"
Interface "vhost1"
type: dpdkvhostuserclient
options: {vhost-server-path="/var/run/openvswitch/vhost1"}
Port "ens1f1"
Interface "ens1f1"
type: dpdk
options: {dpdk-devargs=":81:00.1"}
ovs_version: "2.11.1"
#ovs-vsctl get Open_vSwitch . other_config
{dpdk-init="true", dpdk-socket-mem="0,2048", pmd-cpu-mask="0x02000200"}
#cat /etc/sysconfig/openvswitch
OPTIONS=""
OVS_USER_ID="openvswitch:hugetlbfs"
# ls -la /var/run/openvswitch/
total 12
drwxrwsr-x. 3 openvswitch hugetlbfs 260 May 16 12:00 .
drwxr-xr-x. 29 rootroot 920 May 16 12:14 ..
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 br-internet.mgmt
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 br-internet.snoop
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 br-subscriber.mgmt
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 br-subscriber.snoop
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 db.sock
drwx--. 3 openvswitch hugetlbfs 60 May 16 12:00 dpdk
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 ovsdb-server.21194.ctl
-rw-r--r--. 1 openvswitch hugetlbfs 6 May 16 12:00 ovsdb-server.pid
srwxr-x---. 1 openvswitch hugetlbfs 0 May 16 12:00 ovs-vswitchd.21250.ctl
-rw-r--r--. 1 openvswitch hugetlbfs 6 May 16 12:00 ovs-vswitchd.pid
-rw-r--r--. 1 rootroot 41 May 16 12:00 useropts
--
qemu configuration
#cat /etc/libvirt/qemu.conf
user = "qemu"
group = "hugetlbfs"
Vhostuser parameters used when starting guest with /usr/libexec/qemu-kvm
-chardev socket,id=charnet2,path=/var/run/openvswitch/vhost0,server -netdev
vhost-user,chardev=charnet2,id=hostnet2 -device
virtio-net-pci,netdev=hostnet2,id=net2,mac=0c:c4:7a:ea:4b:b2,bus=pci.0,addr=0x5
-chardev socket,id=charnet3,path=/var/run/openvswitch/vhost1,server -netdev
vhost-user,chardev=charnet3,id=hostnet3 -device
virtio-net-pci,netdev=hostnet3,id=net3,mac=0c:c4:7a:ea:4b:b3,bus=pci.0,addr=0x6
--
Logs
/var/log/openvswitch/ovs-vswitchd.log
2019-05-16T13:05:23.421Z|00142|dpdk|INFO|VHOST_CONFIG: vhost-user client:
socket created, fd: 62
2019-05-16T13:05:23.421Z|00143|netdev_dpdk|INFO|vHost User device 'vhost0'
created in 'client' mode, using client socket '/var/run/openvswitch/vhost0'
2019-05-16T13:05:23.421Z|00144|dpdk|WARN|VHOST_CONFIG: failed to connect to
/var/run/openvswitch/vhost0: No such file or directory
2019-05-16T13:05:23.421Z|00145|dpdk|INFO|VHOST_CONFIG:
/var/run/openvswitch/vhost0: reconnecting...
2019-05-16T13:05:23.421Z|00146|dpif_netdev|INFO|Core 9 on numa node 1 assigned
port 'ens1f0' rx queue 0 (measured processing cycles 123318).
2019-05-16T13:05:23.421Z|00147|dpif_netdev|INFO|Core 25 on numa node 1 assigned
port 'ens1f1' rx queue 0 (measured processing cycles 46293).
2019-05-16T13:05:23.421Z|00148|dpif_netdev|WARN|There's no available
(non-isolated) pmd thread on numa node 0. Queue 0 on port 'vhost0' will be
assigned to the pmd on core 25 (numa node 1). Expect reduced performance.
2019-05-16T13:05:23.421Z|00149|bridge|INFO|bridge br-internet: added interface
vhost0 on port 3
Re: [ovs-discuss] how to forward all traffic from vm with dst 169.254.169.254 to local compute node
чт, 16 мая 2019 г. в 14:57, Daniel Alvarez Sanchez : > > In OpenStack we do this via a DHCP static route [0]. Then we use an > OVN 'localport' in the hypervisor inside a namespace to handle the > requests. > > [0] > https://opendev.org/openstack/networking-ovn/src/branch/stable/stein/networking_ovn/common/ovn_client.py#L1524 > Thank you, why namespace needed? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] how to forward all traffic from vm with dst 169.254.169.254 to local compute node
In OpenStack we do this via a DHCP static route [0]. Then we use an OVN 'localport' in the hypervisor inside a namespace to handle the requests. [0] https://opendev.org/openstack/networking-ovn/src/branch/stable/stein/networking_ovn/common/ovn_client.py#L1524 On Thu, May 16, 2019 at 1:13 PM Vasiliy Tolstov wrote: > > Hi! I need to route all traffic (tcp) from vm to metadata ip address > 169.254.169.254 to host server. Ideally i need to know what vm is > going to this address. > I know that via ovs i can create flow for this stuff, does it possible > something like this with ovn? > > -- > Vasiliy Tolstov, > e-mail: v.tols...@selfip.ru > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] how to forward all traffic from vm with dst 169.254.169.254 to local compute node
Hi! I need to route all traffic (tcp) from vm to metadata ip address 169.254.169.254 to host server. Ideally i need to know what vm is going to this address. I know that via ovs i can create flow for this stuff, does it possible something like this with ovn? -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] How to use group bucket actions with specific controller id? Is it possible?
Hi. I am implementing network control logic with an open source ryu controller. When I search the internet, I can use the controller id in the *T**h**e* *c* *o**n**t**r**o**l**l**e**r* *a**c**t**i**o**n *part of ovs-ofctl manual. > http://www.openvswitch.org/support/dist-docs/ovs-actions.7.html I want to use it with the *group entry*. like below. $ ovs-ofctl -O OpenFlow13 add-flow br0 table=1,priority=100(...etc..),actions=group:1 $ ovs-ofctl -O OpenFlow13 add-group br0 "group_id=1, type=select, bucket=controller(reason=no_match,max_len=65530,id=2)" In other words, I want to send packets to the ryu controller with a specific controller id through the action buckets in the group entry. I knew how to specify the ryu controller id in the source via the mail archive link below. > https://www.mail-archive.com/ryu-devel@lists.sourceforge.net/msg13807.html It works when the controller id is added to the actions of the actual table flow instead of group. but It doesn't work with group bucket function.. :( ovs can not pass to a controller with a specific id. only the default controller option without parameters works like below. > group_id=1,type=select,bucket=actions=CONTROLLER:65535 Does ovs group bucket action can send to specific controller with id? I want to insert serveral controller id (actions) with one bucket I would like you to introduce me if there is a method. p.s * Verison info ubuntu 16.04 ovs-ofctl (Open vSwitch) 2.5.5 OpenFlow versions 0x1:0x4 -- Thanks, yoonhee.choi ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
