Re: Feature requests for Mesos
On 2021-03-01 04:14 PM, Klaus Ma wrote: Mesos is really a great project! In addition to new features, is it possible to make Mesos focus on some specific area, e.g. HPC? I really do think also that HPC should be a target :) -- Klaus <http://k82.me/> From: Damien GERARD Sent: Monday, March 1, 2021 1:05 AM To: user@mesos.apache.org Cc: mesos Subject: Re: Feature requests for Mesos On 2021-02-28 05:38 PM, Qian Zhang wrote: Hi Folks, To reboot this awesome project, I'd like to collect feature requests for Mesos. Please let us know your requirements for Mesos and whether you or your organization would like to contribute to the implementation of the requirements. Thanks! We can already summarize what has been said in previous discussions, mainly making mesos easier to deploy / maintain, and my personal one, with more batteries included by default. There are also several ways of improvements, especially regarding GPU support, numa, ZFS integration, volume management... But first, reducing the effort to have a fully functional mesos cluster would be to me, one of the priorities (and also targeting local development like minimesos was trying to achieve) -- Damien GERARD -- Damien GERARD
Re: Feature requests for Mesos
On 2021-02-28 05:38 PM, Qian Zhang wrote: Hi Folks, To reboot this awesome project, I'd like to collect feature requests for Mesos. Please let us know your requirements for Mesos and whether you or your organization would like to contribute to the implementation of the requirements. Thanks! We can already summarize what has been said in previous discussions, mainly making mesos easier to deploy / maintain, and my personal one, with more batteries included by default. There are also several ways of improvements, especially regarding GPU support, numa, ZFS integration, volume management... But first, reducing the effort to have a fully functional mesos cluster would be to me, one of the priorities (and also targeting local development like minimesos was trying to achieve) -- Damien GERARD
Re: Feature requests for Mesos
On 2021-02-28 08:54 PM, Samuel Marks wrote: Decouple Apache ZooKeeper, enabling Apache Mesos to run completely without ZooKeeper. Specifically enable a choice between ZooKeeper, etcd, and consul. To be honest, I would prefer something like foundationdb, and slowly moving to a multi-master mode My organisation is somewhat interested in contributing this. We tried in the past but came across some hurdles on the Mesos organisation end. Open to trying again, but will need a clear pathway to getting this accepted. Samuel Marks Charity <https://sydneyscientific.org> | consultancy <https://offscale.io> | open-source <https://github.com/offscale> | LinkedIn <https://linkedin.com/in/samuelmarks> On Sun, Feb 28, 2021 at 7:39 PM Qian Zhang wrote: Hi Folks, To reboot this awesome project, I'd like to collect feature requests for Mesos. Please let us know your requirements for Mesos and whether you or your organization would like to contribute to the implementation of the requirements. Thanks! Regards, Qian Zhang -- Damien GERARD
Re: Next Steps
On 2021-02-26 09:05 PM, Charles-François Natali wrote: As mentioned before I'd also be happy to contribute. Concretely, what's the next step to move this forward? On Fri, 26 Feb 2021, 11:15 Thomas Langé, wrote: Hello, I'm part of Criteo team as well, and as Grégoire said, we plan to support Mesos internally for some time. I would like to propose my help as well as a committer, and contribute as much as I can to this project. At Rakuten we also have a couple of clusters. As also mentionned before, happy to contribute. But yeah, need a plan of action :p Br, Thomas - From: Grégoire Seux Sent: Friday, 26 February 2021 11:12 To: priv...@mesos.apache.org ; dev ; user Subject: Re: Next Steps Hello all, here at Criteo, we heavily use Mesos and plan to do so for a foreseeable future alongside other alternatives. I am ok to become committer and help the project if you are looking for contributors. It seems finding committers will be doable but finding a PMC chair will be difficult. To give some context on our usage, Criteo is running 12 Mesos cluster running a light fork of Mesos 1.9.x. Each cluster has 10+ distinct marathons frameworks, a flink framework, an instance of Aurora and an in-house framework. We strongly appreciate the ability to scale the number of nodes (3500 on the largest cluster and growing), the simplicity of the project overall and the extensibility through modules. -- Grégoire -- Damien GERARD
Re: Next Steps
On 2021-02-18 09:08 AM, Samuel Marks wrote: Mesos is great… conceptually. In practice it requires a lot of work to setup and keep running. What my team tried to contribute was a replacement for some of the big moving parts—namely Apache ZooKeeper—with a choice between etcd, Consul, and ZooKeeeper. This was the first of many planned contributions, with the goal to turn Mesos into a tiny component that you could plugin to any scale architecture (1 developer laptop, 1 server, 3 servers, 5 servers, 10,000 servers). Currently there is a threshold for when your architecture is complicated enough + loaded enough to benefit from Mesos. If instead all a developer / sysadmin / DevOps / cloud engineer needed to consider is how many moving parts they have in their own applications (say: Postgres, MySQL, Kubernetes, Kafka), and they thought of Mesos as a simple coordinator between these and their scarce resources, then IMHO Mesos would have a renewed community and interest, and not be falling into the background. The other side of things is that most everyone is now comfortable using cloud hosted services, like DBaaS, container-as-a-Service, queue-as-a-Service, datalake-as-a-Service &etc. The landscape has become so skewed that, from my experience, very few new engineers + new engineering companies are able to offer complete packages in public [and private] clouds. If Mesos makes some key architectural changes, to the point where anyone can use it without so much as a second thought, to the benefit of their compute resources, then I'd expect a huge growth here. Samuel Marks Charity <https://sydneyscientific.org> | consultancy <https://offscale.io> | open-source <https://github.com/offscale> | LinkedIn <https://linkedin.com/in/samuelmarks> PS: My company may even sponsor further development. On Thu, Feb 18, 2021 at 10:54 AM Vinod Kone wrote: Hi folks, I would like to start a discussion around the future of the Mesos project. As you are probably aware, the number of active committers and contributors to the project have declined significantly over time. As of today, there's no active development of any features or a public release planned. On the flip side, I do know there are a few companies who are still actively using Mesos. Given that, we need to assess if there's interest in the community to keep this project moving forward. Specifically, we need some active committers and PMC members who are going to manage the project. Ideally, these would be people who are using Mesos in some capacity and can make code contributions. If there is no active interest, we will likely need to figure out steps for retiring the project. *Call for action: If you are interested in becoming a committer/PMC member (including PMC chair) and actively maintain the project, please reply to this email.* I personally don't foresee myself being very active in the Mesos project going forward, so I'm planning to step down from my chair role as soon as we find a replacement. I think I personally agree with all the previous statements here. I am willing to help eventually in maintaining the project. But first things first, perhaps we should ask to the current maintainers: - what do they think the project should be going? - what is currently good in mesos? - what is currently bad/wrong in mesos? - which target of people / use case we should focus on? We all have ideas I guess, which could to different situations. From what I see from the slack, there were periodic online meetings to give a roadmap to the projects. It is probably something that should be restored and the future of the project could be discussed. -- Damien GERARD
