Re: [VOTE] Release Apache Aurora 0.13.0 RC0

+1 verification passes for me On Tue, Apr 12, 2016 at 1:34 PM, Joshua Cohen wrote: > Ahh, thanks for being on top of that John! > > On Tue, Apr 12, 2016 at 3:05 PM, John Sirois > wrote: > > > On Tue, Apr 12, 2016 at 1:48 PM, Joshua Cohen wrote: > > > > > +1, ran the verification script, every

Build failed in Jenkins: aurora-packaging-nightly #262

See -- [...truncated 9407 lines...] + rm -rf /dist/rpmbuild/BUILDROOT/aurora-scheduler-0.13.1snapshot.2016.04.13-1.el7.centos.aurora.x86_64 ++ dirname /dist/rpmbuild/BUILDROOT/aurora-scheduler-0

Re: [VOTE] Release Apache Aurora 0.13.0 RC0

Ahh, thanks for being on top of that John! On Tue, Apr 12, 2016 at 3:05 PM, John Sirois wrote: > On Tue, Apr 12, 2016 at 1:48 PM, Joshua Cohen wrote: > > > +1, ran the verification script, everything looks good to me. > > > > Nitpick: the NEWS link in the email 404s because we renamed it to > >

Re: [VOTE] Release Apache Aurora 0.13.0 RC0

On Tue, Apr 12, 2016 at 1:48 PM, Joshua Cohen wrote: > +1, ran the verification script, everything looks good to me. > > Nitpick: the NEWS link in the email 404s because we renamed it to > RELEASE-NOTES.md. We should probably update the script that generates the > email? > See my response above

Re: [VOTE] Release Apache Aurora 0.13.0 RC0

+1, ran the verification script, everything looks good to me. Nitpick: the NEWS link in the email 404s because we renamed it to RELEASE-NOTES.md. We should probably update the script that generates the email? On Tue, Apr 12, 2016 at 10:02 AM, Erb, Stephan wrote: > +1 for releasing 0.13.0-rc0 as

Re: Looking for feedback - Setting CommandInfo.user by default when launching tasks.

Stephan and Joshua, I am working on design of an external component which will consume DiscoveryInfo from Mesos and announce it to Zookeeper. (You see why I added DiscoveryInfo to Mesos now :) ) The reason I like to delegate this component to a third party component (calling it a Mesos-ZK-Bridge)

Re: [VOTE] Release Apache Aurora 0.13.0 RC0

+1 for releasing 0.13.0-rc0 as Aurora 0.13.0 * tested with the verification script * deployed the RC to an inhouse test cluster I am also OK with fixing the changelog afterwards. From: Bill Farner Sent: Tuesday, April 12, 2016 16:18 To: jfarr...@apache.o

Re: Looking for feedback - Setting CommandInfo.user by default when launching tasks.

As things stand today, once a task is scheduled, the scheduler can die, or be shut down for maintenance, etc. with no impact to running tasks. If the scheduler were responsible for announcing and it maintained the current practice of creating znodes as ephemeral, it would need to maintain a persist

Re: [VOTE] Release Apache Aurora 0.13.0 RC0

I'm okay with not blocking the release on it. On Tuesday, April 12, 2016, Jake Farrell wrote: > My fault, I thought we had changed this awhile back to automatically pull > in any tickets not having a set fix version that had been marked as > resolved and that this had become a post step to clean

Re: [VOTE] Release Apache Aurora 0.13.0 RC0

My fault, I thought we had changed this awhile back to automatically pull in any tickets not having a set fix version that had been marked as resolved and that this had become a post step to clean up jira after the release when marking the version as released. This should not be a blocker for the

Re: Looking for feedback - Setting CommandInfo.user by default when launching tasks.

I have recently run into another issue due to Thermos running as root (https://issues.apache.org/jira/browse/MESOS-5187). I would therefore like to re-open the discussion. IIRC there was a JIRA ticket proposing that the scheduler should be responsible for announcing services in Zookeeper. Woul