Added ption to start basho bench as part of a node by calling basho_bench:main/1 not just as a standalone node from command line, the default option is the original standalone
FAIL_MSG behaviour to depend on included/standalone mode

If basho_bench is running standalone, call halt(1) on fatal errors
like before.  When included in another node, kill supervisor for a
more graceful exit.
Don't crash if basho_bench is already loaded
add needed cassandra config options
Deprecate the int_to_bin key generator, add 2 others to replace it
Add value_generator_blob_file config option to value generator.

If present, e.g.,

    {value_generator_blob_file, "/path/to/a/file"}.

... then the value generator will use the contents of that file instead
of the (mostly) completely random bytes that are generated by
`crypto:rand_bytes/1`.  By allowing the specify an arbitrary file,
the user has control over much entropy is present in the values that
basho_bench generates.  The user can specify a file with a single
repeating byte (which would yield the same values that the basho_bench
value generator `{fixed_char, Size}` will yield, or specify a file
that contains app-specific data such as representative JSON samples,
or a file that contains output from a command like `dd if=/dev/urandom`,
which would yield an extremely low amount of entropy similar to
what the basho_bench key generator `{fixed_bin, Size}` yields.

The main reason for adding this kind of user-controllable entropy
for value blobs is to study the compression rates of Riak storage
backends such as ELevelDB.

Using the ELevelDB backend with compression disabled or enabled
and with various key generators used (and all other basho_bench
configuration knobs identical.

* compression=false
* 1000-of-N ... Using `{fixed_bin, 1000}` and `{value_generator_source_size, N}`
  where N is closer to 1000 -> less entropy -> better possible compression rate
* foo2*.{file-size}KB ... using `{value_generator_blob_file, "file"}`
  where the file size is {file-size} kilobytes, i.e., 100KB or 1.3KB.
  This file is various JSON objects concatenated together into a single
  file.
  Smaller file size -> less entropy -> better possible compression rate

    % du -hs rel/riak/data/leveldb*
    3.1G        rel/riak/data/leveldb.compression=false+1000-of-1048576
    1.7G        rel/riak/data/leveldb.compression=true+1000-of-1020
    1.9G        rel/riak/data/leveldb.compression=true+1000-of-1200
    2.4G        rel/riak/data/leveldb.compression=true+1000-of-2048
    2.6G        rel/riak/data/leveldb.compression=true+1000-of-4096
    1.7G        rel/riak/data/leveldb.compression=true+foo2b.100KB
    1.1G        rel/riak/data/leveldb.compression=true+foo2d.1.3KB
Add SSL support to HTTP driver.

To use, add {http_use_ssl, true} or {http_use_ssl, [ssl-options]} to
bench config as well ensure that http_raw_port is pointing to a SSL
enabled port.
update the basho-bench docs URL
tweak wording.
Add script to plot latencies by gnuplot
Add script to plot throughput by gnuplot
Added enforce_keyrange setting and edge case verification
Added devrel configurtion for 2i.config
No time for codepaths Dr. Jones
Merge pull request #53 from basho/jd-2i-for-riak-test

2i driver: Added enforce_keyrange setting and edge case verification
Change argument for older gnuplot versions
Fix logging, add option handling

This commit address an issue and adds a feature

Issue

When the switch to lager was made a bug was introduced where
initialization of basho bench could fail before lager is started.
Specifically, if a malformed config was passed basho bench would exit
with no indication as to why.  This was because the config was read
for `test_dir` to determine where to write the log files but lager
cannot start until the log file locations are determined.  Thus a
chicken-egg problem.  This commit changes that behavior, pulling the
test_dir (now called results_dir) from command line options.

Feature

In order to pass the results_dir as a command line option I thought it
would be best to add proper argument handling in the form of getopt.
In addition to the `-d` option I also added `--bench-name`.  By
default basho bench stores the results of a run under a directory with
the current iso8601 timestamp.  This is a great default but many times
I want to name the results of a run for posterity and this required an
extra copy operation afterwards.  The `-n` option allows you to name a
test run which will also be used as the name of the directory.  By
default basho bench will act as it did before but the `-d` and `-n`
options give you more control on where to store results.
Merge branch 'rz-fix-logging-add-getopt'
Merge pull request #40 from basho/slf-deprecate-int_to_bin-keygen

Deprecate the int_to_bin key generator, add 2 others to replace it
add code for voxer tests to bench