Riak CS bundle in a docker container

This project provides a reference setup of a minimal suite of Riak CS, Riak, Stanchion and Riak CS Control, built and run as a docker stack.

Building and running

With make start, you will get riak_cs, stanchion, riak_cs_control and riak images created and their containers started, all properly configured. Applications versions can be defined in environment variables RIAK_VSN, RCS_VSN, RCSC_VSN and STANCHION_VSN (with reasonably recent versions as defaults). Images for riak_cs, riak_cs_control and stanchion are built from source, pulled from repos at github.com/TI-Tokyo.

External addresses of Riak CS nodes and the node running Riak CS Control will be printed at the end of make start. Also, an admin user will be created whose credentials can be copied and used in your s3 client.

The entire stack can be stopped with make stop, and all riak data dirs deleted with make clean.

Older versions of riak and riak_cs

Dockerfiles for versions 2.x of riak, riak_cs and stanchion use 'erlang:R16' for the base image (which has, specifically, tag OTP_R16B02_basho10 from github.com/basho/otp). It will need to be built, once, with make R16.

Cluster topologies

Cluster topologies can be specified in "riak-topo.json" and "rcs-topo.json" (see examples in "riak-topo.json.example" and "rcs-topo.json.example".

Persisting state

Within containers, riak data dirs are bind-mounted to local filesystem at ${RIAK_PLATFORM_DIR}/riak/data/${N}, where N is the riak node number (1-based). Unless explicitly set, directories will be created in "./p". Similarly, riak logs can be found at ${RIAK_PLATFORM_DIR}/riak/logs/${N}. To delete it, do make clean (or rm -rf p manually).

Note that due to non-determinism inherent in the way docker assigns addresses, resuming operation (that is, make start followed by make stop) is only possible for topologies with a single riak cluster.

Load-testing

The bundle provides a script, "lib/load-test", which uses s3-benchmark to generate sample data and perform the test. By default, it runs "../s3-benchmark/s3-benchmark", with parameters "-t 5 -l 10 -d 30", meaning 10 loops 30 sec each, in 3 threads.

Another script, "scripts/all-combos", will build riak tags 2.2.6, 2.9.10 and 3.0.8, riak_cs tags 2.1.3pre1 and 3.0.0pre8, and run the load test in all riak+riak_cs combinations, with results logged in load-test-report.