[Gluster-devel] GlusterD 2.0 status updates

[Krishnan Parthasarathi]

----- Original Message -----
> Hi Atin,
>   This looks interesting.  Currently in Heketi it needs to ssh into a system
>   to send commands to glusterfs.  It would be great to determine the
>   interfaces needed and how it would work with programs like Heketi.  Do you
>   guys have a simple few paragraphs on how glusterd2 rest interface will
>   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.

> 
> Also I do quite a few comments on the code itself.  Should I create github
> issues for them or should I put them here on the email?

Github issues work best.

> 
> Thanks Atin,
> 
> - Luis
> 
> ----- Original Message -----
> From: "Atin Mukherjee" <amukherj at redhat.com>
> To: "Gluster Devel" <gluster-devel at gluster.org>
> Sent: Tuesday, September 1, 2015 1:04:35 AM
> Subject: [Gluster-devel] GlusterD 2.0 status updates
> 
> Here is a quick summary of what we accomplished over last one month:
> 
> 1. The skeleton of GlusterD 2.0 codebase is now available @ [1] and the
> same is integrated with gerrithub.
> 
> 2. Rest end points for basic commands like volume
> create/start/stop/delete/info/list have been implemented. Needs little
> bit of more polishing to strictly follow the heketi APIs
> 
> 3. Team has worked on coming up with a cross language light weight RPC
> framework using pbrpc and the same can be found at [2]. The same also
> has pbcodec package which provides a protobuf based rpc.ClientCodec and
> rpc.ServerCodec that can be used with rpc package in Go's standard library
> 
> 4. We also worked on the first cut of volfile generation and its
> integrated in the repository.
> 
> 
> The plan for next month is as follows:
> 
> 1. Focus on the documentation along with publishing the design document
> 2. Unit tests
> 3. Come up with the initial design & a basic prototype for transaction
> framework.
> 
> [1] https://github.com/kshlm/glusterd2
> [2] https://github.com/kshlm/pbrpc
> 
> Thanks,
> Atin
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>