[Gluster-devel] GlusterD 2.0 status updates

Krishnan Parthasarathi kparthas at redhat.com
Tue Sep 8 06:23:21 UTC 2015

> >   interact with other applications.  Also, normally on REST calls, JSON or
> >   XML is returned.  Is there a reason to go and use binary interfaces?  Do
> >   you see a need to use protobuf?
> The protobuf-based RPC calls are meant for communication between Gluster
> processes
> like bricks, Gluster daemons and GlusterD. This will _not_ be used between
> REST services
> and clients. Also, this RPC mechanism is _not_ going to replace the
> XDR/SunRPC being used
> between clients and brick processes.

To be precise,
[Legend: <---> denotes two-way communication]

* GlusterD 2.0 <---> GlusterD 2.0, brick processes, Gluster daemons, mount processes (akpa clients) - protobuf-based RPC

* GlusterD 2.0 REST service <--> REST clients - JSON/HTTP

(This one remains as is)
* A = {brick processes, Gluster daemons, mount processes}
  All members of "A X A" use XDR/SunRPC for communication. This communication is out
  of scope for GlusterD 2.0 effort and isn't affected due to changes in GlusterD 2.0's
  messaging layer.


More information about the Gluster-devel mailing list