0.9.1.1 release

• Changed default failover for broker from delay of 1 minute and max-delay of 10 minutes. This failover is related to the broker failing and being relaunched on the same slave node. At some point this should give up. Future version will accept a callback from an outside plug-in for monitoring issues such as disk space. Often other schedulers might be part of the general allocation so a time window of trying for 1 minute with a progression to not exceed 10 minutes (based on maxTries which is still defaulted to 2). #77 created to add more scheduler ability to deal with infrastructure acked problems programmatically and more metrics.
• Broker Placement Stickiness - For both failover and manual restarts you often want a window of time that the scheduler will wait for the same resources it had before to become available. When this exceeds the time set the scheduler will then seek resources from another machine. A manual stop can be issued before or during the time period for maintenance tasks via the CLI or REST API.