Hi Dan,
I don't think anyone has been looking at this, and i doubt we will, since
we are quite low on resources.
Cheers,
On Tue, Mar 8, 2022, 19:01 Dan Leary wrote:
> Been doing some testing with mesos 1.11.0 and zookeeper's "dynamic
> reconfiguration" capability.
>
Hi Ajay,
I haven't used TLS much with Mesos but I don't think password
protected key files are supported - I'm not sure how useful that would
be in practice anyway.
I think your best bet is to decrypt it using e.g. openssl and provide
that decrypted key file instead.
Cheers,
Charles
Le mer.
On Mon, 28 Jun 2021, 20:41 Marc, wrote
> > I think it's too late for that, your best bet is probably to pick a fork
> > which is still maintained.
>
> Why late? Login accounts do not die not? Is not the right thing that
> Qian Zhang gets control of accounts like
Hey,
Could we please try to stay on topic?
Thanks,
On Mon, 31 May 2021, 20:55 Zahoor, wrote:
> hmmm... Ethereum has a popular client in golang and attracts many rookie
> developers every day.
> But still one of the most complex and nicely maintained software on Earth.
>
> On Mon, May 31,
being able to apply
> >> my knowledge in other areas, beyond C++ (which unfortunately I am not
> >> proficient in).
> >>
> >> [1] https://github.com/dcos
> >> --
> >> Javi Roman
> >>
> >> Twitter: @javiromanrh
> >&
7PP2%3DUu3rk99gQ%40mail.gmail.com%3E
[2]
https://mail-archives.apache.org/mod_mbox/mesos-dev/202105.mbox/%3CCABY6VOaOxSp%2BeMJm_jSTdY%3DD5Qp%3DT%2B89Cvaxqw7GLbFYr1qzew%40mail.gmail.com%3E
>
> -Renan
>
> [0]https://www.apache.org/dev/pmc.html
>
> On 5/24/21 10:21 AM, Charles-Fr
tagged you in all of them, it'd
be great if you could have a look :).
Cheers,
>
>
> Regards,
> Qian Zhang
>
>
> On Fri, May 21, 2021 at 2:57 AM Charles-François Natali
> wrote:
>
> > Hey,
> >
> > Sorry for being a killjoy and repeating myself, but as me
Hey,
Sorry for being a killjoy and repeating myself, but as mentioned in
the past, I don't think that technical direction is the most important
problem right now - community is.
Coming up with medium/long-term technical roadmap doesn't do much if
there are no contributors to implement them, and
Congratulations!
On Thu, 29 Apr 2021, 23:37 Andreas Peters, wrote:
> Great to hear. :-)
>
> Am 29.04.21 um 16:35 schrieb Vinod Kone:
> > Hi community,
> >
> > Just wanted to let you all know that the board passed the resolution to
> > elect a new PMC chair!
> >
> > Hearty congratulations to
Hi,
I'm still interested.
Would it be possible to get a rough roadmap of the proposed course of
action?
So far there's been several email threads asking for feature requests,
contributors etc, but AFAICT no feedback, so it's hard to know exactly
what's going on, and I imagine it would make it
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
Also in - looking forward to contribute further.
Le jeu. 4 mars 2021 à 16:50, Tomek Janiszewski a écrit :
>
> I'm in
> I can help with ARM CI, UI and some C++
>
> czw., 4 mar 2021 o 16:04 Thomas Langé napisał(a):
>>
>> Same for me, I'm available to share my knowledge and actively contribute to
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
to something substantially different. IMO, this
>> requires a _separate_ discussion.
>>
>> Damien's questions sound like a good starting point for that
>> discussion, I'll try to answer them from my committer/PMC member
>> perspective when I have enough time.
>>
Tomek Janiszewski, wrote:
> Moving to attic is making project read only
> https://attic.apache.org/
> https://attic.apache.org/projects/aurora.html
>
> czw., 18 lut 2021, 11:56 użytkownik Charles-François Natali <
> cf.nat...@gmail.com> napisał:
>
>> I'm not familiar
I'm not familiar with the attic but would it still allow to actually
develop, make commits to the repository etc?
On Thu, 18 Feb 2021, 08:27 Benjamin Bannier, wrote:
> Hi Vinod,
>
> > I would like to start a discussion around the future of the Mesos
> project.
> >
> > As you are probably
Hi,
We're using Mesos at work, and are very happy with it.
I'd be interested in becoming a committer. I could probably get some other
colleagues interested as well but from a diversification point of view it'd
probably be better if more individuals/organisations got involved.
Happy to discuss
It's a bit old but in case it could help, we recently implemented this
at work - here's how we did it:
- the NUMA topology is exposed via agent custom resources
- the framework does the allocation of the corresponding resources to
the tasks according to the NUMA topology: e.g. if the task requests
Marc,
Have you read
https://mesos.readthedocs.io/en/1.1.0/high-availability-framework-guide/ in
particular the section about the FrameworkInfo failover_timeout?
Cheers,
Charles
On Tue, 25 Aug 2020, 16:01 Marc Roos, wrote:
>
>
>
> I assume this was because something happened with zookeeper,
Maybe give it a try then, it might help.
Cheers,
Le lun. 6 juil. 2020 à 21:20, Milind Chabbi a écrit :
>
>
>
> On Mon, Jul 6, 2020 at 1:18 PM Charles-François Natali
> wrote:
>>
>> >> Also, there are some obvious limitations with this: for example
>>
>> Also, there are some obvious limitations with this: for example
>> binding processes to a specific NUMA node means that you might not
>> benefit from CPU bursting (e.g. if there's some available CPU on
>> another NUMA node).
>
>
> True. I would like the bust to be limited to only the cores on a
Hi Milind,
(I'm just a user not a developer so take what I say with a grain of salt :-).
AFAICT the agent/containerisation code is not NUMA-aware, so it
probably wouldn't be trivial.
Also, there are some obvious limitations with this: for example
binding processes to a specific NUMA node means
Hey,
The website doesn't seem to have been updated to point to the most recent
release.
Cheers,
On Thu, 28 May 2020, 17:11 Andrei Sekretenko, wrote:
> Hi all,
>
> The vote for Mesos 1.10.0 (rc1) has passed with the
> following votes.
>
> +1 (Binding)
> --
> Vinod
er soon.
>
>
> Regards,
> Qian Zhang
>
>
> On Fri, Feb 21, 2020 at 4:46 AM Vinod Kone wrote:
>
>> Andrei, Qian: Can one of you answer the above question?
>>
>> On Thu, Feb 20, 2020 at 7:15 PM Charles-François Natali <
>> cf.nat...@gmail.com>
owse/MESOS-9916 . For
> custom executor, you would be on your own to implement the same. Also, your
> custom executor / scheduler should be able to limit one task per executor
> if you so desire.
>
> On Thu, Feb 20, 2020 at 6:34 PM Charles-François Natali <
> cf.nat...@gmail.com&g
Hi,
Is there a way to force Mesos to use one executor per task?
The reason I would want to do that is for resources limits: for example,
when using cgroup to limit CPU and memory, IIUC the containeriser sets
limits corresponding to the sum of the resources allocated to the tasks
managed by the
the target command.
This way we don't need to trust the framework, we don't rely on Mesos
authentication, and don't have to write our own executor.
Le sam. 19 oct. 2019 à 12:20, Charles-François Natali
a écrit :
>
> Hi,
>
> We've been contemplating using Mesos at the co
Hi,
We've been contemplating using Mesos at the company I work for.
Basically we would be writing our own framework, and various users
would submit jobs to it.
However a remaining problem to us is the security model: anyone which
is allowed to connect to the Mesos cluster can start tasks as any
28 matches
Mail list logo
