Introduce Chronos framework for mesos bay

If the open source DC/OS is supported in the bp of "mesos-dcos", then this project will be no longer needed as the open source DC/OS include many default/built-in frameworks including chronos, marathon, cassandra etc. -- jay-lau-513 2016-04-22

Hi hongbin, I try to set up the chronos+ marathon+mesos+docker+ zookeeper cluster. I find both chronos and marathon can work well. If the bp can do. I can work. Thanks.(wangqun)

@wangqun, thanks for willingness to take the work. In the last team meeting, we (sort-of) agreed to run Chronos by using Marathon. Please check if you can implement this BP in such a way. --hongbin
@hongbin,Thank you agree to my request. I will try to test the way to run chronos by using marathon. Thanks again.(wangqun)
@hongbin,I have test to run chronos as a container by using marathon. Both chronos and marathon can work well. (wangqun)

Hongbin and Wangqun, I think that we do not need this project but need focus on "mesos-dcos", the dc/os will provide chronos by default, using DC/OS manage the chronos and other frameworks should be the official way, comments? Thanks. -- jay-lau-513 2016-05-11

Guangya, Does adding the dcos changes largely for image or templete? If it is so. I think we need to discuss if using DC/OS manage the chronos and other frameworks in meeting.
Hongbin, What do you think? -- wangqun 2016-05-11

@Wangqun DC/OS will replace the current mesos bay. The plan is to add a new bay type for DC/OS, then deprecate the current mesos bay. DC/OS is a superset of the current mesos bay. It contains Marathon, Chronos, and many others. For this blueprint, I think it should be superseded by the DC/OS blueprint. -- hongbin 2016-05-11

@hongbin Thank you to answer my question and DC/OS is great for magnum mesos. We can abandon the bp to implement the DC/OS. Thanks again. -- wangqun 2016-05-12