<html><body><p>I would agree that #2 is the most flexible option, providing a well defined path for additional frameworks such as Kubernetes and Swarm. <br>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>framework in Magnum. This will also be useful to users who want other frameworks but not Marathon.<br>Ton,<br><br><img width="16" height="16" src="cid:1__=07BBF502DFC784BC8f9e8a93df938690918c07B@" border="0" 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"><font color="#424282">Adrian Otto ---04/08/2016 08:49:52 PM---On Apr 8, 2016, at 3:15 PM, Hongbin Lu <hongbin.lu@huawei.com<<a href="mailto:hongbin.lu@huawei.com">mailto:hongbin.lu@huawei.com</a>>> wrote:</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Adrian Otto <adrian.otto@rackspace.com></font><br><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><font size="2" color="#5F5F5F">Date: </font><font size="2">04/08/2016 08:49 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br>
<ul><ul><font size="4">On Apr 8, 2016, at 3:15 PM, Hongbin Lu <</font><a href="mailto:hongbin.lu@huawei.com"><u><font size="4" color="#0000FF">hongbin.lu@huawei.com</font></u></a><font size="4">> wrote:</font><br><br><font color="#1F497D" face="Calibri">Hi team,</font><br><font color="#1F497D" face="Calibri">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><font color="#1F497D" face="Calibri">1.</font><font size="1" color="#1F497D" face="Times New Roman"> </font><font 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).</font><br><font color="#1F497D" face="Calibri">2.</font><font size="1" color="#1F497D" face="Times New Roman"> </font><font 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></ul></ul></ul></ul><br><font size="4">This is my preference.</font><br><br><font size="4">Adrian</font><br>
<ul><ul><ul><ul><font color="#1F497D" face="Calibri">3.</font><font size="1" color="#1F497D" face="Times New Roman"> </font><font 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></ul></ul><font color="#1F497D" face="Calibri">Which option you prefer? Or you have other suggestions? Advices are welcome.</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">Best regards,</font><br><font color="#1F497D" face="Calibri">Hongbin</font><br><font color="#1F497D" face="Calibri"> </font><br><b><font face="Tahoma">From:</font></b><font face="Tahoma"> Guz Egor [</font><a href="mailto:guz_egor@yahoo.com"><u><font color="#0000FF" face="Tahoma">mailto:guz_egor@yahoo.com</font></u></a><font face="Tahoma">] </font><b><font face="Tahoma"><br>Sent:</font></b><font face="Tahoma"> March-28-16 12:19 AM</font><b><font face="Tahoma"><br>To:</font></b><font face="Tahoma"> OpenStack Development Mailing List (not for usage questions)</font><b><font face="Tahoma"><br>Subject:</font></b><font face="Tahoma"> Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay</font><br><font size="4" face="Times New Roman"> </font><br>Jay,<br> <br>just keep in mind that Chronos can be run by Marathon. <br> <br>--- <br>Egor<br> <div align="center"><hr width="100%" size="2" align="center"></div><b><font face="Arial">From:</font></b><font face="Arial"> Jay Lau <</font><a href="mailto:jay.lau.513@gmail.com"><u><font color="#800080" face="Arial">jay.lau.513@gmail.com</font></u></a><font face="Arial">></font><b><font face="Arial"><br>To:</font></b><font face="Arial"> OpenStack Development Mailing List (not for usage questions) <</font><a href="mailto:openstack-dev@lists.openstack.org"><u><font color="#800080" face="Arial">openstack-dev@lists.openstack.org</font></u></a><font face="Arial">> </font><b><font face="Arial"><br>Sent:</font></b><font face="Arial"> Friday, March 25, 2016 7:01 PM</font><b><font face="Arial"><br>Subject:</font></b><font face="Arial"> Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay</font><br><font size="4"> </font><br><font size="4">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><br><font size="4"> </font><br><font size="4">Thanks,</font><br><font size="4"> </font><br><font size="4">On Fri, Mar 25, 2016 at 5:25 PM, Michal Rostecki <</font><a href="mailto:michal.rostecki@gmail.com" target="_blank"><u><font size="4" color="#800080">michal.rostecki@gmail.com</font></u></a><font size="4">> wrote:<br></font><br><font size="4">On 03/25/2016 07:57 AM, Jay Lau wrote:<br></font><br><font size="4">Hi Magnum,<br><br>The current mesos bay only include mesos and marathon, it is better to<br>enhance the mesos bay have more components and finally enhance it to a<br>DCOS which focus on container service based on mesos.<br><br>For more detail, please refer to</font><u><font size="4" color="#800080"><br></font></u><a href="https://docs.mesosphere.com/getting-started/installing/installing-enterprise-edition/" target="_blank"><u><font size="4" color="#800080">https://docs.mesosphere.com/getting-started/installing/installing-enterprise-edition/</font></u></a><font size="4"><br><br>The mesosphere now has a template on AWS which can help customer deploy<br>a DCOS on AWS, it would be great if Magnum can also support it based on<br>OpenStack.<br><br>I filed a bp here</font><u><font size="4" color="#800080"><br></font></u><a href="https://blueprints.launchpad.net/magnum/+spec/mesos-dcos" target="_blank"><u><font size="4" color="#800080">https://blueprints.launchpad.net/magnum/+spec/mesos-dcos</font></u></a><font size="4"> , please show<br>your comments if any.<br><br>--<br>Thanks,<br><br>Jay Lau (Guangya Liu)</font><br><font size="4"> </font><br><font size="4">Sorry if I'm missing something, but isn't DCOS a closed source software?<br><br>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><br>Cheers,<br>Michal<br><br>[1] </font><a href="https://github.com/mesosphere/dcos-cli" target="_blank"><u><font size="4" color="#800080">https://github.com/mesosphere/dcos-cli</font></u></a><font size="4"><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: </font><a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank"><u><font size="4" color="#800080">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</font></u></a><u><font size="4" color="#800080"><br></font></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><u><font size="4" color="#800080">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><br><font size="4"> </font><br><font size="4"><br></font><br><font size="4"> </font><br><font size="4">--</font><br><font size="4">Thanks,</font><br><font size="4">Jay Lau (Guangya Liu)</font><br><font size="4"> </font><br><font size="4">__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org"><u><font size="4" color="#800080">OpenStack-dev-request@lists.openstack.org</font></u></a><font size="4">?subject:unsubscribe</font><u><font size="4" color="#800080"><br></font></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><u><font size="4" color="#800080">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><br><font size="4"> </font><p><font size="1">__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org"><u><font size="1" color="#0000FF">OpenStack-dev-request@lists.openstack.org</font></u></a><font size="1">?subject:unsubscribe</font><u><font size="1" color="#0000FF"><br></font></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><u><font size="1" color="#0000FF">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a></ul></ul><tt>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></tt><tt><a 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></tt><br><br><BR>
</body></html>