Still using Mesos - it's stable, boring - in a good way - and great for our
specific use case.
I'm a committer, happy to continue reviewing and merging small changes or
address security issues.
Cheers,
On Mon, Nov 13, 2023, 13:34 Andreas Peters wrote:
> I'm still with Mesos and can do
00:38, Charles-François Natali wrote:
> > I changed the configuration to clone from GitHub because cloning from ASF
> > gitbox would randomly fail with a network error.
> >
> > I cannot reconcile what you say with the extracts below though, it looks
> > like cloning
I changed the configuration to clone from GitHub because cloning from ASF
gitbox would randomly fail with a network error.
I cannot reconcile what you say with the extracts below though, it looks
like cloning cannot find the revision from the ASF gitbox, not from GitHub,
are they mixed somehow?
Hi,
On Wed, May 11, 2022, 05:22 Andreas Peters wrote:
> Hi,
>
> if we run mesos under Linux with cgroupsV2 then the agent through the
> following error message:
>
> "Failed to create docker: Failed to find a mounted cgroups hierarchy for
> the 'cpu' subsystem;"
>
> Well, since cgroupsV2 does
Benjamin Bannier has kindly invited me to join the
https://github.com/orgs/mesos/ organisation, so I now have the
required permissions - I'll get in touch with Renán to get this new
repository up-and-running.
Cheers,
Charles
Le jeu. 2 sept. 2021 à 19:13, Charles-François Natali
a écrit
On Wed, Sep 1, 2021, 20:56 Renán Del Valle wrote:
> Hi folks,
>
> The packaging repo https://github.com/mesosphere/mesos-deb-packaging is
> no longer maintained by D2iQ and could use a new maintainer and/or home.
>
> Since D2iQ is pretty much out of the picture, it'd probably be ideal to
>
Thanks!
Cheers,
Charles
On Sun, Aug 15, 2021, 21:32 Andreas Peters wrote:
> Congratulations Charles. :-) I'm very happy for you.
>
> Cheers,
> Andreas
>
> On 15.08.21 21:32, Andrei Sekretenko wrote:
> > Hi all,
> > Please welcome Charles-François as a committer and PMC member of the
> >
;
>>> > I created a request to Works On ARM
>>> > https://github.com/WorksOnArm/cluster/issues/278
>>> > If you are interested about history of Mesos on ARM
>>> > https://twitter.com/search?q=ARM%20%40janiszt
>>> >
>>> > pon., 2
Hey,
I'm not sure who can arrange that - Qian maybe? - but yes having an ARM64
CI would be great.
Having access to Martin's VM really made it much simpler to debug the
recent issue with libunwind.
Generally having more CI hosts/pipelines would help, e.g. to build and test
with ASAN and UBSAN.
The last option is fine, i.e. checking that we don't reach past the end of
the file.
Weakening this check is fine since... It's not correct anymore.
On Wed, 23 Jun 2021, 17:52 Saad Ur Rahman (Jira), wrote:
>
> [
>
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,
Hey,
I'm not sure, I was wondering about this.
The problem with closing old tickets is hat some of them are still
serious bugs and valid, so it'd be a bit sad to lose them.
Closing all tickets which look like user questions/errors/etc on the
other hand is fine I think.
Cheers,
Le lun. 31 mai
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
Hey Andrei,
You make some very good points.
> I do not see how the approach "let's move the project out of ASF and
> lower the bar there" benefits the _future_ of the project, compared to
> lowering the committer bar while remaining in ASF.
> (I will reconsider my vote if someone explains how
I must say I'm really confused as well - what constitutes a fork in this
context?
On Thu, 8 Apr 2021, 21:07 Andreas Peters, wrote:
> Hi Shane!
>
>
> > Forks are *NOT* allowed to use the ASF's brands or trademarks, so if
> > you're planning to advertise a new fork to do active development, my
Hi Rich,
FWIW, I'm one of those people who said they were interested, and I
still voted to move it to the attic (even though my vote is non
binding as I'm not a committer).
Initially I also thought that we could try to revive it within the
ASF, but it quickly became clear that *none* of the
+1 (non binding)
Hopefully this will allow the project to continue its life outside the ASF.
Can you confirm whether it'll be possible to continue using
https://github.com/apache/mesos and give write permissions to the various
people who expressed interest?
On Tue, 6 Apr 2021, 14:47 Alex R,
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
I couldn't agree more.
On Mon, 1 Mar 2021, 15:08 Benjamin Bannier, wrote:
> Hi Charles-François,
>
> thanks for your detailed message, you captured important points, and I
> think I agree with your sentiment here. Mesos might still have a place, and
> before thinking about what new features
I'm not sure that the comparison to Kubernetes is very apt - I don't think
anyone is under the illusion that Mesos is a contender for it, that ship
has long sailed.
Also, features availability is only one of the many aspects which should be
considered when choosing among potential candidate
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
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
p in the
> remaining checks).
>
> On Thu, May 7, 2020 at 10:28 PM Charles-François Natali <
> cf.nat...@gmail.com>
> wrote:
>
> > Hey,
> >
> > Sorry if I missed something, but I didn't see any follow up on the
> release
> > - is there an ETA?
> &
Hey,
Sorry if I missed something, but I didn't see any follow up on the release
- is there an ETA?
Cheers,
On Fri, 20 Mar 2020, 22:57 Andrei Sekretenko, wrote:
> Hi all,
> as some of you probably know, Mesos 1.10 release is near; expect that next
> week the release candidate will be prepared
Thanks!
Le ven. 1 mai 2020 à 00:11, Vinod Kone a écrit :
>
> I commented on the JIRA.
>
> On Thu, Apr 30, 2020 at 3:02 PM Charles-François Natali
> wrote:
>
> > Thanks Vinod.
> >
> > Yes, I understand that Mesos assumes it's the only process managing
>
rtup.
>
> Resource detection logic is here:
> https://github.com/apache/mesos/blob/master/src/slave/containerizer/containerizer.cpp#L65
>
> On Thu, Apr 30, 2020 at 8:17 AM Charles-François Natali
> wrote:
>
> > Hi,
> >
> > Could someone point me to some code/do
Hi,
Could someone point me to some code/documentation explaining how the
agent available memory is computed, and when it is refreshed?
For example, if I have an agent started, with some outstanding offers,
and I then start a process - not as a task managed by Mesos, but as an
external process
Perfect, thanks!
On Mon, 30 Dec 2019, 13:42 Vinod Kone, wrote:
> In latest versions of mesos that is handled via heartbeats.
>
> Thanks,
> Vinod
>
> > On Dec 30, 2019, at 4:37 AM, Charles-François Natali <
> cf.nat...@gmail.com> wrote:
> >
> &
ion, please use zookeeper master detector (this detector is used
> when using zookeeper).
>
> On Fri, Dec 20, 2019 at 5:11 AM Charles-François Natali <
> cf.nat...@gmail.com>
> wrote:
>
> > Hi,
> >
> > It seems that the C++ scheduler driver doesn't detect loss of
Hi,
It seems that the C++ scheduler driver doesn't detect loss of the
connection to the master when not using zookeeper.
A simple way to reproduce this is to start a server passing it e.g.
"--ip=127.0.0.1", start the scheduler driver passing it "127.0.0.1:5050",
and then send a SIGKILL to the
Hi,
I'm wondering if there's anything I could do to help
https://issues.apache.org/jira/browse/MESOS-10007 move forward?
Basically it's a race condition in libprocess/command executor causing
spurious errors to be reported for short-lived tasks.
I've got a detailed code path of the race and a
39 matches
Mail list logo
