Break Backward Compatibility

[josephholsten]

Someday soon we're going to have to break backwards compatibility, and we may as well rip the bandage off. This is a tracking ticket for all the backwards incompatible changes that should go into the next breaking release (1.0?).

• Non-shard replicaset cluster_name not honored #6 allow arbitrary shard names
• shard_name #95 separate shard and replicaset names
• 10gen is now MongoDB #153 remove references to 10gen
• Compound sharding key #158 support compound sharding keys
• [breaking change] Stop creating a mongodb_instance in mongodb::default #179 stop creating a mongodb_instance in mongodb::default
• Set the log path, config path, data path to the default 10 gen repo  #262 update default paths to match mongodb defaults
• Support YAML config file #309 use yaml format config, incompatible with < 2.6 mongo

[thomas-riccardi]

From the CHANGELOG: DEPRECATE '10gen_repo' for 'mongodb_org_repo' #287 (dropping in 0.16.2). Please don't do that until major version change, ie not in 0.16.2.
(Also, the README still refers to 10gen_repo).

[josephholsten]

Moved to sous-chefs/sc-mongodb#78