[openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

Hongbin Lu hongbin.lu at huawei.com
Fri Apr 8 22:15:27 UTC 2016

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.

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,

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


just keep in mind that Chronos can be run by Marathon.


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.


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

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

I filed a bp here
https://blueprints.launchpad.net/magnum/+spec/mesos-dcos , please show
your comments if any.


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.


[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>

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160408/f7382238/attachment-0001.html>

More information about the OpenStack-dev mailing list