Open Stack

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>
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://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Thanks,

Jay Lau (Guangya Liu)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160326/f58256c0/attachment.html>