ok. That can work.. I believe I found the source of the issue on that as
well. the RHEL ifup / ifdown scripts call ovs-vsctl directly w/o a time
out set. If you'd like I can submit a patch for this and throw in a
default of 30 seconds or something inside it.
-b
On Mon, May 7, 2012 at 2:50
Sounds like a good idea, thanks.
On Mon, May 07, 2012 at 07:07:11PM -0700, bkruger wrote:
> ok. That can work.. I believe I found the source of the issue on that as
> well. the RHEL ifup / ifdown scripts call ovs-vsctl directly w/o a time
> out set. If you'd like I can submit a patch for thi
I'd like to configure OVS using OpenFlow+Nicira extensions to push two VLAN
tags, to load-balance at higher levels of a multi-rooted tree on physical
switches that only support OpenFlow 1.0 in firmware and so don't support
ECMP. Double-stacked VLANs aren't strictly necessary; double IP-in-IP or
VL
On Mon, May 07, 2012 at 02:49:15PM -0700, bkruger wrote:
> I notice that if the db is unreachable, it attempts to reconnect. I'm
> looking at the code (not a C programmer, but can read some) and I see that
> tries to reconnect infinitely. Is there a place where this can be set to
> give up afte
Just curious,
I notice that if the db is unreachable, it attempts to reconnect. I'm
looking at the code (not a C programmer, but can read some) and I see that
tries to reconnect infinitely. Is there a place where this can be set to
give up after X attempts? If you're on a RHEL box at least,
You say, "I am trying to associate each rule in the kernel's flow
table with additional metadata." OK, great, we're finally getting to
learn about your actual goal. So, tell us, what extra metadata do you
want?
On Sun, May 06, 2012 at 09:23:38AM +0800, Danny Y. Huang wrote:
> @Ben: Based on the
