Hi Alexander,
Thanks for your mail and happy to know you are also using Mesos.
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?
I think we may not be able to l
I am happy to know that clusterd exists. Some good news in this world.
Thank you. I will not spam more here.
On Fri, Nov 10, 2023, 15:33 Andreas Peters wrote:
> Hi Alexander,
>
> It seams not so easy (almost impossible) to maintain Mesos with a small
> group of peoples under Apache. Thats why I
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
c
Hello. Except M3S, do we have K8S distro as Mesos frameworks?
On Fri, Nov 10, 2023, 13:32 Alexander Sibiryakov
wrote:
> 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 j
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 ch
>
> Qian, it might be worth having a more explicit email asking users to chime
> in as this email was tailored more for contributors.
Yes, we can have such email, but I think it does not affect whether we
should move Mesos to attic or not, since the most important factor is
whether we have enough
Hello everyone,
At Institutional Shareholder Services we just rolled out additional Mesos
clusters in two of our data-centers. Those are based on Mesos 1.11.0 running on
Debian 11 (using cgroups v1).
Obviously I personally would like to see the community grow again, and also
more than happy to
ion.
-Dan
From: Benjamin Mahler
Sent: Monday, March 20, 2023 2:55 PM
To: user@mesos.apache.org
Cc: mesos ; priv...@mesos.apache.org
Subject: Re: Next steps for Mesos
Also if you are still a user of mesos, please chime in.
Qian, it might be worth having a more explicit email asking users to ch
Hi,
as you know Qian, I'm still on board. 😄
Andreas
On 18.03.23 02:57, 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 contributor
sos ; priv...@mesos.apache.org
Subject: [BULK]Re: Next steps for Mesos
Also if you are still a user of mesos, please chime in.
Qian, it might be worth having a more explicit email asking users to chime in
as this email was tailored more for contributors.
Twitter is still using mesos heavily, we upg
@mesos.apache.org
Cc : mesos ; priv...@mesos.apache.org
Objet : Re: Next steps for Mesos
Also if you are still a user of mesos, please chime in.
Qian, it might be worth having a more explicit email asking users to chime in
as this email was tailored more for contributors.
Twitter is still using mesos
Also if you are still a user of mesos, please chime in.
Qian, it might be worth having a more explicit email asking users to chime
in as this email was tailored more for contributors.
Twitter is still using mesos heavily, we upgraded from a branch based off
of 1.2.x to 1.9.x in 2021, but haven't u
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
13 matches
Mail list logo
