[openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay
Hongbin Lu
hongbin.lu at huawei.com
Sun Apr 10 16:03:49 UTC 2016
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:ton at 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,
[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 at huawei.com]Adrian Otto ---04/08/2016 08:49:52 PM---On Apr 8, 2016, at 3:15 PM, Hongbin Lu <hongbin.lu at huawei.com<mailto:hongbin.lu at huawei.com>> wrote:
From: Adrian Otto <adrian.otto at rackspace.com<mailto:adrian.otto at rackspace.com>>
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at 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.lu at huawei.com<mailto:hongbin.lu at 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_egor at 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.513 at gmail.com<mailto:jay.lau.513 at gmail.com>>
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org<mailto:openstack-dev at 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.rostecki at gmail.com<mailto:michal.rostecki at 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-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@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-request at lists.openstack.org<mailto:OpenStack-dev-request at 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-request at lists.openstack.org<mailto:OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe<mailto:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160410/d3900900/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 105 bytes
Desc: image001.gif
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160410/d3900900/attachment.gif>
More information about the OpenStack-dev
mailing list