[ovs-discuss] how to do force-reload-kmod with systemd script on Centos 7.x

Hi all, I'm trying to find the equivalent to /etc/init.d/openvswitch force-reload-kmod in the systemd based scripts. How do I use a command similar to "service openvswitch " or "systemctl openvswitch" to do it? I understand that systemd script only supports limited operations (start, reload,

Re: [ovs-discuss] how to do force-reload-kmod with systemd script on Centos 7.x

On 4/6/2018 11:20 AM, Martin Xu wrote: Hi all, I'm trying to find the equivalent to /etc/init.d/openvswitch force-reload-kmod in the systemd based scripts. How do I use a command similar to "service openvswitch " or "systemctl openvswitch" to do it? I understand that systemd script only

[ovs-discuss] Fwd: how to do force-reload-kmod with systemd script on Centos 7.x

Hi all, I'm trying to find the equivalent to /etc/init.d/openvswitch force-reload-kmod in the systemd based scripts. How do I use a command similar to "service openvswitch " or "systemctl openvswitch" to do it? I understand that systemd script only supports limited operations (start, reload,

Re: [ovs-discuss] [openvswitch 2.9.90] Unable to use literal in nested output of learn action

Heh, after sending that msg, I did a little digging in the code [1] and doc and it seems clear that integer literals are just not supported as a value for the output action name. I imagine that in order to handle that, that code section would need to be extended to perform a

Re: [ovs-discuss] [openvswitch 2.9.90] Unable to use literal in nested output of learn action

The binary encoding of the "learn" action just doesn't support an "output to immediate" action, so some kind of different approach is needed. On Fri, Apr 06, 2018 at 05:57:14PM -0400, Flavio Fernandes wrote: > > Heh, after sending that msg, I did a little digging in the code [1] and doc > and

Re: [ovs-discuss] Is there an option to disable metadata propagation on patch ports?

Thanks Ben. So then the flow struct, along with its members excluding metadata, tunnel and regs propagate, correct? 2018-04-05 21:30 GMT+02:00 Ben Pfaff : > compose_output_action__(), in ofproto/ofproto-dpif-xlate.c, clears > metadata for patch port traversals in the block that

Re: [ovs-discuss] Is there an option to disable metadata propagation on patch ports?

Yes. On Fri, Apr 06, 2018 at 12:49:21PM +0200, Alan Kayahan wrote: > Thanks Ben. So then the flow struct, along with its members excluding > metadata, tunnel and regs propagate, correct? > > > 2018-04-05 21:30 GMT+02:00 Ben Pfaff : > > > compose_output_action__(), in

[ovs-discuss] open vswitch with userspace datapath

Hi all, I am using ovs with userspace datapath, but I couldn't create many queues on each switch's port to control the transmission rate where ovs uses just the transmission rate of the first queue even I defined QoS rules to use other queues but didn't work. do you think that ovs with userspace

Re: [ovs-discuss] OVS 2.9.0: priority=0 actions=CONTROLLER flow counts but doesn't output packets to the controller

On Tue, Mar 06, 2018 at 11:20:40AM -0800, Ben Pfaff wrote: > On Tue, Mar 06, 2018 at 06:54:30AM +, Josh Bailey via discuss wrote: > > Hoping I'm missing something obvious! > > > > I have a flow like this: > > > > $ grep CONTROLLER sab-dump-flows.log > > cookie=0x5adc15c0, duration=63.446s,