Re: [ovs-discuss] Including bfd status for tunnel endpoints on ovs-vsctl show

2018-03-12 Thread Miguel Angel Ajo Pelayo
Eran was asking me if we can think of a way to get the remote tunnel endpoint host also displayed in the options dictionary. I guess we could add another key to the dictionary with "remote_host" from ovn-controller, a matter for a separate patch. On Fri, Mar 9, 2018 at 7:20 PM Ben Pfaff

Re: [ovs-discuss] Including bfd status for tunnel endpoints on ovs-vsctl show

2018-03-09 Thread Ben Pfaff
Seems reasonable to me, feel free to submit a patch. On Fri, Mar 09, 2018 at 05:43:00PM +, Miguel Angel Ajo Pelayo wrote: > Ok, I have modified it to just show bfd_status, for rexample, in a 3 > controller + 1 compute > environment, with a router and a vm on the compute: > >

Re: [ovs-discuss] Including bfd status for tunnel endpoints on ovs-vsctl show

2018-03-09 Thread Miguel Angel Ajo Pelayo
Ok, I have modified it to just show bfd_status, for rexample, in a 3 controller + 1 compute environment, with a router and a vm on the compute: [heat-admin@overcloud-controller-2 ovs]$ sudo utilities/ovs-vsctl show a4cf68a7-07e9-4ed4-a317-016cb610c821 Bridge br-int fail_mode: secure

Re: [ovs-discuss] Including bfd status for tunnel endpoints on ovs-vsctl show

2018-03-09 Thread Miguel Angel Ajo Pelayo
Thank you Ben, I'll finish it, test it properly and submit the patch. I don't know if it makes any sense to add a filter where the dictionary has only a key "enabled" and it's "false", or it's really not worth it. I'll check out how it looks with a real deployment and get back here with the

Re: [ovs-discuss] Including bfd status for tunnel endpoints on ovs-vsctl show

2018-03-08 Thread Ben Pfaff
On Thu, Mar 08, 2018 at 04:43:50PM +, Miguel Angel Ajo Pelayo wrote: > Ok, looking at the code, it seems like we may only need to do this? > > diff --git a/utilities/ovs-vsctl.c b/utilities/ovs-vsctl.c > index 21fa18d..2ac60bf 100644 > --- a/utilities/ovs-vsctl.c > +++ b/utilities/ovs-vsctl.c

Re: [ovs-discuss] Including bfd status for tunnel endpoints on ovs-vsctl show

2018-03-08 Thread Miguel Angel Ajo Pelayo
Ok, looking at the code, it seems like we may only need to do this? diff --git a/utilities/ovs-vsctl.c b/utilities/ovs-vsctl.c index 21fa18d..2ac60bf 100644 --- a/utilities/ovs-vsctl.c +++ b/utilities/ovs-vsctl.c @@ -1018,7 +1018,9 @@ static struct cmd_show_table cmd_show_tables[] = {

Re: [ovs-discuss] Including bfd status for tunnel endpoints on ovs-vsctl show

2018-03-07 Thread Anil Venkata
This is nice option to have. On 07-Mar-2018 6:27 PM, "Miguel Angel Ajo Pelayo" wrote: > > As OVN started implementing L3HA with the use of BFD monitoring, after > discussing with the people who is doing QA and thinking about future > troubleshooting of the feature, they

Re: [ovs-discuss] Including bfd status for tunnel endpoints on ovs-vsctl show

2018-03-07 Thread Miguel Angel Ajo Pelayo
I will submit it tomorrow, I wanted to share the idea first to make sure it made sense. Thank you, Miguel Ángel. On Wed, Mar 7, 2018 at 8:41 PM Ben Pfaff wrote: > On Wed, Mar 07, 2018 at 12:56:49PM +, Miguel Angel Ajo Pelayo wrote: > > As OVN started implementing L3HA with

[ovs-discuss] Including bfd status for tunnel endpoints on ovs-vsctl show

2018-03-07 Thread Miguel Angel Ajo Pelayo
As OVN started implementing L3HA with the use of BFD monitoring, after discussing with the people who is doing QA and thinking about future troubleshooting of the feature, they proposed something the thing on $subject. What do you think? For example, in this case: