Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect

2014-09-26 Thread Gur Stavi
I will try but I am not too familiar with OVS internals. Hope I can find existing cleanup code to reuse. From: Ben Pfaff Sent: Friday, September 26, 2014 8:39 PM To: Gur Stavi Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] Meter IDs and meter

Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect

2014-09-24 Thread Gur Stavi
ction-mode=out-of-band ovs-vswitchd unix:/var/run/openvswitch/db.sock --pidfile --detach Thanks, Gur -Original Message- From: Ben Pfaff [mailto:b...@nicira.com] Sent: Tuesday, September 23, 2014 17:50 To: Gur Stavi Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] Meter IDs and

Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect

2014-09-24 Thread Gur Stavi
.sock --pidfile --detach Thanks, Gur -Original Message- From: Ben Pfaff [mailto:b...@nicira.com] Sent: Tuesday, September 23, 2014 17:50 To: Gur Stavi Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect So you enabled fail-open mode then? You

Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect

2014-09-23 Thread Gur Stavi
when it loses connection to the controller. Am I missing something? Thanks, Gur -Original Message- From: Ben Pfaff [mailto:b...@nicira.com] Sent: Monday, September 22, 2014 20:08 To: Gur Stavi Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect

Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect

2014-09-22 Thread Gur Stavi
can do about changing OpenFlow specification. Thanks, Gur -Original Message- From: Ben Pfaff [mailto:b...@nicira.com] Sent: Monday, September 22, 2014 20:08 To: Gur Stavi Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] Meter IDs and meter cleanup on disconnect On Sun, Sep 21, 2014

[ovs-discuss] Meter IDs and meter cleanup on disconnect

2014-09-20 Thread Gur Stavi
Hi all, I have 2 questions about meters: If OVS loses connection to controller it delete active flows but does not delete active meters. Shouldn't meters be deleted as well. Meters are stored in an array in ofproto where meter_id is used as an index into the array. The datapath need to pre-dec

[ovs-discuss] Is it allowed to delete a meter that is used by active flows?

2014-07-29 Thread Gur Stavi
Hello, The 'meter_del' callback of ofproto_class does not have a return value. What should happen when there is an attempt to delete a meter that is used by active flows? Thanks, Gur [E-Banner] The contents of this message, together with any attachments

[ovs-discuss] 'get_next_hop' is called without a scope

2014-07-23 Thread Gur Stavi
The get_next_hop in netdev_class is activated without any scope (netdev or ofproto). If a session has multiple active bridges, each with its own set of netdevs, it should maintain a separate next hop table for each bridge. On a call to get_next_hop, how should the callee know on which bridge the

Re: [ovs-discuss] Did anyone manage to build and use ovs with SHARED libraries

2014-07-17 Thread Gur Stavi
Yes, With static libraries I am able to bring up ovs-vswitchd and see it in an OpenDaylight controller. Regards, Gur From: Gurucharan Shetty [mailto:shet...@nicira.com] Sent: Wednesday, July 16, 2014 17:53 To: Gur Stavi Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] Did anyone manage

[ovs-discuss] Did anyone manage to build and use ovs with SHARED libraries

2014-07-15 Thread Gur Stavi
Hi, I tried building ovs with shared libraries to reduce the size of the executables. Mainly I would like to generate libopenvswitch.so instead of libopenvswitch.a. I added --enable-shared to the 'configure' command and also tried some other approaches. The 'make' was successful. ovsdb-server s

[ovs-discuss] Warning on "unsupported bfd"

2014-07-13 Thread Gur Stavi
If bfd is unsupported by ofproto class an 'unsupported' warning is displayed. No such warning is displayed for other unsupported protocols. Proposed fix: In the function: ofproto_port_set_bfd Change: if (error) { VLOG_WARN(...) To: if (error && error != EOPNOTSUPP) { VLOG_WARN