mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From haosdent <haosd...@gmail.com>
Subject Re: [Mesos 2.0] Let's talk about the future
Date Fri, 29 Jul 2016 07:21:55 GMT
I would like to make Containerizer modular. Refer to this ticket
https://issues.apache.org/jira/browse/MESOS-3709

On Fri, Jul 29, 2016 at 3:13 PM, Jay JN Guo <guojiannan@cn.ibm.com> wrote:

> Hi,
>
> As we are all excited about release 1.0.0, it's never too early to talk
> about next big thing: Mesos 2.0.0. What major things should be done next?
>
> I believe there are still many features you desire in Mesos and some of
> them are already under development. I'd like to collect your minds and
> align the vision in this mail thread. For example, here are items on Mesos
> long term roadmap:
>
> Pluggable Fetcher
> Oversubscription for reservation: Optimistic offers
> Resource Revocation
> Pod support
> Quota chunks
> Multiple-role support for frameworks
> User namespace support
> Event bus
> First class resources (Cpu topology info, GPU topology info, disk speed,
> etc)
> Deprecate Docker containerizer (in favor of Unified containerizer w/
> Docker support)
>
> I would appreciate it if you could either share your ideas or vote on
> these items, and we will discuss it in next community sync.
>
> We may not have an unshakeable conclusion as container technology is
> evolving at an ever faster pace, but the whole community, especially
> newbies like myself, would profoundly benefit from a clear plan and
> priority for next 3-6 months.
>
> Cheers,
> /Jay
>
>


-- 
Best Regards,
Haosdent Huang

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message