Thank you both for the information. I've implemented an optional
client-initiated echo option, and the ability to echo when prompted by
the server.
- Matt
On 12/07/2017 03:43 PM, Ben Pfaff wrote:
On Thu, Dec 07, 2017 at 01:59:45PM -0500, Matt Layher via discuss wrote:
But that leads me to
On Thu, Dec 07, 2017 at 01:59:45PM -0500, Matt Layher via discuss wrote:
> But that leads me to another question: does ovsdb-server send echo RPCs to
> its clients at all? If so, I can implement something to reply in my receive
> loop. If not, I won't bother.
Yes, it does (unless configured not
It definitely sends for TCP. You can telnet to ovsdb socket and see the the
requests.
чт, 7 дек. 2017 г. в 21:59, Matt Layher :
> I've already got something like that set up anyway so that I can listen
> for notifications for things like "locked", "steal", "update", etc.
I've already got something like that set up anyway so that I can listen
for notifications for things like "locked", "steal", "update", etc. I
think I've got it nailed down pretty well at the moment.
But that leads me to another question: does ovsdb-server send echo RPCs
to its clients at
Couple years ago I implemented my own lib for OVSDB. It had one
communication thread that replied on the echoes as well as sent management
commands from the application. Something very similar of what you're
thinking to implement but based on python coroutines.
Built-in Python lib is different
On Thu, Dec 07, 2017 at 12:24:51PM -0500, Matt Layher via discuss wrote:
> I'm working on implementing an OVSDB client in Go
> (https://godoc.org/github.com/digitalocean/go-openvswitch/ovsdb) and
> recently implemented the Echo RPC.
>
> https://tools.ietf.org/html/rfc7047#section-4.1.11
>
>
Hi all,
I'm working on implementing an OVSDB client in Go
(https://godoc.org/github.com/digitalocean/go-openvswitch/ovsdb) and
recently implemented the Echo RPC.
https://tools.ietf.org/html/rfc7047#section-4.1.11
According to the RFC, the purpose of Echo is "to verify the liveness of
a