- Verifies Riak startup behavior when strong consistency is enabled and
  AAE is disabled.  (defect https://github.com/basho/riak_kv/issues/959)
- Adds additional console output to reset-current-env to explain
  configuration and steps being executed
- Adds the -n option to the reset-current-env script to specify the
  number of nodes to build.  By default, 5 will be created.
Merge pull request #636 from basho/bugfix/jsb/start-ensemble-without-aae

Verify Riak Startup when Strong Consistency is Misconfigured
Add test to kill a vnode and vnode proxy

Kill a vnode and it's proxy for a given key and ensure that operation
reads succeed afterwards.
add intercept for riak_kv_ensemble_backend:handle_down/4 in ensemble_vnode_crash
Add ability to handle identical siblings in rt:systest_read

Add optional parameter to rt:systest_read that provides the ability to
compare siblings and treat those with identical values and metadata
excluding the dot as a single value for the purposes of testing.

This is to facilitate testing with DVV enabled since there are several
known cases where use of DVV leads to siblings created internally by
Riak. One example of such a case is a write during handoff that is
forwarded by the vnode, but also executed locally.

The existing behavior of rt:systest_read is to fail when any siblings
are encountered with a badmatch. This behavior is maintained as the
default so existing tests maintain their current semantics without
explicit change.
Do sibling comparison in a module function rather than anonymous function
Update calls to rt:systest_read to handle identical siblings

Update the calls to rt:systest_read in repl_util and
repl_aae_fullsync_util to treat identical siblings resulting from the
use of DVV as a single value.  These changes are specifically to
address failures seen in the repl_aae_fullsync_custom_n and
replication_object_reformat tests, but should be generally useful for
replication tests using the utility modules that and that have
allow_mult set to true.
Add handling of errors in rt:index_built_fun

AAE fullsync tests can encounter {error, wrong_node} messages
resulting from rpc calls to riak_kv_vnode:hashtree_pid. Add handling
of error responses to rt:index_built_fun.
Merge pull request #645 from basho/ensemble-vnode-crash2

Add test to kill a vnode and vnode proxy
Merge branch 'feature/systest-read-sibling-handling'
Merge branch 'feature/update-repl-systest-read-use'
Fix replication_object_reformat test failure

Part of the condition checking done in the replication_object_reformat
test is to validate the results of a fullsync using
repl_util:validate_completed_fullsync/6. The way in which the the
function is called from the test expects fullsync to complete with 0
error_exit or retry_exit conditions occurring. This requires that sink
cluster be in a steady state with all partitions available. The test
failed to wait for such conditions to occur and instead relied on
performing a node downgrade asynchronously and waiting for up to 60
seconds for a completion message before continuing with the test. The
test was continually failing after a node was downgraded to `previous`
due to partitions being reported as `down` on that node. To resolve
the issue the node downgrade process is now done in the primary test
process instead of in a separate spawned process. After the version
downgrade is complete, the test now waits for the riak_repl and the
riak_kv services, calls rt:wait_until_nodes_ready/1, calls
rt:wait_until_no_pending_changes/1, and finally waits for the
riak_repl2_fs_node_reserver named process to be registered on the
downgraded node. This process is responsible for handling partition
reservation requests and is key to determining the the new node is
able to handle a fullsync without partition errors.
Reinstate concurrency in replication_object_reformat test