Hi all, We discussed this in our last team meeting, and we were in disagreement. Some of us preferred option #1, others preferred option #2. I would suggest to leave this topic to the design summit so that our team members would have more times to research each option. If we are in disagreement again, I will let the core team to vote (hopefully we will have all the core team in the design summit).
Best regards, Hongbin From: Guz Egor [mailto:guz_e...@yahoo.com] Sent: April-11-16 4:31 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay +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. honestly I don't see how #2 will work, because Marathon installation is different from Aurora installation. --- Egor ________________________________ From: Kai Qiang Wu <wk...@cn.ibm.com<mailto:wk...@cn.ibm.com>> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Sent: Sunday, April 10, 2016 6:59 PM Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay #2 seems more flexible, and if it be proved it can "make the SAME mesos bay applied with mutilple frameworks." It would be great. Which means, one mesos bay should support multiple frameworks. Thanks Best Wishes, -------------------------------------------------------------------------------- Kai Qiang Wu (吴开强 Kennan） IBM China System and Technology Lab, Beijing E-mail: wk...@cn.ibm.com<mailto:wk...@cn.ibm.com> Tel: 86-10-82451647 Address: Building 28(Ring Building), ZhongGuanCun Software Park, No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193 -------------------------------------------------------------------------------- Follow your heart. You are miracle! 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 From: Hongbin Lu <hongbin...@huawei.com<mailto:hongbin...@huawei.com>> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: 11/04/2016 12:06 am Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay ________________________________ 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. Best regards, Hongbin From: Ton Ngo [mailto:t...@us.ibm.com] Sent: April-10-16 11:24 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay I would agree that #2 is the most flexible option, providing a well defined path for additional frameworks such as Kubernetes and Swarm. 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 framework in Magnum. This will also be useful to users who want other frameworks but not Marathon. Ton, Adrian Otto ---04/08/2016 08:49:52 PM---On Apr 8, 2016, at 3:15 PM, Hongbin Lu <hongbin...@huawei.com<mailto:hongbin...@huawei.com>> wrote: From: Adrian Otto <adrian.o...@rackspace.com<mailto:adrian.o...@rackspace.com>> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: 04/08/2016 08:49 PM Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay ________________________________ On Apr 8, 2016, at 3:15 PM, Hongbin Lu <hongbin...@huawei.com<mailto:hongbin...@huawei.com>> wrote: Hi team, 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: 1. Add Chronos to the mesos bay. With this option, the mesos bay will have two mesos frameworks by default (Marathon and Chronos). 2. 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. This is my preference. Adrian 3. 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).Which option you prefer? Or you have other suggestions? Advices are welcome. Best regards, Hongbin From: Guz Egor [mailto:guz_e...@yahoo.com] Sent: March-28-16 12:19 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay Jay, just keep in mind that Chronos can be run by Marathon. --- Egor ________________________________ From: Jay Lau <jay.lau....@gmail.com<mailto:jay.lau....@gmail.com>> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Sent: Friday, March 25, 2016 7:01 PM Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay 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. Thanks, On Fri, Mar 25, 2016 at 5:25 PM, Michal Rostecki <michal.roste...@gmail.com<mailto:michal.roste...@gmail.com>> wrote: On 03/25/2016 07:57 AM, Jay Lau wrote: Hi Magnum, The current mesos bay only include mesos and marathon, it is better to enhance the mesos bay have more components and finally enhance it to a DCOS which focus on container service based on mesos. For more detail, please refer to https://docs.mesosphere.com/getting-started/installing/installing-enterprise-edition/ The mesosphere now has a template on AWS which can help customer deploy a DCOS on AWS, it would be great if Magnum can also support it based on OpenStack. I filed a bp here https://blueprints.launchpad.net/magnum/+spec/mesos-dcos , please show your comments if any. -- Thanks, Jay Lau (Guangya Liu) Sorry if I'm missing something, but isn't DCOS a closed source software? 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. Cheers, Michal [1] https://github.com/mesosphere/dcos-cli __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Thanks, Jay Lau (Guangya Liu) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
