> What is the estimated size of such a team? And is there any data
> available how many man hours were committed by mesosphere the last year
> or so?
>
>
If questions are raised about creating a proper support base for the future
development of mesos. Is it not relevant to have some numbers on
I think it's fair, but it would be nice if the current committers could
reach a consensus on the way forward: either be willing to help new
contributors get up to speed - with the caveats mentioned - or move the
project to the Attic, so that interested people can try to
maintain/continue its
>
> Under the current circumstances, this, in my view, means that Mesos
> has no long-term prospects unless it manages to shift to a
> niche/role/direction in which the problems cannot be reasonably solved
> by the Kubernetes-style cluster orchestration.
>
If I read (outdated?) articles such as
>
> I think the key issues have been brought up by Benjamin and Renan.
>
> Just to add to Benjamin's comments above, achieving those key markers of
> a healthy project requires serious corporate backing such that people
> are being
> employed to primarily work on Mesos. It takes a lot of work to
I think Benjamin Bannier and Benjamin Mahler are right about the
immediate non-technical issues and how the backing of the project
could/could not look like in future.
I would say that the main root cause of both the non-technical
troubles and the lack of the backing is the issue of the long-term
I think the key issues have been brought up by Benjamin and Renan.
Just to add to Benjamin's comments above, achieving those key markers of
a healthy project requires serious corporate backing such that people are
being
employed to primarily work on Mesos. It takes a lot of work to keep the
* csi slrp unmanaged driver
(unless it is possible to work around enabling SYS_ADMIN in
bounding_capabilities for all tasks)
* csi serp
http://mesos.apache.org/documentation/latest/csi/#limitations
https://issues.apache.org/jira/browse/MESOS-8371
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
On Sun, Feb 28, 2021 at 12:39 AM 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
>
_
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 requir
:* 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
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!
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
13 matches
Mail list logo
