GlusterD-2.0 v4.0dev-2

New changes

This release has 2 big changes to GD2.

• PR #128 switched GD2 to use gRPC for internal peer-to-peer RPCs.
• PR #136 introduced the daemon framework, which allows GD2 to actually start bricks. But bricks don't start due to 2 pending issues.
  • #150 - because rundir and logdir are missing
  • #146 - because generated volfiles are incomplete and incorrect

In addition to the above changes to GD2, a new Docker image, kshlm/glusterd2-dev:centos-latest with glusterfs-server 3.8.4 installed. This is used by the included Vagrantfile to spin up 4 nodes which can be used to test during GD2 development.

How to test

A docker image and Vagrantfile with the latest release will be provided soon to help easily test GD2.

Running GD2

• Download the released binary
• Extract and add glusterd2 binary to your $PATH
  • GD2 can run as a non-root user if CAP_SYS_ADMIN is set on the binary
    • Run sudo setcap cap_sys_admin+ep <path-to>/glusterd2
• Ensure etcd is available in your $PATH
• Create an empty working directory
• Run GD2 glusterd2 --workdir <workdir path>

Start GD2 on 2 or more machines/VMs/Containers etc.

Testing commands

GD2 does not have a CLI yet. The ReST API is the only way to communicate with GD2 right now.

The ReST API can be used using curl or a ReST API client tool of your choice. My recommendation is postman.

Refer to the API documentation for more information on the available commands.

Known Issues

• For volume start to work, WORKDIR/run/gluster and WORKDIR/log/glusterfs/bricks. This atleast allows the brick process to attempt to parse and load the volfile, but it fails anyway.