Re: Moving forward on AURORA-1503

It seems that this is not a correct usage of semver and that we should release the link to 0.23.0 as 0.10.0. Given the mesos deprecation cycle described in that ticket, 0.22.0 would be compatible with 0.21.0. IMO a patch release should never break compatibility with versions that the previous patch

Re: TransientStorageException: Storage is not READY

Hi Mauricio, Sorry for the delay in reply. This can sometimes happen during startup or shutdown. It's a race between the leading scheuler (de)registering itself in ZooKeeper (and the client or UI noticing) and starting up (tearing down) its storage. It's usually transient, but definitely a wart.

Re: Testing our UI code

+1 On Thu, Sep 10, 2015 at 1:30 PM, Joseph Smith wrote: > Agreed, this seems awesome. > > Thanks Josh! > > > > On Sep 10, 2015, at 1:09 PM, David McLaughlin > wrote: > > > > +1 to this, seems like an ideal solution to getting testing into the UI > > asap. > > > > On Thu, Sep 10, 2015 at 10:30 A

Re: [DRAFT] [REPORT] Apache Aurora

+1 On Tue, Sep 8, 2015 at 5:04 PM, Bill Farner wrote: > Please take a moment to read through a draft of the board report i have > prepared for Aurora. I'm happy to take any suggestions for edits prior to > submitting this tomorrow. > > > ## Description: > - Apache Aurora lets you use an Apache

Re: Creating Aurora user@ and announcements@ lists?

+1 On Tue, Sep 8, 2015 at 11:07 AM, Zameer Manji wrote: > +1 > > On Tue, Sep 8, 2015 at 10:35 AM, Mauricio Garavaglia < > mauriciogaravag...@gmail.com> wrote: > > > +1 > > > > On Tue, Sep 8, 2015 at 2:29 PM, Hussein Elgridly < > > huss...@broadinstitute.org > > > wrote: > > > > > +1. As a user,

Community meeting next week

Next Monday 7 Sep 2014 is a US holiday and most of the Aurora committers will be out celebrating with their friends and families. As such, I propose we cancel this instance of the community meeting.

Re: [VOTE] Release Apache Aurora 0.9.0 debs

+1 to these debs On Sat, Aug 29, 2015 at 9:59 AM, Bill Farner wrote: > I propose that we accept the following artifacts as the official deb > packaging for > Apache Aurora 0.9.0. > > > http://people.apache.org/~wfarner/aurora/distributions/0.9.0/deb/ubuntu-trusty/ > > The Aurora deb packaging in

Re: [VOTE] Release Apache Aurora 0.9.0 rpms

On Wed, Sep 2, 2015 at 3:33 PM, Kevin Sweeney wrote: > Overall -1 > > -1 Package naming: we use two different naming schemes for RPMs vs. DEBs. > - in debs the clients are aurora-tools, the executor is aurora-executor, > and the scheduler is aurora-scheduler. In the RPM version t

Re: [VOTE] Release Apache Aurora 0.9.0 rpms

Overall -1 -1 Package naming: we use two different naming schemes for RPMs vs. DEBs. - in debs the clients are aurora-tools, the executor is aurora-executor, and the scheduler is aurora-scheduler. In the RPM version the scheduler is aurora, the clients are aurora-client, and the executor is aurora

Re: [VOTE] Release Apache Aurora 0.9.0 debs

g this all up!! > > > >> On Aug 27, 2015, at 5:32 PM, Roger Ignazio wrote: > >> > >> +1 (non-binding). Looking forward to the RPMs too! > >> > >> On Thu, Aug 27, 2015 at 12:47 PM, Maxim Khutornenko > >> wrote: > >> > >&g

Re: Nightly packages

Nice work Bill! On Thu, Aug 27, 2015 at 11:20 AM, Bill Farner wrote: > Hi folks, > > I wanted to report in that i have just completed work [1] to add a jenkins > job [2] to produce nightly builds of our packages (currently centos 7 and > ubuntu 14.04). There is still some follow-up effort neces

Re: [VOTE] Release Apache Aurora 0.9.0 debs

>From my ASF email this time: +1 (binding) On Wed, Aug 26, 2015 at 11:31 AM, Kevin Sweeney wrote: > +1 > > The one issue I have - thermos.pex seems to only appear in > /usr/share/aurora/bin/thermos.pex and not as a globally-linked > /usr/bin/thermos command. This makes it pre

Re: [VOTE] Release Apache Aurora 0.9.0 debs

/dist/release/aurora/KEYS > > > > Please download, verify, and test. > > > > The vote will close in 3 business days, on Mon Aug 31 10:00:00 PT 2015 > > > > [ ] +1 Release these as the deb packages for Apache Aurora 0.9.0 > > [ ] +0 > > [ ] -1 Do not release these artifacts because... > > > > I would like to get the voting started off with my own +1 > > > > > > -=Bill > > > -- Kevin Sweeney @kts

Re: Mechanics of Twitter Commons Import

+1 On Mon, Aug 24, 2015 at 5:14 PM, Zameer Manji wrote: > Hey, > > I would like to inform everyone that there is a review > out that imports the java code we > depend on from Twitter Commons into our tree. The current approach of the > import is a large patc

Re: [DISCUSS] Remove dependency on ZooKeeper for leader election?

Unfortunately, speaking to jieyu this is not possible with the current Log implementation (a follower attempting a write will actually succeed and invalidate the leader's lock, causing the former leader to fall over). So a more fruitful approach may be to embed ZooKeeper in Aurora and optionally us

[DISCUSS] Remove dependency on ZooKeeper for leader election?

While perusing the replicated log code for an upcoming talk I realized we could drop the use of ZooKeeper for leader election in favor of directly using the Mesos replicated log. The reason for this is that we are required to be the leader to write anything to the log. So the ZK-based leader electi

Re: Summary of IRC Meeting in #aurora

Thanks for sending this out Josh! On Monday, August 17, 2015, Joshua Cohen wrote: > No one with karma was around to kick off an official meeting, so we had an > ad-hoc meeting. Here's the transcript: > > 11:01 jcohen: ASFBot: meeting start > 11:01 ASFBot: You don't have enough karma for this req

Improvements to container support with custom executor

ve it launch a child container). -- Kevin Sweeney @kts

Re: SSL Support

The client works fine if the scheduler API is behind an HTTPS reverse proxy. The scheduler doesn't currently support listening on HTTPS by itself but this would be a fairly trivial patch (a fix for https://issues.apache.org/jira/browse/AURORA-343). On Wed, Aug 12, 2015 at 12:40 PM, Erb, Stephan w

Re: [PROPOSAL] Changes to the Python BUILD layout

Posted https://reviews.apache.org/r/36972/ for feedback. On Thu, Jul 30, 2015 at 5:17 PM, Bill Farner wrote: > +1 > > -=Bill > > On Thu, Jul 30, 2015 at 4:24 PM, Kevin Sweeney > > wrote: > > > Somewhat complementary work - this change would make the generated &g

Re: [PROPOSAL] Changes to the Python BUILD layout

this effort against a tool change? > > -=Bill > > On Thu, Jul 30, 2015 at 4:00 PM, Kevin Sweeney wrote: > > > I propose a simplification of the Python BUILD layout as follows and a > set > > of new conventions, as follows: > > > > 1) 1 BUILD per 3rd level dire

[PROPOSAL] Changes to the Python BUILD layout

I propose a simplification of the Python BUILD layout as follows and a set of new conventions, as follows: 1) 1 BUILD per 3rd level directory. These are currently ``` % find src/main/python -maxdepth 3 -mindepth 3 -type d |while read dirname; do echo $dirname | sed 's@src/main/python/\(.*\)/\(.*\

Re: [PROPOSAL] Source releases vs artifact releases

+1 On Mon, Jul 27, 2015 at 3:40 PM, Bill Farner wrote: > Hi folks, > > An issue that we have not yet officially addressed is release management as > it pertains to binary artifacts we produce of Aurora. Today, when we cut a > release, say 0.9.0, we essentially take a snapshot of (most of) our >

Re: [VOTE] Release Apache Aurora 0.9.0 RC0

+1 RC verification script passes On Tue, Jul 21, 2015 at 2:18 PM, Bill Farner wrote: > +1 > > Successfully ran ./build-support/release/verify-release-candidate 0.9.0-rc0 > > -=Bill > > On Mon, Jul 20, 2015 at 10:59 AM, Jake Farrell > wrote: > > > I propose that we accept the following release

Re: http auth and aurora tutorial

I just reproduced this as well - the issue appears to be that the scheduler is registering in ZooKeeper with an IP address of 127.0.1.1, but the netrc file is configured for 192.168.33.7. vagrant@aurora:~$ PEX_INTERPRETER=1 aurora Python 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2] on linux2

Re: Forking twitter-commons into our tree

+1, I suspect we'll find several things that can be replaced by the Java 8 standard library or newer versions of Guava and Guice. On Mon, Jul 6, 2015 at 11:20 AM, Zameer Manji wrote: > Just to be clear, I'm proposing forking the java parts only. > > On Mon, Jul 6, 2015 at 9:06 AM, Joseph Smith

Re: [jira] [Created] (AURORA-1375) When setting quota, the scheduler should prevent setting below current usage

Reporter: Joe Smith > > > Initially I thought this check should live in the admin client, but after > discussing with [~zmanji], we believe the scheduler would be the right > place to enforce this. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > -- Kevin Sweeney @kts

Re: Should we maintain the thermos abstraction?

I think the abstraction has outlived its value, proven by the fact that there are parts of thermos that are completely untested and broken (see gc subcommand) that maintaining them isn't worth the overhead. I think my comment here sums up my feelings on this issue and points out some of the shortc

Re: Culling items from 0.9.0 release

+1 On Tuesday, June 23, 2015, Bill Farner wrote: > Hey folks, > > I've moved the following tickets from the 0.9.0 release to the 0.10.0 > release so that we may release in a more timely manner: > > AURORA-334 Replace in-memory storage with H2 > This change is important, but ~entirely behind the

Re: [VOTE] Release Apache Aurora 0.8.0 API Artifacts

+1 On Thu, Jun 11, 2015 at 1:35 PM, Jake Farrell wrote: > Nexus upload automatically does that > > -Jake > > On Thu, Jun 11, 2015 at 4:33 PM, Kevin Sweeney wrote: > >> It looks like there are checksums of the signatures, is that intentional? >> >> On Thu, J

Re: [VOTE] Release Apache Aurora 0.8.0 API Artifacts

It looks like there are checksums of the signatures, is that intentional? On Thu, Jun 11, 2015 at 1:31 PM, Jake Farrell wrote: > All, > I have packaged up and staged the API jar/source artifacts from Apache > Aurora 0.8.0 > and deployed them to the Apache staging repo [1]. I propose that we acce

Re: [DRAFT] Apache Aurora board report June 2015

+1 Thanks for taking care of this, Jake! On Tue, Jun 9, 2015 at 8:28 AM, Jake Farrell wrote: > Please review the following draft board report, if no comments or changes > are noted in the next day or so I will submit this report > > -Jake > > > > June 2015 > > Apache Aurora is a service schedul

Re: [VOTE] Release Apache Aurora 0.8.0 RC1

. > > Thanks, Jake! > > -=Bill > > On Thu, May 7, 2015 at 9:23 PM, Justin Mclean > wrote: > > > Hi, > > > > Sorry ignore that I got my lists mixed up and thought the VOTE was sent > to > > general@incubator. > > > > Thanks, > > Justin > -- Kevin Sweeney @kts

Re: [DRAFT][REPORT] Apache Aurora

vity > > - 27 JIRA tickets created in the last month [3] > - 47 JIRA tickets closed/resolved in the last month [4] > > > [1] http://meetup.com/Bay-Area-Apache-Aurora-Users-Group > [2] http://s.apache.org/ytb > [3] http://s.apache.org/gmt > [4] http://s.apache.org/KIm > > > -=Bill > -- Kevin Sweeney @kts

Re: [VOTE] Release Apache Aurora 0.8.0 RC0

che.org/repos/dist/dev/aurora/0.8.0-rc0/apache-aurora-0.8.0-rc0.tar.gz.asc > > > > The GPG key used to sign the release are available at: > > https://dist.apache.org/repos/dist/dev/aurora/KEYS > > > > Please download, verify, and test. > > > > The vote will close on Thu May 7 22:35:17 EDT 2015 > > > > [ ] +1 Release this as Apache Aurora 0.8.0 > > [ ] +0 > > [ ] -1 Do not release this as Apache Aurora 0.8.0 because... > > > > I would like to get the voting started with my own +1 > > > > -Jake > > > -- Kevin Sweeney @kts

Re: [VOTE] Release Apache Aurora 0.8.0 RC0

overall +0 - I'm okay with proceeding with the changelog as the only deficiency +1 java tests pass +1 python test pass +1 e2e tests pass +0 changelog is incorrect as wfarner notes On Tue, May 5, 2015 at 3:36 PM, Bill Farner wrote: > -1 overall > > +1 checksums and signatures are good > +1 unit

Re: End to end tests broken?

This is possibly related to https://issues.apache.org/jira/browse/AURORA-1304 On Mon, May 4, 2015 at 2:44 PM, Benjamin Mahler wrote: > Thanks, looks good now. > > On Sat, May 2, 2015 at 4:31 PM, Bill Farner wrote: > > > Try destroying the VM (vagrant destroy -f) and running again. The > upstar

Fwd: Private docker registry authentication

In case you didn't see this thread -- Forwarded message -- From: *Christopher Snell* Date: Wednesday, April 29, 2015 Subject: Private docker registry authentication To: u...@mesos.apache.org Alright, I'm using Aurora so I will have to dig deeper to see if I can figure out how to

Re: docker parameters

The executor completely scrubs the environment [1], so you'd have to prevent it from doing that. I'd suggest adding a flag to the executor to take a list of other environment variables to whitelist. https://github.com/apache/aurora/blob/aad9a5a182b9fbf82ad6048bae0373014f4f10b4/src/main/python/apac

Re: How dead is a job after aurora job kill?

ar case I'm > worrying about is a job continuing to run and surprising us by writing > files when we thought it was dead. > > Thanks, > Hussein Elgridly > Senior Software Engineer, DSDE > The Broad Institute of MIT and Harvard > -- Kevin Sweeney @kts

Re: [jira] [Created] (AURORA-1258) Improve procedure for adding instances to a job

How about a scale command somewhere that will check that the only operation it's doing is "scaling" and not introducing new code. This could be accomplished by diffing the config for the new instances with that of the old instances. For cases where it's not a pure scale operation, maybe have an ove

Re: [DRAFT][REPORT] Apache Aurora -

+1 On Monday, April 6, 2015, Bill Farner wrote: > *Please find a draft of our board report below. Happy to discuss any > modifications anyone would like to see! I'll be submitting this tomorrow, > including any accepted edits.* > > > > ## Description: > > Aurora is a service scheduler used to

Re: Deprecating "restart_theshold" setting

+1 On Fri, Apr 3, 2015 at 3:02 PM, Steve Niemitz wrote: > +100. This is particularly annoying with docker tasks, as the task doesn't > enter running until the pull completes. > > Does this also include making the timer for "initial_interval_secs" start > when the task enters RUNNING? > > On Fri