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:2
gt;
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 m
t for usage questions)"
<openstack-dev@lists.openstack.org>
Date: 12/04/2016 04:36 am
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 provi
--- Egor
From: Kai Qiang Wu <wk...@cn.ibm.com>
To: OpenStack Development Mailing List (not for usage questions)
<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 flexibl
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 introd
[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
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> wrote:
Hi team,
I would like to give an update for this thread. In the last team, we
discussed several options to introd
o: 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
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
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
wrote:
> On 03/25/2016 07:57 AM, Jay Lau wrote:
>
>> Hi
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
opment Mailing List <openstack-dev@lists.openstack.org>
Sent: Thursday, March 24, 2016 11:57 PM
Subject: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay
Hi Magnum,The current mesos bay only include mesos and marathon, it is better
to enhance the mesos bay have more components
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
13 matches
Mail list logo