<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1460392269145_124206" dir="ltr"><span id="yui_3_16_0_ym19_1_1460392269145_124333">+1 for "#1: Mesos and Marathon". Most deployments that I am aware of has this setup. Also we can provide several line instructions how to run Chronos on top of Marathon.</span></div><div id="yui_3_16_0_ym19_1_1460392269145_124206"><span><br></span></div><div id="yui_3_16_0_ym19_1_1460392269145_124206" dir="ltr"><span id="yui_3_16_0_ym19_1_1460392269145_124814">honestly I don't see how #2 will work, because Marathon installation is different from Aurora installation. </span></div><div id="yui_3_16_0_ym19_1_1460392269145_124206"><br></div><div class="signature" id="yui_3_16_0_ym19_1_1460392269145_124207">--- </div><div class="signature" id="yui_3_16_0_ym19_1_1460392269145_124207">Egor</div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1460392269145_124211"><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1460392269145_124235" style="display: block;">  <div style="font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13px;" id="yui_3_16_0_ym19_1_1460392269145_124234"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1460392269145_124233"> <div dir="ltr" id="yui_3_16_0_ym19_1_1460392269145_124232"> <font size="2" face="Arial" id="yui_3_16_0_ym19_1_1460392269145_124236"> <hr size="1" id="yui_3_16_0_ym19_1_1460392269145_124250"> <b id="yui_3_16_0_ym19_1_1460392269145_124249"><span style="font-weight:bold;" id="yui_3_16_0_ym19_1_1460392269145_124248">From:</span></b> Kai Qiang Wu <wkqwu@cn.ibm.com><br> <b><span style="font-weight: bold;">To:</span></b> OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Sunday, April 10, 2016 6:59 PM<br> <b id="yui_3_16_0_ym19_1_1460392269145_124247"><span style="font-weight: bold;" id="yui_3_16_0_ym19_1_1460392269145_124246">Subject:</span></b> Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1460392269145_124239"><br><div id="yiv3603195009"><div id="yui_3_16_0_ym19_1_1460392269145_124238"><div id="yui_3_16_0_ym19_1_1460392269145_124237">#2 seems more flexible, and if it be proved it can "make the <b>SAME</b> mesos bay applied with mutilple frameworks." It would be great. Which means, one mesos bay should support multiple frameworks.<br clear="none"><br clear="none"><br clear="none"><br clear="none"><br clear="none">Thanks<br clear="none"><br clear="none"><br clear="none">Best Wishes,<br clear="none">--------------------------------------------------------------------------------<br clear="none">Kai Qiang Wu (吴开强  Kennan)<br clear="none">IBM China System and Technology Lab, Beijing<br clear="none"><br clear="none">E-mail: wkqwu@cn.ibm.com<br clear="none">Tel: 86-10-82451647<br clear="none">Address: Building 28(Ring Building), ZhongGuanCun Software Park,  <br clear="none">         No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193<br clear="none">--------------------------------------------------------------------------------<br clear="none">Follow your heart. You are miracle! <br clear="none"><br clear="none"><img width="16" height="16" border="0" alt="Inactive hide details for Hongbin Lu ---11/04/2016 12:06:07 am---My preference is #1, but I don’t feel strong to exclude #2. I" data-id="3c8482c8-0201-c5d9-3b59-c97e0590297c"><font color="#424282" id="yui_3_16_0_ym19_1_1460392269145_124914">Hongbin Lu ---11/04/2016 12:06:07 am---My preference is #1, but I don’t feel strong to exclude #2. I would agree to go with #2 for now and</font><br clear="none"></div><div class="yiv3603195009yqt6434844442" id="yiv3603195009yqtfd17428"><br clear="none"><font size="2" color="#5F5F5F">From:        </font><font size="2">Hongbin Lu <hongbin.lu@huawei.com></font><br clear="none"><font size="2" color="#5F5F5F">To:        </font><font size="2">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br clear="none"><font size="2" color="#5F5F5F">Date:        </font><font size="2">11/04/2016 12:06 am</font><br clear="none"><font size="2" color="#5F5F5F">Subject:        </font><font size="2">Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay</font><br clear="none"></div><div class="yiv3603195009yqt6434844442" id="yiv3603195009yqtfd23514"><hr align="left" noshade="" width="100%" size="2" style="color:#8091A5;"><br clear="none"><br clear="none"><br clear="none"><font color="#1F497D" face="Calibri">My preference is #1, but I don’t feel strong to exclude #2. I would agree to go with #2 for now and switch back to #1 if there is a demand from users. For Ton’s suggestion to push Marathon into the introduced configuration hook, I think it is a good idea.</font><br clear="none"><font color="#1F497D" face="Calibri"> </font><br clear="none"><font color="#1F497D" face="Calibri">Best regards,</font><br clear="none"><font color="#1F497D" face="Calibri">Hongbin</font><br clear="none"><font color="#1F497D" face="Calibri"> </font><br clear="none"><b><font face="Tahoma">From:</font></b><font face="Tahoma"> Ton Ngo [</font><font face="Tahoma"><a rel="nofollow" shape="rect" ymailto="mailto:ton@us.ibm.com" target="_blank" href="mailto:ton@us.ibm.com">mailto:ton@us.ibm.com</a></font><font face="Tahoma">] </font><b><font face="Tahoma"><br clear="none">Sent:</font></b><font face="Tahoma"> April-10-16 11:24 AM</font><b><font face="Tahoma"><br clear="none">To:</font></b><font face="Tahoma"> OpenStack Development Mailing List (not for usage questions)</font><b><font face="Tahoma"><br clear="none">Subject:</font></b><font face="Tahoma"> Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay</font><br clear="none"><font size="4" face="Times New Roman"> </font><div id="yui_3_16_0_ym19_1_1460392269145_124755"><font size="4" face="Times New Roman" id="yui_3_16_0_ym19_1_1460392269145_124754">I would agree that #2 is the most flexible option, providing a well defined path for additional frameworks such as Kubernetes and Swarm. <br clear="none">I would suggest that the current Marathon framework be refactored to use this new hook, to serve as an example and to be the supported<br clear="none">framework in Magnum. This will also be useful to users who want other frameworks but not Marathon.<br clear="none">Ton,<br clear="none"><br clear="none"></font><img width="16" height="16" alt="Inactive hide details for Adrian Otto ---04/08/2016 08:49:52 PM---On Apr 8, 2016, at 3:15 PM, Hongbin Lu <hongbin.lu@huawei.com" data-id="558ac5c9-4c7e-b416-6d53-274e43915f83"><font size="4" color="#424282" face="Times New Roman">Adrian Otto ---04/08/2016 08:49:52 PM---On Apr 8, 2016, at 3:15 PM, Hongbin Lu <hongbin.lu@huawei.com<</font><a rel="nofollow" shape="rect" ymailto="mailto:hongbin.lu@huawei.com" target="_blank" href="mailto:hongbin.lu@huawei.com"><u><font size="4" color="#0000FF" face="Times New Roman">mailto:hongbin.lu@huawei.com</font></u></a><font size="4" color="#424282" face="Times New Roman">>> wrote:</font><font size="4" face="Times New Roman"><br clear="none"></font><font color="#5F5F5F" face="Times New Roman"><br clear="none">From: </font><font face="Times New Roman">Adrian Otto <</font><a rel="nofollow" shape="rect" ymailto="mailto:adrian.otto@rackspace.com" target="_blank" href="mailto:adrian.otto@rackspace.com"><u><font color="#0000FF" face="Times New Roman">adrian.otto@rackspace.com</font></u></a><font face="Times New Roman">></font><font color="#5F5F5F" face="Times New Roman"><br clear="none">To: </font><font face="Times New Roman">"OpenStack Development Mailing List (not for usage questions)" <</font><a rel="nofollow" shape="rect" ymailto="mailto:openstack-dev@lists.openstack.org" target="_blank" href="mailto:openstack-dev@lists.openstack.org"><u><font color="#0000FF" face="Times New Roman">openstack-dev@lists.openstack.org</font></u></a><font face="Times New Roman">></font><font color="#5F5F5F" face="Times New Roman"><br clear="none">Date: </font><font face="Times New Roman">04/08/2016 08:49 PM</font><font color="#5F5F5F" face="Times New Roman"><br clear="none">Subject: </font><font face="Times New Roman">Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay</font><br clear="none"></div><hr align="left" noshade="" width="100%" size="2"><br clear="none"><font size="4" face="Times New Roman"><br clear="none"></font><ul><ul><ul><ul></ul></ul></ul></ul><font size="5" face="Times New Roman">On Apr 8, 2016, at 3:15 PM, Hongbin Lu <</font><a rel="nofollow" shape="rect" ymailto="mailto:hongbin.lu@huawei.com" target="_blank" href="mailto:hongbin.lu@huawei.com"><u><font size="5" color="#0000FF" face="Times New Roman">hongbin.lu@huawei.com</font></u></a><font size="5" face="Times New Roman">> wrote:</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="4" color="#1F497D" face="Calibri" id="yui_3_16_0_ym19_1_1460392269145_124758"><br clear="none">Hi team,<br clear="none">I would like to give an update for this thread. In the last team, we discussed several options to introduce Chronos to our mesos bay:</font><ul><ul><ul><ul></ul></ul></ul></ul><font size="4" color="#1F497D" face="Calibri">1.</font><font size="2" color="#1F497D" face="Times New Roman"> </font><font size="4" color="#1F497D" face="Calibri">Add Chronos to the mesos bay. With this option, the mesos bay will have two mesos frameworks by default (Marathon and Chronos).<br clear="none">2.</font><font size="2" color="#1F497D" face="Times New Roman"> </font><font size="4" color="#1F497D" face="Calibri">Add a configuration hook for users to configure additional mesos frameworks, such as Chronos. With this option, Magnum team doesn’t need to maintain extra framework configuration. However, users need to do it themselves.</font><font size="5" face="Times New Roman"><br clear="none">This is my preference.</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none">Adrian</font><ul><ul><ul><ul><ul><ul><ul><ul></ul></ul></ul></ul></ul></ul></ul></ul><font size="4" color="#1F497D" face="Calibri">3.</font><font size="2" color="#1F497D" face="Times New Roman"> </font><font size="4" color="#1F497D" face="Calibri">Create a dedicated bay type for Chronos. With this option, we separate Marathon and Chronos into two different bay types. As a result, each bay type becomes easier to maintain, but those two mesos framework cannot share resources (a key feature of mesos is to have different frameworks running on the same cluster to increase resource utilization).</font><font size="4" color="#1F497D" face="Calibri">Which option you prefer? Or you have other suggestions? Advices are welcome.</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="4" color="#1F497D" face="Calibri"><br clear="none">Best regards,<br clear="none">Hongbin</font><font size="4" face="Times New Roman"><br clear="none"></font><b><font size="4" face="Tahoma"><br clear="none">From:</font></b><font size="4" face="Tahoma"> Guz Egor [</font><a rel="nofollow" shape="rect" ymailto="mailto:guz_egor@yahoo.com" target="_blank" href="mailto:guz_egor@yahoo.com"><u><font size="4" color="#0000FF" face="Tahoma">mailto:guz_egor@yahoo.com</font></u></a><font size="4" face="Tahoma">] </font><b><font size="4" face="Tahoma"><br clear="none">Sent:</font></b><font size="4" face="Tahoma"> March-28-16 12:19 AM</font><b><font size="4" face="Tahoma"><br clear="none">To:</font></b><font size="4" face="Tahoma"> OpenStack Development Mailing List (not for usage questions)</font><b><font size="4" face="Tahoma"><br clear="none">Subject:</font></b><font size="4" face="Tahoma"> Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay</font><font size="4" face="Times New Roman"><br clear="none"><br clear="none">Jay,<br clear="none"><br clear="none">just keep in mind that Chronos can be run by Marathon. <br clear="none"><br clear="none">--- <br clear="none">Egor</font><div align="center"><hr align="center" width="100%" size="2"></div><b><font size="4" face="Arial">From:</font></b><font size="4" face="Arial"> Jay Lau <</font><a rel="nofollow" shape="rect" ymailto="mailto:jay.lau.513@gmail.com" target="_blank" href="mailto:jay.lau.513@gmail.com"><u><font size="4" color="#800080" face="Arial">jay.lau.513@gmail.com</font></u></a><font size="4" face="Arial">></font><b><font size="4" face="Arial"><br clear="none">To:</font></b><font size="4" face="Arial"> OpenStack Development Mailing List (not for usage questions) <</font><a rel="nofollow" shape="rect" ymailto="mailto:openstack-dev@lists.openstack.org" target="_blank" href="mailto:openstack-dev@lists.openstack.org"><u><font size="4" color="#800080" face="Arial">openstack-dev@lists.openstack.org</font></u></a><font size="4" face="Arial">> </font><b><font size="4" face="Arial"><br clear="none">Sent:</font></b><font size="4" face="Arial"> Friday, March 25, 2016 7:01 PM</font><b><font size="4" face="Arial"><br clear="none">Subject:</font></b><font size="4" face="Arial"> Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none">Yes, that's exactly what I want to do, adding dcos cli and also add Chronos to Mesos Bay to make it can handle both long running services and batch jobs.</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none">Thanks,</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none">On Fri, Mar 25, 2016 at 5:25 PM, Michal Rostecki <</font><a rel="nofollow" shape="rect" ymailto="mailto:michal.rostecki@gmail.com" target="_blank" href="mailto:michal.rostecki@gmail.com"><u><font size="5" color="#800080" face="Times New Roman">michal.rostecki@gmail.com</font></u></a><font size="5" face="Times New Roman">> wrote:</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none">On 03/25/2016 07:57 AM, Jay Lau wrote:</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none">Hi Magnum,<br clear="none"><br clear="none">The current mesos bay only include mesos and marathon, it is better to<br clear="none">enhance the mesos bay have more components and finally enhance it to a<br clear="none">DCOS which focus on container service based on mesos.<br clear="none"><br clear="none">For more detail, please refer to</font><u><font size="4" color="#0000FF" face="Times New Roman"><br clear="none"></font></u><a rel="nofollow" shape="rect" target="_blank" href="https://docs.mesosphere.com/getting-started/installing/installing-enterprise-edition/"><u><font size="5" color="#800080" face="Times New Roman">https://docs.mesosphere.com/getting-started/installing/installing-enterprise-edition/</font></u></a><font size="5" face="Times New Roman"><br clear="none"><br clear="none">The mesosphere now has a template on AWS which can help customer deploy<br clear="none">a DCOS on AWS, it would be great if Magnum can also support it based on<br clear="none">OpenStack.<br clear="none"><br clear="none">I filed a bp here</font><u><font size="4" color="#0000FF" face="Times New Roman"><br clear="none"></font></u><a rel="nofollow" shape="rect" target="_blank" href="https://blueprints.launchpad.net/magnum/+spec/mesos-dcos"><u><font size="5" color="#800080" face="Times New Roman">https://blueprints.launchpad.net/magnum/+spec/mesos-dcos</font></u></a><font size="5" face="Times New Roman"> , please show<br clear="none">your comments if any.<br clear="none"><br clear="none">--<br clear="none">Thanks,<br clear="none"><br clear="none">Jay Lau (Guangya Liu)</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none">Sorry if I'm missing something, but isn't DCOS a closed source software?<br clear="none"><br clear="none">However, the "DCOS cli"[1] seems to be working perfectly with Marathon and Mesos installed by any way if you configure it well. I think that the thing which can be done in Magnum is to make the experience with "DOCS" tools as easy as possible by using open source components from Mesosphere.<br clear="none"><br clear="none">Cheers,<br clear="none">Michal<br clear="none"><br clear="none">[1] </font><a rel="nofollow" shape="rect" target="_blank" href="https://github.com/mesosphere/dcos-cli"><u><font size="5" color="#800080" face="Times New Roman">https://github.com/mesosphere/dcos-cli</font></u></a><font size="5" face="Times New Roman" id="yui_3_16_0_ym19_1_1460392269145_124764"><br clear="none"><br clear="none">__________________________________________________________________________<br clear="none">OpenStack Development Mailing List (not for usage questions)<br clear="none">Unsubscribe: </font><a rel="nofollow" shape="rect" target="_blank" href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe"><u><font size="5" color="#800080" face="Times New Roman">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</font></u></a><u><font size="4" color="#0000FF" face="Times New Roman"><br clear="none"></font></u><a rel="nofollow" shape="rect" target="_blank" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><u><font size="5" color="#800080" face="Times New Roman">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><font size="4" face="Times New Roman"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none"></font><font size="4" face="Times New Roman"><br clear="none"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none">--<br clear="none">Thanks,<br clear="none">Jay Lau (Guangya Liu)</font><font size="4" face="Times New Roman"><br clear="none"></font><font size="5" face="Times New Roman"><br clear="none">__________________________________________________________________________<br clear="none">OpenStack Development Mailing List (not for usage questions)<br clear="none">Unsubscribe: </font><a rel="nofollow" shape="rect" ymailto="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank" href="mailto:OpenStack-dev-request@lists.openstack.org"><u><font size="5" color="#800080" face="Times New Roman">OpenStack-dev-request@lists.openstack.org</font></u></a><font size="5" face="Times New Roman">?subject:unsubscribe</font><u><font size="4" color="#0000FF" face="Times New Roman"><br clear="none"></font></u><a rel="nofollow" shape="rect" target="_blank" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><u><font size="5" color="#800080" face="Times New Roman">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><div id="yui_3_16_0_ym19_1_1460392269145_124771"><font size="2" face="Times New Roman">__________________________________________________________________________<br clear="none">OpenStack Development Mailing List (not for usage questions)<br clear="none">Unsubscribe: </font><a rel="nofollow" shape="rect" ymailto="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank" href="mailto:OpenStack-dev-request@lists.openstack.org"><u><font size="2" color="#0000FF" face="Times New Roman">OpenStack-dev-request@lists.openstack.org</font></u></a><font size="2" face="Times New Roman">?subject:unsubscribe</font><u><font size="4" color="#0000FF" face="Times New Roman"><br clear="none"></font></u><a rel="nofollow" shape="rect" target="_blank" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><u><font size="2" color="#0000FF" face="Times New Roman">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><font face="Courier New">__________________________________________________________________________<br clear="none">OpenStack Development Mailing List (not for usage questions)<br clear="none">Unsubscribe: </font><a rel="nofollow" shape="rect" ymailto="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"><u><font color="#0000FF" face="Courier New">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</font></u></a><u><font color="#0000FF" face="Courier New"><br clear="none"></font></u><a rel="nofollow" shape="rect" target="_blank" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" id="yui_3_16_0_ym19_1_1460392269145_124770"><u id="yui_3_16_0_ym19_1_1460392269145_124769"><font color="#0000FF" face="Courier New" id="yui_3_16_0_ym19_1_1460392269145_124768">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><font size="4" face="Times New Roman"><br clear="none"><br clear="none"></font><tt>__________________________________________________________________________<br clear="none">OpenStack Development Mailing List (not for usage questions)<br clear="none">Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br clear="none"></tt><tt><a rel="nofollow" shape="rect" target="_blank" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br clear="none"></tt><br clear="none"><br clear="none"><br clear="none">
</div></div></div></div><br><div class="yqt6434844442" id="yqtfd10606">__________________________________________________________________________<br clear="none">OpenStack Development Mailing List (not for usage questions)<br clear="none">Unsubscribe: <a shape="rect" ymailto="mailto:OpenStack-dev-request@lists.openstack.org" href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br clear="none"><a shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br clear="none"></div><br><br></div> </div> </div>  </div></div></body></html>