Hi Alexander,It seams not so easy (almost impossible) to maintain Mesos with a small group of peoples under Apache. Thats why I decide to create a fork of Mesos (https://github.com/m3scluster/clusterd). Have a look into the changelog. Maybe some changes are interesting for you. You (and of course every one else) are always welcome.
To m3s! As I know, there is only the K8 framework for DCOS. If M3S does not match your requirements, I would be happy if you send me a EMail (or ping me via Matrix or Slack) with the reasons. Feedback are always welcome.
Cheers, Andreas Am 10.11.23 um 11:31 schrieb Alexander Sibiryakov:
Hi Qian and others, We're also Mesos user, having 4-5 clusters of Mesos, running 1.4.1. Some of them are powering our Scrapy Cloud product using 3K CPUs, around 6-10K jobs executing in parallel, and several hundreds starting per second. I think the situation with Mesos is that its purpose have changed with the time. Initially it was widely adopted as containers orchestration platform run a variety of applications. Currently there are mature, future rich and battle-tested alternatives like Kubernetes, especially the managed offers. So Mesos due its simplicity, concentrating mainly on orchestration, is out of the competition in this market. But, there are still very little frameworks for building cloud systems. As it is stated on the main pageApache Mesos abstracts CPU, memory, storage, and other compute resources away from machines (physical or virtual), enabling fault-tolerant and elastic distributed systems to easily be built and run effectively.These days Mesos is still a good solution for those who need to orchestrate a specific workload at scale. Its operational model with customisable schedulers receiving resource offers fits perfectly when there is a queue of jobs which needs to be executed on a limited amount of hardware. Kubernetes isn't really designed for that. But, this is a concern of cloud builders, which is a rare occasion today. Due to the complexity of the cloud systems, very few people on the planet can design and build them. Meaning you should not expect the same amount of active contributors as for other projects. So my question is, is there an option to lift the requirement of 3 active contributors for the specific case of Mesos and postpone the decision on moving this project to the attic? A. On 2023/03/18 01:57:00 Qian Zhang wrote:Hi all, I'd like to restart the discussion around the future of the Mesos project. As you may already be aware, the Mesos community has been inactive for the last few years, there were only 3 contributors last year, that's obviously not enough to keep the project moving forward. I think we need at least 3 active committers/PMC members and some active contributors to keep the project alive, or we may have to move it to attic <https://attic.apache.org/>. Call for action: If you are the current committer/PMC member and still have the capacity to maintain the project, or if you are willing to actively contribute to the project as a contributor, please reply to this email, thanks! Regards, Qian Zhang
OpenPGP_0x6A83F12541CFCCF9.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
