Re: Question on status update retry in agent

(1) Assuming you're referring to the scheduler's acknowledgement of a status update, the agent will not forward TS2 until TS1 has been acknowledged. So, TS2 will not be acknowledged before TS1 is acknowledged. FWICT, we'll ignore any violation of this ordering and log a warning. (2) To reverse

Re: [MoA] Update Jenkins ARM configuration

Thank you James! Jenkins build is back to normal : Mesos-Buildbot-ARM -- Forwarded message - From: Apache Jenkins Server Date: sob., 17.03.2018, 02:16 Subject: Jenkins build is back to normal : Mesos-Buildbot-ARM » autotools,gcc,--verbose

[GitHub] mesos pull request #274: Install ping. This is required by OsTest.Which

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/274 ---

Re: API Review: Resize (persistent) volume support

> 3) target volume in `Resource` format: this may not be possible for any CSI volume because the implementation could change certain metadata, so we did not take this approach. Can you expand on this? 3 looks like the best approach since it's idempotent and doesn't require that clients compute

Re: Release policy and 1.6 release schedule

Thanks Greg for starting this thread! > My primary motivation here is to bring our documented policy in line with > our practice, whatever that may be +100 Do people think that we should attempt to bring our release cadence more in > line with our current stated policy, or should the policy

Re: API Review: Resize (persistent) volume support

> > That said, I'm not sure if this is a valid concern since we don't have such > CSI functions yet. So input from folks would be very welcome! FYI, I just opened an issue in the CSI community: https://github.com/container-storage-interface/spec/issues/212 - Jie On Fri, Mar 16, 2018 at 11:40

Re: API Review: Resize (persistent) volume support

Thanks Zhitao for the summary. My thoughts are: For `SHRINK_VOLUME`, I feel option 2 is appropriate, as it gives the component that actually applies the operation to decide what the resulting free disk space would become. Option 3 is also acceptable. For `GROW_VOLUME`, I actually prefer option 1

Re: [MoA] Update Jenkins ARM configuration

Thanks, I hope this fix ARM builds pt., 16.03.2018, 18:35 użytkownik James Peach napisał: > > > > On Mar 16, 2018, at 8:27 AM, James Peach wrote: > > > > > > > >> On Mar 16, 2018, at 5:11 AM, Tomek Janiszewski > wrote: > >> > >> Hey >

API Review: Resize (persistent) volume support

Hi everyone, Chun, Greg, Gastón and I are working on supporting resizing of persistent volume[1]. See [2] for the design doc in length. The proposed new offer operation and corresponding operator API are in following two patches: https://reviews.apache.org/r/66049/

API Change: Abort SchedulerDriver when offer operation 'id' field is set

Hello everyone, Gastón and I are working on enabling offer operation feedback for frameworks [1]. The 'id' field in an offer operation is used by the framework to enable status updates for that operation. This field is new in 1.5.0, and currently the master simply drops all operations which have

Re: [MoA] Update Jenkins ARM configuration

> On Mar 16, 2018, at 8:27 AM, James Peach wrote: > > > >> On Mar 16, 2018, at 5:11 AM, Tomek Janiszewski wrote: >> >> Hey >> >> Who can edit Jenkins configuration? I noticed we run tests with the wrong >> configuration (we miss

Re: [MoA] Update Jenkins ARM configuration

> On Mar 16, 2018, at 5:11 AM, Tomek Janiszewski wrote: > > Hey > > Who can edit Jenkins configuration? I noticed we run tests with the wrong > configuration (we miss --disable-libtool-wrappers') it should > be CONFIGURATION='--disable-java --disable-python >

[MoA] Update Jenkins ARM configuration

Hey Who can edit Jenkins configuration? I noticed we run tests with the wrong configuration (we miss --disable-libtool-wrappers') it should be CONFIGURATION='--disable-java --disable-python --disable-libtool-wrappers' Can you fix it, please? https://issues.apache.org/jira/browse/MESOS-7500