Testing releases

This page describes how you can test GD2 using the released binaries.

Installation

You can either manually install and use the released binary or use the corresponding gluster/glusterd2-test docker image.

Docker + Vagrant

A Vagrantfile is available in the GD2 repo, which starts 4 docker containers running the latest gluster/glusterd2-test image. This image contains GD2 installed into $PATH and additional tools like tmux to make lives easier for testers.

This method requires Vagrant and Docker installed on your system.

• Download the Vagrantfile into a directory and cd into the directory OR
• If you have the GD2 git repo on your system, cd into extras/test-env inside the repo.
• Run vagrant up --provider docker. This launches 4 containers named gd2test-{1..4}.
• SSH into the container using vagrant ssh <name>

Vagrant only downloads the latest docker image the first time a vagrant up is done. It does not keep the image updated. If you have already used this method before for previous releases, you need to ensure you run docker pull gluster/glusterd2-dev after every release to get the latest image.

Manual

• Download the released binary from the releases page.
• 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

Install on more machines/VMs as required.

Running

• Create an empty working directory
• Create run/gluster and log/glusterfs directories under the working directory.
• Start GD2 by running glusterd2 --workdir <workdir path>

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