Differentiate read- and write-clusters

The ability to place a cluster into "write-only mode" is intended to
facilitate operational maneuvers, like re-provisioning a farm. The
intended workflow is:

 - Add a new cluster, in write-only mode
 - Perform a backfill, to populate the new cluster
 - Perform sanity checks, e.g. equal key counts
 - Switch the cluster to normal read+write mode

The new mode prevents farm read strategies from querying what's
effectively a known-bad set of instances while they're spinning up.
Replace all instances of '%s' with %q
Prometheus histograms use configurable max summary age
Tests for ParseFarmString
TestWriteOnly
Merge pull request #20 from soundcloud/write-only

Differentiate read- and write-clusters
pool: fix example in README
Log cluster configuration
prometheus.prefix becomes prometheus.namespace
Oops!
README: fix erroneous claim re: LWW-element-set

Closes #21. Thanks, @rsltrifork, for the eagle eyes!
Remove writeonly mode for a cluster.

It's just not used in the way I thought it would be.
Merge pull request #22 from soundcloud/remove-write-only-mode

Remove writeonly mode for a cluster.
First sketch of Select{Offset,Cursor} split
Work in progress
Work in progress
cluster: import organization
farm: work in progress
Work in progress: update roshi-server
roshi-walker: fix for SelectOffset