Re: Cgroups v2 + Python 3 + Upstreaming X/Twitter Patches
Awesome, thanks so much Ben. :-) Am 12.01.24 um 23:55 schrieb Benjamin Mahler: As part of upgrading to CentOS 9 at X/Twitter, Shatil / Devin (cc'ed) will be working on: * Upgrading to Python 3 * Cgroups v2 support We will attempt to upstream this work for the benefit of other users. In addition, we have several long-standing internal patches that should have been upstreamed but weren't. We currently deploy from an internal 1.9.x branch with these additional patches on top of OSS 1.9.x. To simplify the above work since the code changes will be substantial (especially for cgroups v2), we'll try to work off master (or 1.11.x) and upstream our long-standing internal patches to minimize the delta between OSS and our internal branch. Let me know if folks have any questions. IMO it would be good for users to hold off on going into the attic so that we can land this work at least. Ben OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Can you help provide a future for Apache Mesos?
I'm still with Mesos and can do what I done the last years. Keep an eye at issues and give support via Slack and Jira. Am 13.11.23 um 13:51 schrieb Shane Curcuru: As a mature and successful project, Mesos hasn't seen much new development in the past couple of years. The question now for everyone on these lists is: - Is Mesos still a maintained project, where even if no new features are developed, there's at least a group to respond to security issues and make new releases? Or is it time to 'deprecate' Mesos, and move the project as a whole to the Apache Attic? [1] It feels like there are still plenty of users who rely on Mesos; what we need now is for enough people here to step up and volunteer to stick around and be available to fix security issues in the future. Thanks to Qian for raising this question in March [2], where several people did speak up. I'd like to clarify what the ASF board's requirements are for an 'active' Apache project. We don't actually need people doing active development on a project. What's really needed is at least three PMC members who are monitoring the project's lists and issues, and who could be available in the future *if* a serious security issue or other major bug were discovered. So we're not looking for people with time to do active development - just enough reliable volunteers who could monitor for major issues that are reported, and make a new release if security fixes are needed. Does that help, and does that make sense? We will also be running a Roll Call of the PMC [3] now, so the board can understand how many PMC members (who have access to security issue details, for example) could still stick around to monitor lists. Along with that roll call, we'll also be reminding the existing PMC that they can vote in any existing committers who will also step up and volunteer. * What can you do? If you are still using Mesos, have enough time to check the mailing lists/issue tracker periodically for any security or giant breaking bugs (i.e. not small bugs), and might be able to help someday with a fix or making a new release of Mesos, then speak up now! Be sure to say what specific kinds of tasks you might be able to take on if they arise. Remember: we don't need active development, just some folks making sure any security bugs are addressed in the future (if they come up). OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Next steps for Mesos
Hi, as you know, 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 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 -- AVENTER UG (haftungsbeschraenkt) Köllner Chaussee 144 25337 Kölln-Reisiek Phone: (+49)4121 - 235582 0 E-Mail: a...@aventer.biz Internet: https://www.aventer.biz Git: https://www.github.com/AVENTER-UG Geschäftsführer/CEO: Andreas Peters Unternehmenssitz/City: Kölln-Reisiek Handelsregister beim Amtsgericht/Legal Court: Itzehoe Handelsregister-Nummer/Company Registration Number: HRB 9995 PI OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Apache Mesos Twitter Account
I was thinking, if it would be possible that I help out with the twitter account? Sometimes there are still some mesos tweets and it would be good to retweet them at least. :-) What do u think? Am 22.08.22 um 00:33 schrieb Benjamin Mahler: Yes I still have access, I was mostly managing it during the 2016-present period but haven't done anything since late 2020. Do you have anything in mind you'd like to see tweeted or retweeted? On Thu, Aug 18, 2022 at 5:05 AM Andreas Peters wrote: Hi, sorry for this non technical question. I already tried it unsuccessfully on other ways. :-( Does someone have access to the Twitter account of Mesos? The last tweet is already decades ;-) ago. Would be good if we can reactivate it. Regards, Andreas OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Apache Mesos Twitter Account
Hi, sorry for this non technical question. I already tried it unsuccessfully on other ways. :-( Does someone have access to the Twitter account of Mesos? The last tweet is already decades ;-) ago. Would be good if we can reactivate it. Regards, Andreas OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Seeking contributions to fix Mesos website build
I fixed the gem error. Just have to update ruby to a newer version. At
least, is working on my local system. :-)
https://github.com/apache/mesos/pull/444
Am 28.06.22 um 14:49 schrieb Andreas Peters:
Sorry, I'm sick since some days. :-(
I will try to fix the RubyGems issue.
@Dave, did u got my EMail? :-)
On 27.06.22 21:48, Charles-François Natali wrote:
The Jenkins configuration has been fixed, it now only fails on the
RubyGems errors:
https://ci-builds.apache.org/job/Mesos/job/Mesos-Websitebot/1307/console
Cheers,
On Fri, 24 Jun 2022 at 06:07, Andreas Peters
wrote:
I will have a look over weekend. :-)
On 24.06.22 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 cannot find the revision from the ASF gitbox, not from
GitHub,
are they mixed somehow?
Looking at the below the github url looks wrong, it should be
mesos-site.git not mesos.git, I'll fix.
However the original issue regarding the dependencies update might be
different altogether, might be good if someone - maybe Andreas? - could
have a look.
Cheers,
On Thu, Jun 23, 2022, 23:36 Tomek Janiszewski
wrote:
It looks like job configuration has changed and it's using GitHub
repo now
and could not find revision so build does not even start.
Now:
Cloning repository https://gitbox.apache.org/repos/asf/mesos-site.git
Avoid second fetch
> git rev-parse origin/asf-site^{commit} # timeout=10
> git rev-parse asf-site^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and
branch configuration for this job.
Finished: FAILURE
Before:
Cloning repository https://github.com/apache/mesos.git
Avoid second fetch
> git rev-parse origin/asf-site^{commit} # timeout=10
Checking out Revision f14e3b07149b7213aa3552c50ff059155b33effd
(origin/asf-site)
> git config core.sparsecheckout # timeout=10
> git checkout -f f14e3b07149b7213aa3552c50ff059155b33effd #
timeout=10
Commit message: "Updated
czw., 23 cze 2022, 23:16 użytkownik Dave Lester
napisał:
Hi all,
The build for the Mesos website is currently broken. It looks like
several
dependency updates via dependabot were merged into the codebase on
May
22nd
causing the issue along the way.
The last successful website build
https://ci-builds.apache.org/job/Mesos/job/Mesos-Websitebot/1268/ is
based on the revision cd71826, which was committed May 4th.
Can the two dependabot changes to “/site” be rolled back (9c7ccc2 and
9019e3a) or better yet is there a community member with Middleman
/ Ruby
debugging experience that can help fix the build?
Thanks,
Dave
--
AVENTER UG (haftungsbeschraenkt)
Köllner Chaussee 144
25337 Kölln-Reisiek
Phone: (+49)4121 - 235582 0
E-Mail: a...@aventer.biz
Internet: https://www.aventer.biz
Git: https://www.github.com/AVENTER-UG
Geschäftsführer/CEO: Andreas Peters
Unternehmenssitz/City: Kölln-Reisiek
Handelsregister beim Amtsgericht/Legal Court: Itzehoe
Handelsregister-Nummer/Company Registration Number: HRB 9995 PI
--
AVENTER UG (haftungsbeschraenkt)
Köllner Chaussee 144
25337 Kölln-Reisiek
Phone: (+49)4121 - 235582 0
E-Mail: a...@aventer.biz
Internet: https://www.aventer.biz
Git: https://www.github.com/AVENTER-UG
Geschäftsführer/CEO: Andreas Peters
Unternehmenssitz/City: Kölln-Reisiek
Handelsregister beim Amtsgericht/Legal Court: Itzehoe
Handelsregister-Nummer/Company Registration Number: HRB 9995 PI
OpenPGP_0x6A83F12541CFCCF9.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Re: Seeking contributions to fix Mesos website build
Sorry, I'm sick since some days. :-(
I will try to fix the RubyGems issue.
@Dave, did u got my EMail? :-)
On 27.06.22 21:48, Charles-François Natali wrote:
The Jenkins configuration has been fixed, it now only fails on the
RubyGems errors:
https://ci-builds.apache.org/job/Mesos/job/Mesos-Websitebot/1307/console
Cheers,
On Fri, 24 Jun 2022 at 06:07, Andreas Peters wrote:
I will have a look over weekend. :-)
On 24.06.22 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 cannot find the revision from the ASF gitbox, not from GitHub,
are they mixed somehow?
Looking at the below the github url looks wrong, it should be
mesos-site.git not mesos.git, I'll fix.
However the original issue regarding the dependencies update might be
different altogether, might be good if someone - maybe Andreas? - could
have a look.
Cheers,
On Thu, Jun 23, 2022, 23:36 Tomek Janiszewski wrote:
It looks like job configuration has changed and it's using GitHub repo now
and could not find revision so build does not even start.
Now:
Cloning repository https://gitbox.apache.org/repos/asf/mesos-site.git
Avoid second fetch
> git rev-parse origin/asf-site^{commit} # timeout=10
> git rev-parse asf-site^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and
branch configuration for this job.
Finished: FAILURE
Before:
Cloning repository https://github.com/apache/mesos.git
Avoid second fetch
> git rev-parse origin/asf-site^{commit} # timeout=10
Checking out Revision f14e3b07149b7213aa3552c50ff059155b33effd
(origin/asf-site)
> git config core.sparsecheckout # timeout=10
> git checkout -f f14e3b07149b7213aa3552c50ff059155b33effd # timeout=10
Commit message: "Updated
czw., 23 cze 2022, 23:16 użytkownik Dave Lester
napisał:
Hi all,
The build for the Mesos website is currently broken. It looks like
several
dependency updates via dependabot were merged into the codebase on May
22nd
causing the issue along the way.
The last successful website build
https://ci-builds.apache.org/job/Mesos/job/Mesos-Websitebot/1268/ is
based on the revision cd71826, which was committed May 4th.
Can the two dependabot changes to “/site” be rolled back (9c7ccc2 and
9019e3a) or better yet is there a community member with Middleman / Ruby
debugging experience that can help fix the build?
Thanks,
Dave
--
AVENTER UG (haftungsbeschraenkt)
Köllner Chaussee 144
25337 Kölln-Reisiek
Phone: (+49)4121 - 235582 0
E-Mail: a...@aventer.biz
Internet: https://www.aventer.biz
Git: https://www.github.com/AVENTER-UG
Geschäftsführer/CEO: Andreas Peters
Unternehmenssitz/City: Kölln-Reisiek
Handelsregister beim Amtsgericht/Legal Court: Itzehoe
Handelsregister-Nummer/Company Registration Number: HRB 9995 PI
--
AVENTER UG (haftungsbeschraenkt)
Köllner Chaussee 144
25337 Kölln-Reisiek
Phone: (+49)4121 - 235582 0
E-Mail: a...@aventer.biz
Internet: https://www.aventer.biz
Git: https://www.github.com/AVENTER-UG
Geschäftsführer/CEO: Andreas Peters
Unternehmenssitz/City: Kölln-Reisiek
Handelsregister beim Amtsgericht/Legal Court: Itzehoe
Handelsregister-Nummer/Company Registration Number: HRB 9995 PI
OpenPGP_0x6A83F12541CFCCF9.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Re: Seeking contributions to fix Mesos website build
I will have a look over weekend. :-)
On 24.06.22 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 cannot find the revision from the ASF gitbox, not from GitHub,
are they mixed somehow?
Looking at the below the github url looks wrong, it should be
mesos-site.git not mesos.git, I'll fix.
However the original issue regarding the dependencies update might be
different altogether, might be good if someone - maybe Andreas? - could
have a look.
Cheers,
On Thu, Jun 23, 2022, 23:36 Tomek Janiszewski wrote:
It looks like job configuration has changed and it's using GitHub repo now
and could not find revision so build does not even start.
Now:
Cloning repository https://gitbox.apache.org/repos/asf/mesos-site.git
Avoid second fetch
> git rev-parse origin/asf-site^{commit} # timeout=10
> git rev-parse asf-site^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and
branch configuration for this job.
Finished: FAILURE
Before:
Cloning repository https://github.com/apache/mesos.git
Avoid second fetch
> git rev-parse origin/asf-site^{commit} # timeout=10
Checking out Revision f14e3b07149b7213aa3552c50ff059155b33effd
(origin/asf-site)
> git config core.sparsecheckout # timeout=10
> git checkout -f f14e3b07149b7213aa3552c50ff059155b33effd # timeout=10
Commit message: "Updated
czw., 23 cze 2022, 23:16 użytkownik Dave Lester
napisał:
Hi all,
The build for the Mesos website is currently broken. It looks like
several
dependency updates via dependabot were merged into the codebase on May
22nd
causing the issue along the way.
The last successful website build
https://ci-builds.apache.org/job/Mesos/job/Mesos-Websitebot/1268/ is
based on the revision cd71826, which was committed May 4th.
Can the two dependabot changes to “/site” be rolled back (9c7ccc2 and
9019e3a) or better yet is there a community member with Middleman / Ruby
debugging experience that can help fix the build?
Thanks,
Dave
--
AVENTER UG (haftungsbeschraenkt)
Köllner Chaussee 144
25337 Kölln-Reisiek
Phone: (+49)4121 - 235582 0
E-Mail: a...@aventer.biz
Internet: https://www.aventer.biz
Git: https://www.github.com/AVENTER-UG
Geschäftsführer/CEO: Andreas Peters
Unternehmenssitz/City: Kölln-Reisiek
Handelsregister beim Amtsgericht/Legal Court: Itzehoe
Handelsregister-Nummer/Company Registration Number: HRB 9995 PI
OpenPGP_0x6A83F12541CFCCF9.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
cgroupv2 and mesos
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 not mount the subsystems like cpu, memory and so on, maybe we should remove these check lines? https://github.com/apache/mesos/blob/cd71826ab244db1f73e78fafe8a42181758a41e8/src/docker/docker.cpp#L146 I done it in my test environment and could not found a issue so far. Docker in newer versions run very well under cgroupsV2. That's why I' thinking, maybe the "precheck" makes no sense in that point. What do u think? Regards, Andreas OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Fix Mesos-Mini Pipeline
No problem Qian. :-) On 15.02.22 15:44, Qian Zhang wrote: Hi Andreas, Could you please create an infra ticket (similar to this one <https://issues.apache.org/jira/browse/INFRA-22262>) to ask the Apache infra team for help? Thanks! Regards, Qian Zhang On Tue, Feb 15, 2022 at 3:32 PM Andreas Peters wrote: Hi, the Mesos-Mini pipeline cannot find some credentials (ERROR: Could not find credentials entry with ID 'mesos-docker-bot'). Can someone take a look at it? :-) I'm also willing to help. https://builds.apache.org/job/Mesos/job/Docker/job/Mini/job/1.11.x/lastFailedBuild/console Thanks, Andreas OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Fix Mesos-Mini Pipeline
Hi, the Mesos-Mini pipeline cannot find some credentials (ERROR: Could not find credentials entry with ID 'mesos-docker-bot'). Can someone take a look at it? :-) I'm also willing to help. https://builds.apache.org/job/Mesos/job/Docker/job/Mini/job/1.11.x/lastFailedBuild/console Thanks, Andreas OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Mesos Packaging
Hi Renán, thanks for the info and that you are willing to help out. :-) Regards, Andreas On 01.09.21 21:55, 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 create a fork at https://github.com/mesos/ in order to add patches here and there to keep it compatible and up to date with newer distros. If some can make this happen, I'd like to volunteer to maintain it for now. -Renán OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Bintray is jfrog now
Hi Martin, thanks for the link. :-) I will update the link at the website and open a PR. I see the last two versions 1.10 and 1.11 are not there. Does someone know why? Regards, Andreas On 30.08.21 13:47, Martin Tzvetanov Grigorov wrote: Hi Andreas, I've noticed that Qian Zhang created this ticket: https://issues.apache.org/jira/browse/INFRA-22262 Mesos' files are now at https://apache.jfrog.io/ui/repos/tree/General/mesos Regards, Martin On 2021/08/16 08:56:18, Andreas Peters wrote: Hi, since bintray.com does not exists anymore, I was thinking to changes the download link at the mesos website. The question is, what shell I use instead as official source for the RPM files? Any ideas? I can also try to create a github workflow therefore we will have RPM releases there. Regards, Andreas OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bintray is jfrog now
Hi, since bintray.com does not exists anymore, I was thinking to changes the download link at the mesos website. The question is, what shell I use instead as official source for the RPM files? Any ideas? I can also try to create a github workflow therefore we will have RPM releases there. Regards, Andreas OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Welcome Charles-François Natali as Mesos Committer and PMC Member!
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 Apache Mesos project! Charles started contributing to Mesos a bit more than a year ago. During this time, he has discovered and fixed a significant number of issues in all corners of Mesos, from libprocess and the build system to the cgroups isolator, thus becoming the most active contributor since November 2020. Also, Charles has been helping a lot with JIRA triage, mentoring other contributors and moving forward a number of technical discussions. Charles, thanks for all your contributions so far and looking forward to continuing to work with you on the project! - Andrei -- AVENTER UG (haftungsbeschraenkt) Köllner Chaussee 144 25337 Kölln-Reisiek Phone: (+49)4121 - 235582 0 E-Mail: a...@aventer.biz Internet: https://www.aventer.biz Git: https://www.github.com/AVENTER-UG Geschäftsführer/CEO: Andreas Peters Unternehmenssitz/City: Kölln-Reisiek Handelsregister beim Amtsgericht/Legal Court: Itzehoe Handelsregister-Nummer/Company Registration Number: HRB 9995 PI Diese E-Mail kann vertrauliche und/oder rechtlich geschützte Informationen enthalten. Wenn Sie nicht der beabsichtigte Empfänger sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender telefonisch oder per E-Mail und löschen Sie diese E-Mail aus Ihrem System. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This email can be confidential and/or legally protected Information included. If you are not the intended recipient or have received this e-mail in error, inform your contact and the sender immediately by phone or email and delete this email from your system. Unauthorized copying as well the unauthorized forwarding of this mail is not permitted. OpenPGP_0x6A83F12541CFCCF9.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Apache Mesos CI on ARM64
Hi! > Should we ask Mesos on ARM for new machine? Is anybody interested in having > ARM CI? I think, if it does not take to much time for us then it would be a good idea to build the packages for ARM again. :-) Best, Andreas OpenPGP_signature Description: OpenPGP digital signature
Re: Old Jira Tasks
Hi Charles, yeah u are right, that's definitely a point we have to keep in mind. To be sure that we don't misunderstand each other; I mean bugs reported by users, not by the committers. :-) First of all, maybe we should clean up all the old and untouched questions/wishes/improvments? Cheers, Andreas Am 31.05.21 um 19:02 schrieb Charles-François Natali: > 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 2021 à 09:05, Andreas Peters a > écrit : >> >> Hi, >> >> just to discuss! :-) Does it makes sense to close all abandoned bug >> reports older then (maybe) two years? >> >> I have no idea if the bugs still exists, and it's not even easy to get >> feedback of much younger Jira tasks. >> >> What do u think? >> >> Cheers, >> Andreas >> >> OpenPGP_signature Description: OpenPGP digital signature
Old Jira Tasks
Hi, just to discuss! :-) Does it makes sense to close all abandoned bug reports older then (maybe) two years? I have no idea if the bugs still exists, and it's not even easy to get feedback of much younger Jira tasks. What do u think? Cheers, Andreas OpenPGP_signature Description: OpenPGP digital signature
MESOS-10219: How to handle patches
Hi, how we handle patches like this on? https://issues.apache.org/jira/browse/MESOS-10219 The target system is windows! I can only review the code but (unlike linux) I have nothing to test it. Cheers, Andreas OpenPGP_signature Description: OpenPGP digital signature
Re: Discuss the possible technical directions of Mesos
Hi Qian, great list and good ideas. Maybe we can also add some new features to the mesos_cli? > I feel that we should not position Mesos as a generic container > orchestrator, instead we should find a specific scenario for it, maybe HPC > is a good direction? My customers always tell me, they like and still use Mesos because it do not give them borders. They can use containers but they don't have to. And (maybe that's the biggest advantage), they can develope there own framework for there specific case. So, I think, HPC is definitely a very interesting direction, but we should not be too specific. :-) Cheers, Andreas OpenPGP_signature Description: OpenPGP digital signature
Re: Permissions to close Jira Issues
Yes perfect. Now it's there. Thanks. :-) Am 20.05.21 um 11:55 schrieb Andrei Sekretenko: > Looks like the "Contributors" group of the JIRA project should have > this permission; I've just added you there manually, now it should > work, please try again. > > I don't remember if there has ever been any automation to fill this > group based on 'contributors.yaml'. > > On Thu, 20 May 2021 at 11:33, Andreas Peters wrote: >> >> Hi Qian, >> >> yes thats what I mean. But there is nothing to mark it as resolved. :-( >> >> Regards, >> Andreas >> >> Am 20.05.21 um 10:22 schrieb Qian Zhang: >>> Hi Andreas >>> >>> Do you mean marking issues in https://issues.apache.org/jira/ as resolved? >>> I do not think you need special permission to do that. >>> >>> >>> Regards, >>> Qian Zhang >>> >>> >>> On Thu, May 20, 2021 at 3:18 PM Andreas Peters >>> wrote: >>> >>>> Hey, >>>> >>>> >>>> what I have to do, to get the permissions to close issues in "our" Jira? >>>> >>>> >>>> Regards, >>>> Andreas >>>> >>>> >>> >> >> -- >> AVENTER UG (haftungsbeschraenkt) >> Köllner Chaussee 144 >> 25337 Kölln-Reisiek >> >> Phone: (+49)4121 - 235582 0 >> E-Mail: a...@aventer.biz >> Internet: https://www.aventer.biz >> Git: https://www.github.com/AVENTER-UG >> >> Geschäftsführer/CEO: Andreas Peters >> Unternehmenssitz/City: Kölln-Reisiek >> Handelsregister beim Amtsgericht/Legal Court: Itzehoe >> Handelsregister-Nummer/Company Registration Number: HRB 9995 PI >> >> Diese E-Mail kann vertrauliche und/oder rechtlich geschützte >> Informationen enthalten. Wenn Sie nicht der beabsichtigte Empfänger >> sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie >> bitte sofort den Absender telefonisch oder per E-Mail und löschen >> Sie diese E-Mail aus Ihrem System. Das unerlaubte Kopieren sowie >> die unbefugte Weitergabe dieser Mail ist nicht gestattet. >> >> >> This email can be confidential and/or legally protected >> Information included. If you are not the intended recipient >> or have received this e-mail in error, inform your >> contact and the sender immediately by phone or email and delete this >> email from your system. Unauthorized copying as well >> the unauthorized forwarding of this mail is not permitted. >> -- AVENTER UG (haftungsbeschraenkt) Köllner Chaussee 144 25337 Kölln-Reisiek Phone: (+49)4121 - 235582 0 E-Mail: a...@aventer.biz Internet: https://www.aventer.biz Git: https://www.github.com/AVENTER-UG Geschäftsführer/CEO: Andreas Peters Unternehmenssitz/City: Kölln-Reisiek Handelsregister beim Amtsgericht/Legal Court: Itzehoe Handelsregister-Nummer/Company Registration Number: HRB 9995 PI Diese E-Mail kann vertrauliche und/oder rechtlich geschützte Informationen enthalten. Wenn Sie nicht der beabsichtigte Empfänger sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender telefonisch oder per E-Mail und löschen Sie diese E-Mail aus Ihrem System. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This email can be confidential and/or legally protected Information included. If you are not the intended recipient or have received this e-mail in error, inform your contact and the sender immediately by phone or email and delete this email from your system. Unauthorized copying as well the unauthorized forwarding of this mail is not permitted. OpenPGP_signature Description: OpenPGP digital signature
Re: Permissions to close Jira Issues
Hi Qian, yes thats what I mean. But there is nothing to mark it as resolved. :-( Regards, Andreas Am 20.05.21 um 10:22 schrieb Qian Zhang: > Hi Andreas > > Do you mean marking issues in https://issues.apache.org/jira/ as resolved? > I do not think you need special permission to do that. > > > Regards, > Qian Zhang > > > On Thu, May 20, 2021 at 3:18 PM Andreas Peters > wrote: > >> Hey, >> >> >> what I have to do, to get the permissions to close issues in "our" Jira? >> >> >> Regards, >> Andreas >> >> > -- AVENTER UG (haftungsbeschraenkt) Köllner Chaussee 144 25337 Kölln-Reisiek Phone: (+49)4121 - 235582 0 E-Mail: a...@aventer.biz Internet: https://www.aventer.biz Git: https://www.github.com/AVENTER-UG Geschäftsführer/CEO: Andreas Peters Unternehmenssitz/City: Kölln-Reisiek Handelsregister beim Amtsgericht/Legal Court: Itzehoe Handelsregister-Nummer/Company Registration Number: HRB 9995 PI Diese E-Mail kann vertrauliche und/oder rechtlich geschützte Informationen enthalten. Wenn Sie nicht der beabsichtigte Empfänger sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender telefonisch oder per E-Mail und löschen Sie diese E-Mail aus Ihrem System. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This email can be confidential and/or legally protected Information included. If you are not the intended recipient or have received this e-mail in error, inform your contact and the sender immediately by phone or email and delete this email from your system. Unauthorized copying as well the unauthorized forwarding of this mail is not permitted. OpenPGP_signature Description: OpenPGP digital signature
Permissions to close Jira Issues
Hey, what I have to do, to get the permissions to close issues in "our" Jira? Regards, Andreas OpenPGP_signature Description: OpenPGP digital signature
Re: New PMC Chair
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 *Qian Zhang* for becoming the new Apache Mesos > PMC chair and VP of the project. > > Thanks, > OpenPGP_signature Description: OpenPGP digital signature
Re: [VOTE] Move Apache Mesos to Attic
Sounds good, thanks Vinod. :-) Andreas Am 15.04.21 um 00:49 schrieb Vinod Kone: > To circle back here, the vote to install a new PMC chair has passed and the > request for the same is sent to the ASF Board. It will become official once > the board meets and passes the resolution. I am expecting this to happen > around the end of the month. > > On Fri, Apr 9, 2021 at 9:33 AM Andreas Peters wrote: > >> Thanks Vinod. :-) >> >> >> >> >> Am 09.04.21 um 01:55 schrieb Vinod Kone: >>> Hi folks, >>> >>> Thanks for further responses and strong interest from a few folks in >>> keeping the project going! >>> >>> I also had a chance to talk to some ASF members and it sounds like the >> ASF >>> preferred option forward in this situation is to keep the project going >> in >>> ASF. >>> >>> Given all the above, I'm cancelling this vote thread. >>> >>> I will start another thread to elect a new PMC chair and let them handle >>> adding new PMC members / committers. >>> >>> Thanks, >>> >>> >>> On Thu, Apr 8, 2021 at 4:30 PM Samuel Marks wrote: >>> >>>> In reference to new responses: >>>> 0. If you need a 501c3 equivalent to hold the copyright, I run a charity >>>> concentrating on facilitating large-scale screening programmes and >> intend >>>> to use Mesos to handle multiple clusters on the same set of servers ( >>>> https://sydneyscientific.org), and would be happy to be that >> placeholder >>>> and potentially fund further R&D >>>> 1. On the moving CI side I remember years ago adding an issue about OOM >> for >>>> building it on a small AWS instance and it being closed as wontfix. >>>> Hopefully time is spent on refactoring and modularity to get over this, >>>> making moving to anyones CI viable >>>> 2. The Apache brand alone makes Mesos more attractive; so would hate to >>>> lose it >>>> >>>> Just my 2¢ >>>> >>>> Samuel Marks >>>> Charity | consultancy | open-source | LinkedIn >>>> >>>> On Fri, 9 Apr 2021, 5:02 am Andreas Peters, >>>> wrote: >>>> >>>>>> Hopefully the other people who said they >>>>>> were interested, like the guys from Criteo, Andreas, Javi, etc would >>>>>> help too. >>>>> >>>>> I will and I'm sure the others too. I already try to help with the >>>>> tickets in jira. Thanks to Benjamin Mahler who told me that it's ok if >> I >>>>> do it. >>>>> >>>>> Andreas >>>>> >>>>> >>>> >>> >> >> > -- AVENTER UG (haftungsbeschraenkt) Köllner Chaussee 144 25337 Kölln-Reisiek Phone: (+49)4121 - 235582 0 E-Mail: a...@aventer.biz Internet: https://www.aventer.biz Git: https://www.github.com/AVENTER-UG Geschäftsführer/CEO: Andreas Peters Unternehmenssitz/City: Kölln-Reisiek Handelsregister beim Amtsgericht/Legal Court: Itzehoe Handelsregister-Nummer/Company Registration Number: HRB 9995 PI Diese E-Mail kann vertrauliche und/oder rechtlich geschützte Informationen enthalten. Wenn Sie nicht der beabsichtigte Empfänger sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender telefonisch oder per E-Mail und löschen Sie diese E-Mail aus Ihrem System. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This email can be confidential and/or legally protected Information included. If you are not the intended recipient or have received this e-mail in error, inform your contact and the sender immediately by phone or email and delete this email from your system. Unauthorized copying as well the unauthorized forwarding of this mail is not permitted. OpenPGP_signature Description: OpenPGP digital signature
Re: [VOTE] Move Apache Mesos to Attic
Thanks Vinod. :-) Am 09.04.21 um 01:55 schrieb Vinod Kone: > Hi folks, > > Thanks for further responses and strong interest from a few folks in > keeping the project going! > > I also had a chance to talk to some ASF members and it sounds like the ASF > preferred option forward in this situation is to keep the project going in > ASF. > > Given all the above, I'm cancelling this vote thread. > > I will start another thread to elect a new PMC chair and let them handle > adding new PMC members / committers. > > Thanks, > > > On Thu, Apr 8, 2021 at 4:30 PM Samuel Marks wrote: > >> In reference to new responses: >> 0. If you need a 501c3 equivalent to hold the copyright, I run a charity >> concentrating on facilitating large-scale screening programmes and intend >> to use Mesos to handle multiple clusters on the same set of servers ( >> https://sydneyscientific.org), and would be happy to be that placeholder >> and potentially fund further R&D >> 1. On the moving CI side I remember years ago adding an issue about OOM for >> building it on a small AWS instance and it being closed as wontfix. >> Hopefully time is spent on refactoring and modularity to get over this, >> making moving to anyones CI viable >> 2. The Apache brand alone makes Mesos more attractive; so would hate to >> lose it >> >> Just my 2¢ >> >> Samuel Marks >> Charity | consultancy | open-source | LinkedIn >> >> On Fri, 9 Apr 2021, 5:02 am Andreas Peters, >> wrote: >> >>>> Hopefully the other people who said they >>>> were interested, like the guys from Criteo, Andreas, Javi, etc would >>>> help too. >>> >>> I will and I'm sure the others too. I already try to help with the >>> tickets in jira. Thanks to Benjamin Mahler who told me that it's ok if I >>> do it. >>> >>> Andreas >>> >>> >> > OpenPGP_signature Description: OpenPGP digital signature
Re: [VOTE] Move Apache Mesos to Attic
> Hopefully the other people who said they > were interested, like the guys from Criteo, Andreas, Javi, etc would > help too. I will and I'm sure the others too. I already try to help with the tickets in jira. Thanks to Benjamin Mahler who told me that it's ok if I do it. Andreas OpenPGP_signature Description: OpenPGP digital signature
Re: [VOTE] Move Apache Mesos to Attic
As I see, Andrei you are sitting close to me (Hamburg, Germany), thats just 30km away from me. :-) It would make mentoring more easy, if we can see each other (of course, after covid). So, Andrei provide to be a mentor, I provide to be his student. :-) Cheers, Andreas OpenPGP_signature Description: OpenPGP digital signature
Re: [VOTE] Move Apache Mesos to Attic
> - Given the discussions here that show there are likely new contributors > who want to help build Apache Mesos, don't worry about the Attic. We/there are a couple of peoples who want to be contributors and help to build Mesos. :-) > Trademarks are about *products*. Using github.com/mesos/mesos as an > organization and project outside the ASF is not a good idea. Forking > /ghuser/mesos/ and then trying to build a whole new community to ship > Mesos software to the world is not a good idea. Building a new product > called M-Cloud, Powered By Apache Mesos would be fine, however. OK, thanks for clarify this point. > It doesn't matter if it's ever going to be close to K8s, all that matters is > if people are using > it and want to keep maintaining it here for their own workloads - if > there are folks who want to do that, then just step up and it can happen. You are speaking from my soul. Cheers, Andreas OpenPGP_signature Description: OpenPGP digital signature
Re: [VOTE] Move Apache Mesos to Attic
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 bet > is you'll need a new name. Does it mean, "my" fork cannot called Mesos? If it's so, then please do not move Mesos in the attic. There are peoples who like to care Mesos but if we have to rename it, then it's like you kill it. Cheers, Andreas OpenPGP_signature Description: OpenPGP digital signature
