[ovs-discuss] ovs-appctl to monitor HVs sb connection status

Ben Pfaff blp at ovn.org
Tue Jul 10 03:30:46 UTC 2018


On Mon, Jul 09, 2018 at 06:12:11PM -0700, Han Zhou wrote:
> On Mon, Jul 9, 2018 at 3:37 PM, Ben Pfaff <blp at ovn.org> wrote:
> >
> > On Sun, Jul 08, 2018 at 01:09:12PM -0700, aginwala wrote:
> > > As per discussions in past OVN meetings regarding ovn monitoring stand
> > > point, need some clarity from design perspective. I am thinking of below
> > > approaches:
> > >
> > > 1. Can we implement something like ovs-appctl -t <sbdb>
> chassis-conn/list
> > > that will show all HVs stats (connected/non-connected)?
> >
> > You're interested particularly in which chassis are connected to the ovn
> > southbound database?  The db server only knows who is connected to it if
> > they provide SSL certificates.  It might not be too hard to get it to
> > report the common name (CN) of the SSL certificates for the clients
> > connected to it.  Would that suffice?
> >
> > > 2. or  on individual HVs using ovs-appctl -t ovn-controller
> > > chassis-conn/list ?
> >
> > The HVs definitely don't know who is connected to the sbdb server.
> > _______________________________________________
> > discuss mailing list
> > discuss at openvswitch.org
> > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> 
> Discussion in the meeting was about showing connection status to SB-DB on a
> given HV, and for that HV only.
> So I think a new command like "ovs-appctl -t ovn-controller rconn/show"
> should be enough.

I forgot the context.  If that's enough, it will work.

We don't currently have a good way to do general-purpose monitoring or
configuration of ovn-controller.  What little we do now, we do through
the ovs-vswitchd database.  If we want something more extensive, maybe
it should have its own hypervisor-local database.

> The suggestion from Ben is a good one if we are trying to check all HV
> connections status from central node point of view.

I don't think it should be very hard (but sometimes OpenSSL makes easy
things difficult).


More information about the discuss mailing list