Re: Subject: [VOTE] Release Apache Mesos 1.10.0 (rc1)

2020-05-27 Thread Greg Mann
+1 (binding) Observed only known flakes in internal CI. On Wed, May 27, 2020 at 9:56 AM Benjamin Mahler wrote: > +1 (binding) > > On Mon, May 18, 2020 at 4:36 PM Andrei Sekretenko > wrote: > >> Hi all, >> >> Please vote on releasing the following candidate as Apache Mesos 1.10.0. >> >> 1.10.0

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

2020-05-19 Thread Greg Mann
Hi all, The vote for Mesos 1.7.3 (rc1) has passed with the following votes. +1 (Binding) -- Vinod Kone Benjamin Mahler Greg Mann There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.7.3 It is recommended

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

2020-05-08 Thread Greg Mann
+1 (binding) Ran in internal CI, also built manually on CentOS 7. Only known flaky test failures observed. On Thu, May 7, 2020 at 3:02 PM Benjamin Mahler wrote: > +1 (binding) > > On Mon, May 4, 2020 at 1:48 PM Greg Mann wrote: > > > Hi all, > > > > Please v

[VOTE] Release Apache Mesos 1.7.3 (rc1)

2020-05-04 Thread Greg Mann
this package as Apache Mesos 1.7.3 [ ] -1 Do not release this package because ... Thanks, Greg Mann

Custom Docker executors

2020-04-22 Thread Greg Mann
Hi all, I'd like to propose that we remove the code in the Docker containerizer which allows schedulers to run custom executors in Docker containers. I suspect that this feature may not be used at all currently, and its presence in the containerizer leads to some added complexity. If you do run

RFC: Task Resource Limits Design

2019-11-22 Thread Greg Mann
Hi all, Myself and a few others have been working recently on a design to support task resource limits in Mesos. This feature allows schedulers to specify on their tasks an upper limit for CPU and memory which is greater than the requested CPU/mem resources. The task will be guaranteed access to

Re: Converting vm to task (performance degraded)

2019-08-29 Thread Greg Mann
Hi Marc, Could you clarify the hardware configuration of the host? How many cores does it have? Is this host the same one that you were running the VM on? How many cores were allocated to the VM? Regarding the 'top' output, if you're running 'top' with default settings I would expect to see the

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

2019-07-17 Thread Greg Mann
+1 'sudo make check' on CentOS On Tue, Jul 16, 2019 at 4:56 PM Meng Zhu wrote: > +1 > > tested on centos 7.4, only known flakies: > > [ PASSED ] 466 tests. > [ FAILED ] 7 tests, listed below: > [ FAILED ] CgroupsIsolatorTest.ROOT_CGROUPS_CFS_EnableCfs > [ FAILED ]

[API WG] Meeting today cancelled

2019-07-09 Thread Greg Mann
Hi all, We don't have anything on the agenda for today, so I'm going to cancel today's meeting. Please add any items you might have for discussion to the agenda here if you'd like to discuss them

Re: Design doc: Agent draining and deprecation of maintenance primitives

2019-06-14 Thread Greg Mann
lity issues of the current offer > model. > > > > And as somewhat of an aside, the lack of built-in scheduling has been > bad for the Mesos ecosystem. The vast majority of users just need to > schedule: services, jobs and cron jobs. These have a pretty standard look > and feel (incl

Re: Design doc: Agent draining and deprecation of maintenance primitives

2019-06-14 Thread Greg Mann
future, and allows us to incorporate automatic draining into the maintenance schedule later. Cheers, Greg On Fri, Jun 14, 2019 at 4:18 PM Greg Mann wrote: > Christoph, > Great to hear that you're using the maintenance primitives! It seems > unwise for us to deprecate this part of the

Re: Design doc: Agent draining and deprecation of maintenance primitives

2019-06-06 Thread Greg Mann
Maxime, Thanks for the feedback, it's much appreciated. I agree that it would be possible to evolve the existing primitives to accomplish something similar to the proposal. That is one option that was considered before writing the design doc, but after some discussion, I thought that it seems more

[API WG] Meeting today cancelled

2019-04-30 Thread Greg Mann
Hi all, There are no agenda items for the API working group meeting today, so I'm cancelling it. The next meeting is scheduled for May 14, please add agenda items if you have any planned or proposed API changes

Planned change: disallow frameworks changing principals

2019-04-01 Thread Greg Mann
Hi all, Due to MESOS-2842 , we are planning to update the Mesos master to disallow frameworks from changing their principal during reregistration. This will mean that over the lifetime of a framework with a given framework ID, the framework will

Moving the 'mesos-rxjava' repo

2019-03-21 Thread Greg Mann
Hi all, I wanted to announce a planned change to the mesos-rxjava project, which is currently hosted in Mesosphere's github organization. I'm planning to move this project into the unofficial Mesos github organization so that

Re: [API WG] Meeting tomorrow, call for agenda

2019-03-19 Thread Greg Mann
Looks like we have no agenda for the meeting today, so I'm cancelling it. Next API working group meeting will be held on April 2, see you then! On Mon, Mar 18, 2019 at 11:33 AM Greg Mann wrote: > Hi all! > We have an API working group meeting scheduled for tomorrow, but as

[API WG] Meeting tomorrow, call for agenda

2019-03-18 Thread Greg Mann
Hi all! We have an API working group meeting scheduled for tomorrow, but as of now there are no items on the agenda . If you have any planned or in-progress API changes that have not yet been

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

2019-03-07 Thread Greg Mann
+1 (binding) Ran through internal CI and observed only known flaky tests; almost all configurations passed with no failures. Cheers, Greg On Thu, Mar 7, 2019 at 1:55 AM Vinod Kone wrote: > +1 (binding) > > Ran in ASF CI. Saw some flaky tests but otherwise looks good. > > *Revision*:

[API WG] Meeting tomorrow

2019-03-04 Thread Greg Mann
Hi all, The next API working group meeting will be held tomorrow, March 5, at 11am PST. We'll be discussing the planned update of scheduler API operation reconciliation to a pattern more similar to task state reconciliation. *Note that this will be a breaking change for schedulers which are

Re: Discussion: Scheduler API for Operation Reconciliation

2019-02-28 Thread Greg Mann
Hey folks, Sorry to let this thread die out! I wanted to loop back and confirm our planned approach. We would like to change the v1 scheduler API so that the RECONCILE_OPERATIONS call no longer receives a synchronous HTTP response, but instead results in an asynchronous stream of operation status

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

2019-02-25 Thread Greg Mann
Hi all, The vote for Mesos 1.6.2 (rc1) has passed with the following votes. +1 (Binding) -- Vinod Kone Gastón Kleiman Meng Zhu Gilbert Song There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.6.2 It is

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

2019-02-21 Thread Greg Mann
+1 Built on CentOS 7.4 and ran all tests as root. Only 3 test failures were observed, all known flakes. Cheers, Greg On Wed, Feb 20, 2019 at 7:12 AM Vinod Kone wrote: > +1 > > Ran this on ASF CI. > > The red builds are a flaky infra issue and a known flaky test >

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

2019-02-20 Thread Greg Mann
lel-test-execution,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:16.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/console > >in > ASF CI. Doesn't seem to be a known issue according to JIRA. > > @Greg Mann can you please confirm if this is a flaky >

[VOTE] Release Apache Mesos 1.6.2 (rc1)

2019-02-19 Thread Greg Mann
Hi all, Please vote on releasing the following candidate as Apache Mesos 1.6.2. 1.6.2 includes a number of bug fixes since 1.6.1; the CHANGELOG for the release is available at: https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.6.2-rc1

[API Working Group] Meeting today cancelled

2019-02-19 Thread Greg Mann
Hi all, We don't have any agenda items for the API working group meeting today, so I'm cancelling it. The next meeting will be held on March 5 at 11am PST, feel free to add items to the agenda here !

[DISCUSSION] Making RESOURCE_PROVIDER capability required

2019-02-11 Thread Greg Mann
Hi all, I'm working on an issue related to operation feedback on agent default resources, MESOS-9535 . This involves the master's handling of an agent capability that we recently added, AGENT_OPERATION_FEEDBACK. This new capability is optional

Re: [DISCUSS] Updating the support and release policy

2019-01-28 Thread Greg Mann
I'm fine with keeping old branches around and stating in our docs/READMEs that the branches are unsupported. After looking at a few other open source projects, it seems that this practice is not uncommon. On Mon, Jan 14, 2019 at 11:42 AM Vinod Kone wrote: > Hi folks, > > As discussed in the

[API WG] Meeting today cancelled

2019-01-08 Thread Greg Mann
Hi all! We don't have an agenda for the API working group meeting today, so I'm cancelling it. Please add any proposed API changes or other items for discussion to the agenda here and we can discuss

[API WG] Meeting tomorrow

2018-12-10 Thread Greg Mann
Hi all, The API working group will meet tomorrow, Dec. 11 at 11am PST. On the agenda we have: - Proposed calls for the scheduler API: - UNSUPPRESS - CLEAR_FILTER - REQUEST_RESOURCE - Adding a new 'ResourceQuantity' type - Improving the scheduler operation

[API WG] Meeting today, 11am PST

2018-11-27 Thread Greg Mann
Hi all, The API working group is meeting this morning at 11am PST. We'll be discussing some potential changes to the agent's executor API to address agent/executor communication issues, as well as an update to the master's operator API to mitigate problems we've seen with Amazon's ELB. Feel free

Re: [API WG] Proposals for dealing with master subscriber leaks.

2018-11-21 Thread Greg Mann
Thanks for the proposal Joseph! I think I'm also leaning toward the circular buffer approach. The one real concern there seems to be the potential for "DDoS"-type scenarios when users hit the subscriber limit using clients which have retry logic. Providing a metric for the number of currently

[API WG] Meeting cancelled - Oct. 30

2018-10-29 Thread Greg Mann
Hi all, We currently have no agenda for the meeting tomorrow, and I'll be unable to attend. For these reasons, I'd like to cancel this one. Our next meeting is scheduled for Nov. 13 - see you then! Cheers, Greg

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

2018-10-24 Thread Greg Mann
Hmm I wonder if this is an issue on 1.5.1, or perhaps introduced by this commit? https://github.com/apache/mesos/commit/902aa34b79 On Wed, Oct 24, 2018 at 12:30 PM Vinod Kone wrote: > -1 > > Tested on ASF CI. Looks like Clang builds are failing with a build error. > See example build output > <

Proposal: Adding health check definitions to master state output

2018-10-18 Thread Greg Mann
Hi all, In addition to the health check API change proposal that I recently sent out, we're considering adding a task's health check definition (when present) to the 'Task' protobuf message so that it appears in the master's '/state' endpoint response, as well as the v1 GET_STATE response and the

Request for Comments - Health Check API Proposal

2018-10-17 Thread Greg Mann
Hi all, Some users have recently reported issues with our current implementation of health checks. See this ticket for an introduction to the issue. To summarize: we currently use a single 'optional bool healthy' field within the 'TaskStatus'

[API WG] Next meeting today, 11am PST

2018-10-16 Thread Greg Mann
Hi all, Please join us for the Mesos API working group meeting today at 11am PST. We'll be discussing proposed updates to the 'CREATE_DISK' API, as well as possible updates to the way Mesos exposes health checks to frameworks in task status updates. Feel free to add more items to the agenda here

This Month in Mesos: September 2018

2018-10-05 Thread Greg Mann
Hi all, It's time again for your monthly dose of news from Apache Mesosland! Here's a recap of the happenings from September: Mesos 1.7.0 Of course, the big news this past month is the new version! Apache Mesos 1.7.0 has been released; huge thanks to release managers Gastón Kleiman and Chun-Hung

[API WG] Meeting today cancelled

2018-10-02 Thread Greg Mann
Hi all, We don't have any agenda items for the API working group meeting today, so I'm going to cancel it. As a reminder, if you're designing or working on any user-facing API changes, please bring them to the working group for discussion! You can add items to the agenda for the next meeting here

[API WG] Meeting in 30 minutes!

2018-09-18 Thread Greg Mann
Hi all, We'll be holding the API working group meeting in 30 minutes, at 11am PST. You can find the agenda document, which includes a link for the Zoom meeting, here ; feel free to add inew agenda tems!

[API WG] Meeting today

2018-09-04 Thread Greg Mann
Hi all, We're having an API working group meeting this morning at 11am PST. I'll be facilitating a discussion about the future of metrics in Mesos. If you have any other topics for discussion, feel free to add them to the agenda:

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

2018-08-28 Thread Greg Mann
+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

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

2018-08-24 Thread Greg Mann
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: Follow up to discussion regarding use : in paths on Windows (MESOS-9109)

2018-08-23 Thread Greg Mann
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

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

2018-08-22 Thread Greg Mann
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: API Working Group Tomorrow

2018-08-21 Thread Greg Mann
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

API Working Group Tomorrow

2018-08-20 Thread Greg Mann
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

This Month in Mesos: August 2018

2018-08-15 Thread Greg Mann
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,

Re: Backport Policy

2018-07-26 Thread Greg Mann
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

[RESULT][VOTE] Release Apache Mesos 1.6.1 (rc2)

2018-07-25 Thread Greg Mann
Hi all, The vote for Mesos 1.6.1 (rc2) has passed with the following votes: +1 (Binding) -- Chun-Hung Hsiao Vinod Kone Gastón Kleiman There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.6.1 It is recommended

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

2018-07-25 Thread Greg Mann
aram() = true > > They are all known to be flaky. > > On Wed, Jul 11, 2018 at 6:15 PM Greg Mann wrote: > > > Hi all, > > > > Please vote on re

Re: [API WG] Meeting tomorrow, 11am PST

2018-07-24 Thread Greg Mann
Hey folks, It looks like we don't have an agenda for the meeting today, so let's cancel this one. The next API working group meeting will be on August 7; see you then! Cheers, Greg On Mon, Jul 23, 2018 at 11:04 AM, Greg Mann wrote: > Hi all, > We have an API working group meeting sch

[API WG] Meeting tomorrow, 11am PST

2018-07-23 Thread Greg Mann
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 !

Re: [VOTE] Move the project repos to gitbox

2018-07-17 Thread Greg Mann
+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

2018-07-16 Thread Greg Mann
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

Re: Backport Policy

2018-07-13 Thread Greg Mann
It seems to me that putting the burden of deciding on backports on the release manager would actually increase the amount of work required. Simply cutting the release on a particular date is pretty quick - however, examining tickets to determine whether or not a particular fix should be backported

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

2018-07-11 Thread Greg Mann
-9002] - GCC 8.1 build failure in os::Fork::Tree. * [MESOS-9024] - Mesos master segfaults with stack overflow under load. * [MESOS-9025] - The container which joins CNI network and has checkpoint enabled will be mistakenly destroyed by agent. Cheers, Greg On Wed, Jul 11, 2018 at 6:15 PM, Greg

[VOTE] Release Apache Mesos 1.6.1 (rc2)

2018-07-11 Thread Greg Mann
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: Normalization of metric keys

2018-07-09 Thread Greg Mann
e user actually supplied > '#%$' or '/'. But using something like percent-encoding would have property > 3. > > On Fri, Jul 6, 2018 at 10:25 AM, Greg Mann wrote: > >> Thanks for the reply Ben! >> >> Yea I suspect the lack of normalization there was not intentional, and i

Re: Normalization of metric keys

2018-07-06 Thread Greg Mann
Thanks for the reply Ben! Yea I suspect the lack of normalization there was not intentional, and it means that you can no longer reliably split on '/' unless you apply some external controls to user input. Yep, this is bad :) One thing we should consider when normalizing metadata embedded in

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

2018-07-03 Thread Greg Mann
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

Normalization of metric keys

2018-07-03 Thread Greg Mann
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)

2018-06-29 Thread Greg Mann
n 27, 2018 at 11:59 AM Jie Yu wrote: > >> +1 >> >> Passed on our internal CI that has the following matrix. I looked into >> the only failed test, looks to be a flaky test due to a race in the test. >> >> >> >> On Tue, Jun 26, 2018 at 7:02 PM, Gr

[VOTE] Release Apache Mesos 1.6.1 (rc1)

2018-06-26 Thread Greg Mann
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: Proposing change to the allocatable check in the allocator

2018-06-12 Thread Greg Mann
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: Doc-a-thon - May 24th

2018-05-17 Thread Greg Mann
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

Soliciting documentation feedback

2018-05-17 Thread Greg Mann
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: [VOTE] Release Apache Mesos 1.5.1 (rc1)

2018-05-15 Thread Greg Mann
+1 (binding) I did `sudo make check` and verified that only expected flaky tests failed. Cheers, Greg On Fri, May 11, 2018 at 12:35 PM, Gilbert Song wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.5.1. > > 1.5.1 includes the

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

2018-05-11 Thread Greg Mann
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:

Re: Getting roles' info in Scheduler

2018-05-10 Thread Greg Mann
Hi Pascal, This isn't possible directly with the SchedulerDriver, but your scheduler could use the 'GET_ROLES' call of the operator API [1] for this purpose. Cheers, Greg [1] http://mesos.apache.org/documentation/latest/operator-http-api/#get_roles On Sat, May 5, 2018 at 3:37 AM, Pascal Gillet

[VOTE] Release Apache Mesos 1.6.0 (rc1)

2018-05-07 Thread Greg Mann
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

UPDATE: Mesos 1.6.0 release

2018-05-04 Thread Greg Mann
. I have created the 1.6.x branch and *will cut Mesos 1.6 RC1 on Monday, May 7. *Keep your eyes peeled on the mailing list for the email, your help in testing is greatly appreciated! Thanks for your patience! Cheers, Greg On Tue, Apr 24, 2018 at 3:44 PM, Greg Mann <g...@mesosphere.io>

[API WG] Meeting tomorrow!

2018-04-30 Thread Greg Mann
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

UPDATE: Mesos 1.6.0 release

2018-04-24 Thread Greg Mann
Hi all, Several contributors who are either assignees or shepherds for 1.6 blocker tickets (myself included) have recently been pulled into some high priority internal work, so unfortunately I would like to delay the cut of the first release candidate for Mesos 1.6.0 to ensure that we have

Re: Doc-a-thon May 24th?

2018-04-13 Thread Greg Mann
Sounds good to me - thanks Judith!! On Wed, Apr 11, 2018 at 1:35 PM, Judith Malnick wrote: > Hi All, > > I'd like the next Mesos Doc-a-thon to happen on May 24th from 3-8pm > Pacific time. I picked the date because it's best for Ben H. > > Does anyone have major reasons

Proposal: Constrained upgrades from Mesos 1.6

2018-04-10 Thread Greg Mann
Hi all, We are currently working on patches to implement the new GROW_VOLUME and SHRINK_VOLUME operations [1]. In order to make it into Mesos 1.6, we're pursuing a workaround which affects the way these operations are accounted for in the Mesos master. These operations will be marked as

Re: Release policy and 1.6 release schedule

2018-04-10 Thread Greg Mann
Thanks for the reviews, y'all! I've got a few "Ship-Its" - I'll commit this later today unless I hear any objections. Cheers, Greg On Wed, Apr 4, 2018 at 11:49 AM, Greg Mann <g...@mesosphere.io> wrote: > Hey folks, > I've posted a proposed update to our documented rel

Re: Release policy and 1.6 release schedule

2018-04-04 Thread Greg Mann
Hey folks, I've posted a proposed update to our documented release schedule: https://reviews.apache.org/r/66454/ Please take a look and comment! Cheers, Greg On Mon, Mar 26, 2018 at 11:34 AM, Greg Mann <g...@mesosphere.io> wrote: > +1 for quarterly. I would also say that we should

Re: Mesos master endless attemps to kill unexisting task

2018-04-04 Thread Greg Mann
t; Yes I can confirm No kill ack received for instance >> [pub_api_oecd-rest-api-on-port-20015.marathon-196f414a-f61f-11e7-856c-f6e84742f1ef], >> retrying (73402 attempts so far)i cannot find this UUID in Mesos interface. >> >> Regards, Adam. >> >> On 03/15/2018 0

[API WG] Meeting today

2018-04-03 Thread Greg Mann
Hi all, The API working group will be meeting today at 11am PST. We'll be discussing HTTP return codes in Mesos [1]. If you have any other items for discussion, add them to the agenda! [2] Cheers, Greg [1] https://issues.apache.org/jira/browse/MESOS-7697 [2]

This Month in Mesos - March 2018

2018-03-30 Thread Greg Mann
Oh hai there Apache Mesos Community! Back again with your monthly update on current events in the Mesosverse: *Working Groups* Below you'll find a brief summary of the group meetings from this past month, as well as some info about related work that's been happening in the project. Working

Re: Release policy and 1.6 release schedule

2018-03-26 Thread Greg Mann
h of an ask for committers and > maintainers. > > > > I also agree with folks that there're benefits doing releases more > > frequently. Given the historical data, I'd suggest we do quarterly > > releases, and maintain three release branches. > > > > - Jie

Re: Release policy and 1.6 release schedule

2018-03-26 Thread Greg Mann
> > I think the burden of maintaining a release branch is not just > backporting. We need to run CI to make sure every maintained release branch > are working, and do testing for that. It's a burden if there are too many > release branches. > > That's a good point, we do need to run CI on all

Re: Release policy and 1.6 release schedule

2018-03-23 Thread Greg Mann
we declared on policy. That makes upstream projects easier to >> gauge when a feature will be ready and when they can try it out. >> >> On Tue, Mar 13, 2018 at 3:10 PM, Greg Mann <g...@mesosphere.io> wrote: >> >> > Hi folks, >> > During the recent API worki

Re: Mesos master endless attemps to kill unexisting task

2018-03-15 Thread Greg Mann
Hi Adam, The KILL calls are being sent to Mesos by Marathon. Since the KILL call is being forwarded to the agent, it seems that the Mesos master is aware of the task. Could you verify that the tasks show up as running in the Mesos UI? You say that the tasks don't exist anymore - how did you verify

Release policy and 1.6 release schedule

2018-03-13 Thread Greg Mann
Hi folks, During the recent API working group meeting [1], we discussed the release schedule. This has been a recurring topic of discussion in the developer sync meetings, and while our official policy still specifies time-based releases at a bi-monthly cadence, in practice we tend to gate our

API Working Group - First Meeting Tomorrow

2018-03-05 Thread Greg Mann
Hello all, We'll be having our first API working group meeting tomorrow, March 6 at 11am PST. This working group is a great opportunity for us to work toward greater consistency and usability of our API, as well as raise issues with the current interface and plan future directions. You can find

This Month in Mesos - February 2018

2018-02-28 Thread Greg Mann
Dear Apache Mesos Community, Hello all! I've got a short update for you this month with recent happenings in Mesosland: *Working Groups* Here's the latest from the working groups. Working group meetings can be found on the Mesos community calendar

This Month in Mesos - January 2018

2018-01-30 Thread Greg Mann
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

This Month in Mesos - December 2017

2017-12-12 Thread Greg Mann
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

[Design Doc] An Improved KillPolicy

2017-09-25 Thread Greg Mann
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

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

2017-06-15 Thread Greg Mann
; > 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

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

2017-05-24 Thread Greg Mann
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: [VOTE] Release Apache Mesos 1.0.4 (rc1)

2017-04-25 Thread Greg Mann
+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 Kevin Klues as a Mesos Committer and PMC member!

2017-03-01 Thread Greg Mann
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)

2017-03-01 Thread Greg Mann
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: Welcome Neil Conway as Mesos Committer and PMC member!

2017-01-23 Thread Greg Mann
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: Question on dynamic reservations

2017-01-17 Thread Greg Mann
ces) > with attributes on them you could have frameworks voluntarily choose not to > consume resources not meant for them. > > e.g. Disk resource has attribute `CASSANDRA`. Ok, since I'm a Kafka > framework I won't go use that disk. > > On Tue, Jan 17, 2017 at 11:24 AM Greg Mann

Re: Question on dynamic reservations

2017-01-17 Thread Greg Mann
Hi Povilas, Another approach you could try is to use dynamic reservations only. You could either: 1. Alter your stateful framework to dynamically reserve the resources that it needs, or 2. Add a script to your cluster tooling that would make use of the operator endpoint for dynamic

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

2017-01-06 Thread Greg Mann
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

2017-01-04 Thread Greg Mann
, 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

  1   2   >