Hello, Naive Q: Do we already have gRPC/Protocol Buffers (PB) support for ODL RPCs? Say if you were writing something in say Go and wanted to call some ODL RPC, and sure could start with a HTTP REST call to the RPC's RESTCONF, but wondered whether there was a faster way with generated strongly typed client library for the future... interesting/useful? Stupid?
I briefly searched around, and found references like https://bugs.opendaylight.org/show_bug.cgi?id=1638 (which is closed and anyway not directly what I'm after, but was an idea to use PB in the CDS impl, which is different, I think?), then hit https://github.com/opendaylight/controller/blob/master/opendaylight/md-sal/sal-akka-raft/README-FIRST (is that just an outdated README?), or https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Architecture:Clustering saying "Serialization of Normalized Node and conversion of all messages to protocol buffers serialization (target Jul 8th)" In Progress - is there code related to that left anywhere? If one were to implement something like this, it would best be... presumably, a new generator, a bit like a binding, which would generate a *.proto for a *.yang (no idea how easy/hard this is?), and then use the PB infra to gen. the clients, and then gen. an impl of the PB server "stubs" mapping the request/response from PB to a Java Binding or (probably better) Normalized Node - does this idea make sense, in principle? More curious than anything else, at this point. Tx, M. -- Michael Vorburger, Red Hat vorbur...@redhat.com | IRC: vorburger @freenode | ~ = http://vorburger.ch
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
