Re: Add JIRA ticket# to `TODO`s in comments

+1 for adding TODO(MESOS-) to the style guide as a soft requirement. I don't think it should be strictly required, since sometimes creating a JIRA ticket just doesn't make sense, but I do have the feeling that in *most* cases, our process would benefit from creating a JIRA at the moment a TODO

Re: Backticks in comments

Hello everyone! FYI, here's the review for the backtick style guide change: https://reviews.apache.org/r/40367/ Greg On Fri, Nov 6, 2015 at 7:55 AM, Greg Mann <g...@mesosphere.io> wrote: > Thanks for the input y'all, sounds like we have a general consensus for > backticks in comment

Backticks in comments

Hey folks! I wanted to bring up a style issue that I noticed recently. In some comments in the codebase, backticks are used to quote code excerpts and object names, while in other comments, single quotes are used. This doesn't seem to be documented in our style guide (nor in Google's), and I think

Re: New Cloud Foundry Framework - Mesos & CloudFoundry Integration

I think that the Mesos org. on github (https://github.com/mesos) hosts similar projects, so perhaps that would be a suitable location? On Thu, Nov 5, 2015 at 2:09 PM, Marco Massenzio wrote: > Hey Deepak, > > that's really exciting, great stuff! > > As Alex correctly pointed

Re: Backticks in comments

.io> wrote: > +1 for backticks! > > > On 02 Nov 2015, at 19:32, Greg Mann <g...@mesosphere.io> wrote: > > > > Hey folks! > > I wanted to bring up a style issue that I noticed recently. In some > > comments in the codebase, backticks are used to quote co

Re: Executor can't start d-bus communication

t; > After I started all components as user, its worked. > > I wrote the executor using the Executor APIs. By creating a new class. > > Thanks for your reply. > > Regards, > Pradeep > > > On 14 October 2015 at 17:18, Greg Mann <g...@mesosphere.io> wrote: &

Re: Executor can't start d-bus communication

Hi Pradeep, Can you tell us a bit about your executor: in particular, did you write it against the Executor API , or is it a plain executable that gets run through the command executor? Cheers, Greg On Wed, Oct 14,

Re: [VOTE] Release Apache Mesos 0.25.0 (rc2)

Successfully built `sudo make distcheck` on CentOS 7.1 and Ubuntu 14.04 with only expected test failures. On our Fedora 22 CI build, however, while the tests are building the following compile-time error is produced: [17:18:46][Step 4/6] CXX

Re: Community Sync Interval

I agree with Daniel, +1 for weekly and we can re-evaluate in a bit to see how people are liking it. On Thu, Oct 15, 2015 at 3:33 PM, Guangya Liu wrote: > +1 for bi-weekly > > Thanks, > > Guangya > > On Fri, Oct 16, 2015 at 6:08 AM, Daniel Mercer >

Re: More Project Structure in JIRA

+1 On Tue, Oct 20, 2015 at 9:50 AM, tommy xiao wrote: > +1 Yes please! > > 2015-10-19 16:09 GMT+08:00 Alexander Rojas : > > > +1 Yes please! > > > > > On 15 Oct 2015, at 10:11, Bernd Mathiske wrote: > > > > > > Proposal: in

Re: Proposal: moving Mesos website to project codebase

+1 to incorporating the mesos-website-container, I've found that very helpful for catching formatting issues when making documentation changes. (thanks Artem! :-) On Fri, Oct 9, 2015 at 2:33 PM, Jonathon Rossi wrote: > Adam, I wasn't aware of >

Re: Speed up Mesos tests

AlexR, thanks for this great work! :-D It's nice to hear that so many tests have been added in the past year, and I appreciate the list of tickets to check out; I'll definitely take one on soon when I have some time. I'd like to bring up something that both Neil and Joseph mentioned to me

Mesos build & testing environment instructions

Hey folks! Something occurred to me recently which is related to the extensive testing we did in preparation for the 0.26.0 release. Since I started contributing to the project, my Source of Truth for "how to prepare a given platform to compile and run Mesos" has been the Getting Started page of

0.26.0 blocker: CFS cgroups

Hello all! It's recently come up in MESOS-3964 ( https://issues.apache.org/jira/browse/MESOS-3964) that some kernels currently in use (including in the latest Debian) do not have cgroup support for CFS. Due to this, LimitedCpuIsolatorTest.ROOT_CGROUPS_Cfs and

Re: WebUI authentication in 1.0.0-rc1

Benno, Would you mind providing more information on the ACL definitions that you used to gain full access to the web UI? I'm working on some more documentation for this. Also, did you have authorization enabled on the agents as well? Cheers, Greg On Wed, Jun 8, 2016 at 7:43 AM, Neil Conway

Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm - 4pm (Apache Mesos)

nel - Slack, HipChat, IRC? - AI [Vinod] : Email dev@ and user@ about using Slack as canonical communication channel On Wed, Jun 15, 2016 at 6:46 PM, Greg Mann <g...@mesosphere.io> wrote: > Also note: tomorrow's community sync will be hosted at Mesosphere HQ, 88

Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm - 4pm (Apache Mesos)

Also note: tomorrow's community sync will be hosted at Mesosphere HQ, 88 Stevenson St., San Francisco, CA. Community members are welcome to attend in person! As usual, Google Hangout and Youtube links for the meeting will be posted in the Google doc just before the meeting begins. Cheers, Greg

Re: Inconsistent naming of support scripts

+1 On Thu, Feb 11, 2016 at 11:41 AM, Vinod Kone wrote: > Some the scripts in the "support" directory have dashes ("-") in their > names (e.g., apply-review.sh, apply-reviews.py), whereas some have > underscores ("_") (e.g., docker_build.sh, mesos_split.py). > > This is

Version numbers in docs

Hi all! In our docs, you find such sentences as: "Mesos 0.15.0 added support for framework authentication, and 0.19.0 added slave authentication." It's a minor point, but I wonder how long we should maintain such version numbers in the docs? In the example above, my feeling is that we are far

Design Doc: HTTP Stream IDs for Mesos Schedulers

Hey folks, As part of the HTTP scheduler API, we've been designing "stream IDs" which can be used to uniquely identify HTTP framework instances; this makes the protocol more robust in the face of some failover scenarios. The current design document for this feature can be found here

Re: [VOTE] Release Apache Mesos 0.24.2 (rc1)

+1 (non-binding) `sudo make check` on Ubuntu 14.04, using gcc with libevent and SSL enabled. All tests pass except MemoryPressureMesosTest.CGROUPS_ROOT_Statistics, which is a known failure in 0.24. Cheers, Greg On Mon, Feb 29, 2016 at 11:20 AM, Kapil Arya wrote: > +1

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

+1 (non-binding) `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL enabled. All tests pass except MemoryPressureMesosTest.CGROUPS_ROOT_Statistics, which seems to be due to the issue found here: https://issues.apache.org/jira/browse/MESOS-4053 On Mon, Feb 29, 2016 at 2:17 PM,

Re: [VOTE] Release Apache Mesos 0.26.1 (rc1)

+1 (non-binding) `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL enabled. All tests pass except: PerfEventIsolatorTest.ROOT_CGROUPS_Sample, which is covered here: https://issues.apache.org/jira/browse/MESOS-4655 CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf,

Re: [VOTE] Release Apache Mesos 0.27.2 (rc1)

gt;>> Fedora 23: `make check` non-root OK > >>> OS X: `make check` non-root OK > >>> Ubuntu 14.04: `make check` non-root, three failures: > >>> ContainerLoggerTest.DefaultToSandbox [flaky, tracked in MESOS-4615] > >>> MasterQuotaTest.AvailableResourcesAfterRescinding [flaky, tracked in >

Re: [VOTE] Release Apache Mesos 0.25.1 (rc1)

I was also able to successfully test a simple upgrade scenario between 0.24.2-rc1 and 0.25.1-rc1 using Niklas's upgrade testing script, which I've modified slightly and reposted here: https://reviews.apache.org/r/44229/ On Tue, Mar 1, 2016 at 9:29 AM, Greg Mann <g...@mesosphere.io> wrote:

Re: [VOTE] Release Apache Mesos 0.26.1 (rc2)

+1 (non-binding) Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. All tests pass. I was also able to successfully test a simple upgrade scenario from 0.25.1-rc2 to 0.26.1-rc2 using the script found here: https://reviews.apache.org/r/44229/ Cheers, Greg On Tue, Mar

Re: [VOTE] Release Apache Mesos 0.24.2 (rc2)

+1 (non-binding) Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. All tests pass. I was also able to successfully test a simple upgrade scenario from 0.23.1 to 0.24.2-rc2 using the script found here: https://reviews.apache.org/r/44229/ Cheers, Greg On Tue, Mar 8,

Re: [VOTE] Release Apache Mesos 0.25.1 (rc2)

+1 (non-binding) Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. The following tests failed during the first test run: ContainerizerTest.ROOT_CGROUPS_BalloonFramework MemoryPressureMesosTest.CGROUPS_ROOT_Statistics MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery

Re: [VOTE] Release Apache Mesos 0.28.0 (rc2)

+1 (non-binding) Ran `sudo make check` on CentOS 7 and Ubuntu 14.04, using gcc with libevent and SSL enabled. On CentOS 7, all tests passed. On Ubuntu 14.04, one test failed: MemoryPressureMesosTest.CGROUPS_ROOT_Statistics. This is a flaky test; it passes most of the time. While there have been

Re: Shepherd for MESOS-4744

I can help review this one. Jian, feel free to add me as reviewer when you post your patch, my reviewboard username is 'greggomann'. Cheers, Greg On Mon, Mar 14, 2016 at 3:09 PM, Michael Park wrote: > I suspect this will be a simple change. > I'm willing to shepherd this if

Re: [VOTE] Release Apache Mesos 0.28.1 (rc2)

+1 (non-binding) Ran `sudo make check` on CentOS 7 with libevent and SSL enabled; all tests pass. I was also able to successfully simulate a simple upgrade scenario using 'test-upgrade.py'. Note that this initially failed due to some changes made to the test framework in this release, but after

[Proposal] Remove the default value for agent work_dir

Hey folks! A number of situations have arisen in which the default value of the Mesos agent `--work_dir` flag (/tmp/mesos) has caused problems on systems in which the automatic cleanup of '/tmp' deletes agent metadata. To resolve this, we would like to eliminate the default value of the agent

Mesos Community Sync 4/7/16 - Notes

Hey Mesos community, Find below the notes from our last Mesos Community Sync meeting, which occurred on 4/7/2016 at 9am PST. The next community sync will be on 4/21/2016 from 3-4pm PST. See the Mesos community calendar for upcoming meetings (note that you can

Re: [3/9] mesos git commit: Added agent flags for HTTP authentication.

f/mesos/tree/40138729 >> Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/40138729 >> >> Branch: refs/heads/master >> Commit: 401387299a04b71f62021adc6ee5e7545ac63376 >> Parents: a1482ac >> Author: Greg Mann &

Re: [VOTE] Release Apache Mesos 0.28.0 (rc1)

+1 (non-binding) `make check` and `sudo make check` on OSX 10.10.5 and CentOS 7.1, with libevent and SSL enabled. All tests pass on CentOS 7.1 When running the sudo tests on OSX, three failures were observed: ExamplesTest.JavaFramework is tracked by

Re: [jira] [Updated] (MESOS-3583) Introduce stream IDs in HTTP Scheduler API

API >> > -- >> > >> > Key: MESOS-3583 >> > URL: https://issues.apache.org/jira/browse/MESOS-3583 >> > Project: Mesos >> > Issue Type: Task >> &

Re: [VOTE] Release Apache Mesos 0.25.1 (rc1)

+1 (non-binding) `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL enabled. All tests pass except: PerfEventIsolatorTest.ROOT_CGROUPS_Sample, which is covered here: https://issues.apache.org/jira/browse/MESOS-4655 CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf,

Mesos Community Sync Notes

Hello all! Today we had another Mesos community sync meeting; find the notes pasted below. Of particular interest is our new roadmap document , which outlines items planned for development within the next six months. For

Persistent Volume API Change

Hello all, I'm currently working on MESOS-5005 , which is fixing a small bug in the persistent volumes API. When a new persistent volume is created, a `DiskInfo` message is included in the disk resources of the volume. Nested within another message

Community Sync Notes

Hello all! We had some great discussion yesterday during the Mesos community sync, you can find the notes below. Cheers, Greg Mesos Developer Community Sync http://mesos.apache.org/community/ May 19, 2016 Time: 3pm PST Location: Mesosphere HQ Attendees: Mesosphere: Greg M., Gilbert,

Re: Notification: Community Meeting @ Thu May 5, 2016 9pm - 10pm (Apache Mesos)

Hey all, I have to apologize; I told MPark that I would start a hangout last night for the community sync and I neglected to do so :-( Haosdent, I'm sorry for not having anything set up!! We planned a sync at this time to attract attendees from your region, so it's a shame to miss that

Re: [Proposal] Remove the default value for agent work_dir

t; >> On Tue, Apr 12, 2016 at 9:31 PM, Jie Yu <yujie@gmail.com> wrote: >> >>> +1 >>> >>> On Tue, Apr 12, 2016 at 9:29 PM, James Peach <jor...@gmail.com> wrote: >>> >>> > >>> > > On Apr 12, 2016, at 3:58 PM, G

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

+1 (non-binding) * Ran `sudo make distcheck` successfully on CentOS 7.1 with only one test failure: ExamplesTest.PythonFramework fails for me the first time it's executed as part of the whole test suite, and then succeeds on subsequent executions. I'm investigating further, and will file a ticket

Re: Notification: Community Meeting @ Thu Aug 11, 2016 3pm - 4pm (Apache Mesos)

See you all at the community meeting in a few hours! If you have any items you'd like to discuss, take a minute to add them to the agenda here . Google Hangout and YouTube links will be added to that document a

Re: [VOTE] Release Apache Mesos 1.0.1 (rc1)

+1 (non-binding): * Ran "sudo make distcheck" on CentOS 7 with libevent and SSL enabled. All tests passed. * Used "test-upgrade.py" to test upgrades from 0.28.2 -> 1.0.1 and 1.0.0 -> 1.0.1; both were successful. Cheers, Greg On Wed, Aug 10, 2016 at 5:32 PM, Vinod Kone

Re: [VOTE] Release Apache Mesos 1.0.1 (rc1)

Whoops! Sorry y'all, my wires got crossed :) I ran these tests on Ubuntu 14.04. G On Fri, Aug 12, 2016 at 12:50 PM, Greg Mann <g...@mesosphere.io> wrote: > +1 (non-binding): > > * Ran "sudo make distcheck" on CentOS 7 with libevent and SSL enabled. All > tests passe

Re: Validate lamba function in `Flags::add` for required parameters

Thanks for bringing this up, Klaus - in this case, I think that extra argument appears simply to match the desired function overload. Over time, the overloads for `FlagsBase::add` have multiplied considerably; It looks like we have about 20 now :-) I think it would be really nice to clean these up

Re: Notification: Community Meeting @ Fri Jul 1, 2016 6am - 7am (Apache Mesos)

Hi all, I hate to say, I failed to host the sync again at this time slot last night! After a long day at the office, I came home and was actually sitting at my computer the entire time! :-( Jay Guo, I notice that you were on Slack asking about the meeting - I apologize, I even had Slack open but I

Re: Welcome Neil Conway as Mesos Committer and PMC member!

Congratulations Neil!!! :D On Sun, Jan 22, 2017 at 4:46 PM, Neil Conway wrote: > Thanks for the kind words, everyone! It's been a pleasure to be a part > of the Mesos community, and I'm looking forward to continuing to > contribute. > > Neil > > On Sun, Jan 22, 2017 at

Re: Is there any plan to enhance authentication and authorization feature?

Hi Jared, As Vinod said, if you're using the default Mesos authenticators, the only way to update the dictionary of credentials is to restart the master/agent process. Note, however, that the authentication system is modular, so you could also write a custom authenticator which permits dynamic

Re: Welcome Kevin Klues as a Mesos Committer and PMC member!

Woowoo! Congrats Kevin!! On Wed, Mar 1, 2017 at 2:26 PM, Avinash Sridharan wrote: > Awesome !! Congrats Kevin !! > > On Wed, Mar 1, 2017 at 2:07 PM, Jie Yu wrote: > >> Congrats! Kevin! Well deserved! >> >> On Wed, Mar 1, 2017 at 2:05 PM, Benjamin

Re: [VOTE] Release Apache Mesos 1.2.0 (rc2)

I wanted to give a heads up on a flaky test failure I've encountered while testing this RC: 'DockerRuntimeIsolatorTest.ROO T_INTERNET_CURL_DockerDefaultEntryptRegistryPuller'. One issue related to this test was resolved recently (https://issues.apache.org/ jira/browse/MESOS-6001), but this seems

Re: Adding "syntax=proto2" to Mesos public protobuf files

AFAICT, this shouldn't break anything, since by omitting the syntax specification we're effectively setting it to the default, "proto2". As a quick test, I added `syntax = "proto2";` to the top of mesos.proto, built Mesos, and then ran some tests - it seems to work fine! Greg On Tue, Sep 6,

Re: Mesos 1.0.1-2.0.93.centos65 error on rpm installation.

Hi Sarjeet, Sorry for the delayed reply! I was just able to install Mesos 1.0.1 successfully on CentOS 6.6 by doing the following: sudo rpm -Uvh http://repos.mesosphere.com/el/6/noarch/RPMS/mesosphere-el-repo-6-0.noarch.rpm sudo yum install mesos Note that this ends up installing a

Re: mesos git commit: Added `DEFAULT_ROLE` constant to persistent volume tests.

, could you submit a patch to update it to `DEFAULT_TEST_ROLE`? > > Thanks! > > MPark > > On Thu, Sep 22, 2016 at 9:37 PM, Greg Mann <g...@mesosphere.io> wrote: > > > Good point, I think `DEFAULT_TEST_ROLE` would be better. I was indeed > > hoping to make use of this in oth

Re: mesos git commit: Added `DEFAULT_ROLE` constant to persistent volume tests.

Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/c2b595e1 > > Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/c2b595e1 > > Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/c2b595e1 > > > > Branch: refs/heads/master > > Commit: c2b595e1c59bb23e3

Re: A Plan for Mesos Community Syncs

+1 Thanks MPark! I've dropped the ball several times recently and forgotten to set up hangouts for these meetings, so I can also accept some of the responsibility for the decline in consistency and attendance; my apologies. I'm happy to help out going forward MPark, let me know if you need

Re: Question about mesos authentication and authorization?

Hi Jared, The default authenticator modules included with Mesos only support storing the credentials in a file on disk. However, Mesos exposes an authenticator module interface which can be used to implement more complex authentication scenarios. Note that there are authenticator module interfaces

Re: Welcome Guangya Liu as Mesos Committer and PMC member!

Congratulations Guangya!!! :D On Fri, Dec 16, 2016 at 11:10 AM, Jie Yu wrote: > Hi folks, > > Please join me in formally welcoming Guangya Liu as Mesos Committer and PMC > member. > > Guangya has worked on the project for more than a year now and has been a > very active

Re: Welcome Haosdent Huang as Mesos Committer and PMC member!

Congratulations Haosdent!!! :D On Fri, Dec 16, 2016 at 11:08 AM, Zhitao Li wrote: > Congrats Haosdent! Well deserved! > > So glad and honored to work with you! Very impressed with your amount of > contribution on many tasks. > > > > On Fri, Dec 16, 2016 at 10:59 AM, Vinod

Re: Need help!

820 master.cpp:6841] Updating the state of task > 324.0.0-9947ffab-b8f5-4925-94d8-12c7814ec572 of framework > 9947ffab-b8f5-4925-94d8-12c7814ec572 (latest state: TASK_FINISHED, status > update state: TASK_FINISHED) > > Thanks a lot for you help, > > - Venkat >

Re: Need help!

Venkat, There should be some information in the master logs to help you debug. In the case of a successful status update, you will see something like the following: master.cpp:5848] Status update TASK_RUNNING (UUID: ccb9beae-d62c-40f1-9d4e-9b6153cb0fff) for task test-task of framework

Re: [VOTE] Release Apache Mesos 0.28.3 (rc1)

+1 (non-binding) Did `sudo make check` on CentOS 7. Aside from several LinuxFilesystemIsolatorTests and two other flaky tests, CgroupsAnyHierarchyWithFreezerTest.ROOT_CGROUPS_DestroyTracedProcess and MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery, everything passed. Cheers, Greg On Wed, Nov

Re: [MESOS-6240] Allow executor/agent communication over non-TCP/IP stream socket.

Hi Bingqiang, I've had some recent discussions with folks about this feature; it's something we are interested in doing but I'm not sure what its priority is in relation to other tickets. While the AF_UNIX address type has been added to libprocess, libprocess does not currently accept domain

Re: [Design Doc] [RFC] Executor Authentication

, 2016 at 7:00 PM, Greg Mann <g...@mesosphere.io> wrote: > Hello all, > As part of the continuing effort to secure all communication in a Mesos > cluster, we would like to add authentication to the executor HTTP API. > Linked below is a design document draft for this feature; I w

[Design Doc] [RFC] Executor Authentication

Hello all, As part of the continuing effort to secure all communication in a Mesos cluster, we would like to add authentication to the executor HTTP API. Linked below is a design document draft for this feature; I would love to get the community's feedback! Feel free to leave comments on the

Re: [VOTE] Release Apache Mesos 1.0.4 (rc1)

+1 (non-binding) Ran `sudo make check` on CentOS 7 with Docker 1.12.1. The only test failure was: ProvisionerDockerPullerTest.ROOT_INTERNET_CURL_Whiteout While I haven't had a chance to look deeply into this, it seems that the whiteout handling was not correct at the time of 1.0, and these

Re: Welcome Gilbert Song as a new committer and PMC member!

Congratulations Gilbert!! :D On Wed, May 24, 2017 at 12:01 PM, Avinash Sridharan wrote: > Congrats Gilbert !! Very well deserved !! > > On Wed, May 24, 2017 at 11:56 AM, Timothy Chen wrote: > > > Congrats! Rocking the containerizer world! > > > > Tim >

Re: Mesos on Windows needs your help

Thanks Li Li, and others involved!! I'll definitely start keeping an eye on the Windows reviewbot, this is great to have. On Tue, May 30, 2017 at 10:58 AM, Li Li wrote: > With the joint effort from Mesosphere and Microsoft, the windows build > performance *should* be

Re: Easing the Pain of Code Formatting in Mesos

+1!!! On Thu, Jun 15, 2017 at 8:43 AM, Jie Yu wrote: > +1 > > Also, agreed with AlexR. Some of our style rules are very subjective. > Tooling and enforceable rules are much more important. > > - Jie > > On Thu, Jun 15, 2017 at 8:13 AM, Zhitao Li

Re: Welcome Greg Mann as a new committer and PMC member!

; > On Tue, Jun 13, 2017 at 2:42 PM Vinod Kone <vinodk...@apache.org> wrote: > > > Hi folks, > > > > Please welcome Greg Mann as the newest committer and PMC member of the > > Apache Mesos project. > > > > Greg has been an active contributor to the

[Design Doc] An Improved KillPolicy

Hello all! I've been working on a little design for some improvements to the KillPolicy. You can find the design doc here . TL;DR: the plan is to extend the KillPolicy message to allow the

This Month in Mesos - December 2017

Dear Apache Mesos Community, Development in Mesos has been active lately, with work taking place to enable things like hybrid cloud and network storage support, as well as improvements to the scheduler API designed to make the lives of framework developers easier. Apache Mesos version 1.5 is

Re: UPDATE: Mesos 1.6.0 release

Storage Interface version 0.2. > * [MESOS-8801] - Linux support for jemalloc. If any of that should be updated, please let me know! Thanks for your patience! Cheers, Greg On Tue, Apr 24, 2018 at 3:44 PM, Greg Mann <g...@mesosphere.io> wrote: > Hi all, > Several contributors who are

[VOTE] Release Apache Mesos 1.6.0 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.6.0. 1.6.0 includes the following: * Resizing of persistent volumes for agent default resources * Offer operation feedback for resource

[RESULT][VOTE] Release Apache Mesos 1.6.0 (rc1)

Hi all, The vote for Mesos 1.6.0 (rc1) has passed with the following votes. +1 (Binding) -- Vinod Kone Chun-Hung Hsiao James Peach Zhitao Li Andrew Schwartzmeyer There were no 0 or -1 votes. Please find the release at:

Soliciting documentation feedback

Hi everyone, As part of our ongoing effort to improve the Mesos docs, we're looking for your help. What areas of the Mesos documentation need the most improvement? Do you have projects to suggest or mistakes to flag? We'll be compiling this feedback into project suggestions for the May 24th

Re: Doc-a-thon - May 24th

Hi all, Just a reminder about the Mesos Doc-a-thon coming up next Thursday, May 24 starting at 3pm PST! You can join in person (RSVP here ) or online (link to join ). It would be great to see you

Re: Proposing change to the allocatable check in the allocator

Hi all, We had a nice discussion about this in the API working group meeting today. I agree that it's a good idea to do our best to make this change compatible with future updates to the Request call and/or quota. I think it would be beneficial to have a meeting in a few days to brainstorm some

Re: CHECK_NOTNULL(self->bev) Check failed inside LibeventSSLSocketImpl::shutdown

Su Teng, Thank you very much for this bug report! Much appreciated. Could you provide more information about the environment in which you noticed the bug originally - was it a running Mesos cluster? Did you use the provided snippet to reproduce the issue? Greg On Tue, Jun 26, 2018 at 11:25 PM,

[VOTE] Release Apache Mesos 1.6.1 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.6.1. 1.6.1 includes the following: *Announce major features here* *Announce major bug fixes here* The CHANGELOG for the

Re: [VOTE] Release Apache Mesos 1.6.1 (rc1)

tical bug that would wipe out persistent data. I'm backporting > this to 1.4, 1.5 and 1.6. > > On Fri, Jun 29, 2018 at 9:05 AM Greg Mann wrote: > > > The failures here are mostly command executor/default executor tests. > > Looking at the test output, it seems that the tasks i

[API WG] Meeting tomorrow!

Hi all, The API working group will meet tomorrow, May 1, from 11:00-11:50am PST. We'll be chatting about a proposal for per-framework metrics . Feel free to add more items to the agenda doc

Normalization of metric keys

Hi all! I'm currently working on adding a suite of new per-framework metrics to help schedulers better debug unexpected/unwanted behavior (MESOS-8842 ). One issue that has come up during this work is how we should handle strings like the framework

Re: [VOTE] Release Apache Mesos 1.6.1 (rc1)

Hey folks, an update on the 1.6.1-rc2 candidate: an issue surfaced after the fix was merged for MESOS-8830, which is being addressed currently. I'll be AFK for the next 3 days, so I'll cut 1.6.1-rc2 this coming Monday. Sorry for the delay! Cheers, Greg On Mon, Jul 2, 2018 at 12:30 PM, Greg Mann

This Month in Mesos - January 2018

Dear Apache Mesos Community, Happy new year! Here's your latest update on happenings in Mesosworld over the past month. *Working Groups* The working groups have been active; here's a brief summary of recent developments, along with links to the agenda documents. If you see anything that

Re: API working group

API working group will be great! I'd be interested in leading or co-leading this one. If anybody else has interest in leading as well, feel free to reach out. Greg On Wed, Jan 31, 2018 at 8:44 AM, Yan Xu wrote: > I’m in. Thanks! > > (mobile) > > > On Jan 30, 2018, at 10:42

Re: API working group

Sounds good to me. Thanks, Judith!! Greg On Wed, Feb 14, 2018 at 11:14 AM, Judith Malnick wrote: > I'm glad there's so much interest. > > Greg, can I put you down as the leader and Vinod can I put you down as the > co-leader? If that's ok, I'll follow up with a doodle

Re: API working group

18 at 10:30 AM, Judith Malnick <jmaln...@mesosphere.io > > > > wrote: > > > >> Hi everyone, > >> > >> Please vote for your favorite WG times in this doodle poll > >> <https://doodle.com/poll/hknkmtkazc45vrg4>. Greg and Vinod, please let > >

Re: Backport Policy

t;>>> are >>>> on the hook to triage and fix it and not the release manager. >>>> >>>> Having said that, if "during" the release process (i.e., cutting an RC) >>>> these backports cause delays for a release manager in getting the &g

This Month in Mesos: August 2018

Hi all, My apologies for the lack of emails during the last few months - I'm going to try to get back into the routine! Here's your August update on recent developments in the Mesos community, organized by working group: Containerization This has continued to be an area of active development,

API Working Group Tomorrow

Hi all, The next scheduled API working group meeting is tomorrow at 11am PST. There are currently no items on the agenda - please feel free to add them here ! If you're currently working on or planning any

Re: Follow up to discussion regarding use : in paths on Windows (MESOS-9109)

Thanks for addressing this Andy!! AFAIK we allow all characters in executor and task IDs; I'm surprised we haven't run into issues like this before on Linux. The percent-encoding approach seems fine to me. As long as the percent character isn't an issue on any filesystems that we're interested

Re: Follow up to discussion regarding use : in paths on Windows (MESOS-9109)

Thanks Andy! Responses inlined below. > No: As the only character we've run into a problem with is `:` > (MESOS-9109), it might not be worth it to generalize this to solve a bunch > of problems that we haven't encountered. > > It's true that I'm not aware of other scenarios where

[Community WG] Next meeting Monday 8/27, 10:30am PST

Hi all, The next Mesos community working group meeting will be held this coming Monday, 8/27 at 10:30am PST. If you have any items for the agenda, please add them here ! Thus far on the agenda, we

Re: API Working Group Tomorrow

in the next evolution of Mesos metrics! Cheers, Greg On Mon, Aug 20, 2018 at 11:40 AM, Greg Mann wrote: > Hi all, > The next scheduled API working group meeting is tomorrow at 11am PST. > There are currently no items on the agenda - please feel free to add them > here > <https

Re: [VOTE] Release Apache Mesos 1.7.0 (rc2)

+1 (binding) Tested in our internal CI; several test failures were observed but they are known flaky tests. Also ran our internal DC/OS integration tests against this build, and the results look good. Thanks for the reminder, Chun-Hung! Greg On Tue, Aug 28, 2018 at 9:14 AM, Chun-Hung Hsiao

Re: [VOTE] Move the project repos to gitbox

+1 On Tue, Jul 17, 2018 at 9:39 AM, Jie Yu wrote: > +1 > > On Tue, Jul 17, 2018 at 9:38 AM, Andrew Schwartzmeyer < > and...@schwartzmeyer.com> wrote: > >> +1 >> >> >> >> On 07/17/2018 8:54 am, Zhitao Li wrote: >> >> +1 >> >> On Tue, Jul 17, 2018 at 8:10 AM James Peach wrote: >> >>> >>> >>> >

Re: Backport Policy

My impression is that we have two opposing schools of thought here: 1. Backport as little as possible, to avoid unforeseen consequences 2. Backport as much as proves practical, to eliminate bugs in supported versions Do other people agree with this assessment? If so, how can we find

[API WG] Meeting tomorrow, 11am PST

Hi all, We have an API working group meeting scheduled tomorrow at 11am PST. There are currently no items on the agenda - if you have something to discuss in the meeting, please add it here !

  1   2   >