[ovs-discuss] ovn-controller periodically reporting status

Han Zhou zhouhan at gmail.com
Fri Mar 16 21:55:31 UTC 2018

On Wed, Mar 14, 2018 at 10:14 PM, Anil Venkata <anilvenkata at redhat.com>
> On Thu, Mar 15, 2018 at 3:35 AM, Ben Pfaff <blp at ovn.org> wrote:
>> On Tue, Mar 13, 2018 at 05:46:41PM +0530, Anil Venkata wrote:
>> > In Openstack neutron reference implementation, all agents will be
>> > periodically reporting their status to neutron server. Similarly in
>> > Openstack OVN based deployment, we want ovn-controller to periodically
>> > report its status to neutron server.
>> What kind of monitoring do you need?  If it's just a matter of finding
>> out that the controllers are still alive, then the existing "nb_cfg"
>> column in Chassis can suffice.  When neutron wants to check on the
>> controllers, it can increment nb_cfg in NB_Global and then see which
>> controllers update nb_cfg in Chassis in response.
> Thanks a lot Ben.
> Yes, the requirement is to check if the ovn-controller is dead or alive.
> "nb_cfg" column is sufficient for this. I will follow your suggestion.
> Thanks
> Anil
As discussed in this weeks OVN meeting, current nb_cfg mechanism triggers a
lot of update notifications unnecessarily. For this mechanism to be used by
the monitoring purpose, we also need to optimize it so that the HV nb_cfg
updates won't be notified to other HVs. I just sent out the patch for that


Please take a look.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20180316/224d9ebe/attachment.html>

More information about the discuss mailing list