Re: Reducing Failover Time by Eagerly Reading/Replaying Log in Followers

Some (hopefully) constructive criticism: - the doc is very high-level on the problem statement and the proposal, making it difficult to agree with prioritization over cheaper snapshots or the oft-discussed support of an external DBMS. - the supporting data is a single data point of the scheduler_

Re: ResourceBag Ordering violates general contract

Neat bug! The implementation gets into trouble when different resource types are in play, giving inconsistent results depending on which argument is 'left'. e.g. host A: cpu=2, disk=1 host B: cpu=2, ram=1 In this example, compare(A, B) considers A > B, and compare(B, A) considers B > A. The fi

Re: ResourceBag Ordering violates general contract

I've implemented the above suggestion here: https://reviews.apache.org/r/61238/ On Fri, Jul 28, 2017 at 7:19 PM, Bill Farner wrote: > Neat bug! > > The implementation gets into trouble when different resource types are in > play, giving inconsistent results depending on which

Notice - removing rewriteConfigs API call

FYI - i have a patch out for review that will remove the rewriteConfigs thrift API call, with no deprecation period (see the review for rationale). Currently there is movement to land the patch. If you use or care about this API call, please chime in ASAP!

Re: Future of storage in Aurora

rformance, I'd verify there is a benefit before > > submitting > > any review. > > > > Thanks all for the feedback. > > > > > > On Thu, Mar 30, 2017 at 12:08 PM, Bill Farner > m> > > wrote: > > > > > Adding some background -

Re: Future of storage in Aurora

That’s right, nothing fancy. On Oct 2, 2017, 4:24 AM -0700, Erb, Stephan , wrote: > What do you have in mind for the in-memory replacement? Revert back to the > usage of thrift objects within plain Java containers like we do for the task > store? > > On 02.10.17, 00:59, "

Re: Future of storage in Aurora

i.e. the job update store). Will converting it have an impact on, e.g., > storage write-lock contention? > > On Sun, Oct 1, 2017 at 5:59 PM, Bill Farner wrote: > > > I would like to revive this discussion in light of some work i have been > > doing around the storage system.

Re: gorealis is now officially a PayPal Open Source Project

Congrats on releasing! On Oct 16, 2017, 4:15 PM -0500, Renan DelValle , wrote: > Hi all, > > Just wanted to drop a note about a recent update for gorealis[1]. For those > who aren't familiar with it, gorealis is a library that aims to enable > users to programmatically interact with the Aurora sc

Re: Build failed in Jenkins: Aurora #1858

Possibly rehashing an old discussion - does the build really require 4 GB? On Mon, Oct 23, 2017 at 1:53 PM, Erb, Stephan wrote: > Ah, again a node with insufficient memory. I once added a mechanism to > abort the build early rather than running and eventually failing in these > cases. This was v

[VOTE] Release Apache Aurora 0.18.1 RC1

All, I propose that we accept the following release candidate as the official Apache Aurora 0.18.1 release. Aurora 0.18.1-rc1 includes the following: --- The RELEASE NOTES for the release are available at: https://git-wip-us.apache.org/repos/asf?p=aurora.git&f=RELEASE-NOTES.md&hb=rel/0.18.1-rc1

Re: [VOTE] Release Apache Aurora 0.18.1 RC1

+1 Verified by running ./build-support/release/verify-release-candidate 0.18.1-rc1 On Sun, Oct 29, 2017 at 12:05 PM, David McLaughlin wrote: > +1 > > On Sun, Oct 29, 2017 at 10:32 AM, Bill Farner wrote: > > > All, > > > > I propose that we accept the foll

0.19.0 release preparation

Folks, I propose we cut our 0.19.0 release soon. We have built up a respectable set of unreleased changes . I am happy to perform this release, and should be able to do so as soon as this week. Please chime in here if there is any o

Re: [VOTE] Release Apache Aurora 0.18.1 RC1

> 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- > 0 > curl: (22) The requested URL returned error: 404 Not Found > > > On Sun, Oct 29, 2017 at 5:03 PM, Bill Farner wrote: > > > +1 > > > > Verified by running ./build-support/release/verify-release-candidate

Re: Build failed in Jenkins: Aurora #1858

ded the remaining 2 > as an additional safeguard when something else is launched on the > Jenkins node shortly after we have passed the guard. > > On Tue, 2017-10-24 at 21:38 -0700, Bill Farner wrote: > > Possibly rehashing an old discussion - does the build really require > >

Re: [VOTE] Release Apache Aurora 0.18.1 RC1

ng opinions. > > +0 > > On Mon, Oct 30, 2017 at 12:06 PM, Stephan Erb wrote: > > > +1 > > > > Thanks for handling this, Bill. > > > > On Mon, 2017-10-30 at 10:05 -0500, Joshua Cohen wrote: > > > +1 > > > > > > On Sun, Oct 29, 20

[RESULT][VOTE] Release Apache Aurora 0.18.1 RC1

All, The vote to accept Apache Aurora 0.18.1 RC1 as the official Apache Aurora 0.18.1 release has passed. +1 (Binding) -- Bill Farner David McLaughlin Joshua Cohen Stephan Erb +0 (Non-binding) -- Mohit Jaggi There were no -1 votes. Thank

Re: 0.19.0 release preparation

os 1.4. Unfortunately this is currently > > blocked by a missing mesos.interface package on PyPI. I send a mail out > to > > the Mesos Dev list but I am still waiting for a response. So this will > have > > to wait for 0.20. > > > > On 29.10.17, 23:15, "Bill Far

Re: 0.19.0 release preparation

x27;ll get to this week, one is minor and > one is relatively serious (no longer showing pending reasons on the task > list). If people are comfortable moving forward without those fixes, then > go for it. > > On Tue, Nov 7, 2017 at 9:55 AM, Bill Farner wrote: > > > David - n

[VOTE] Release Apache Aurora 0.19.0 RC0

All, I propose that we accept the following release candidate as the official Apache Aurora 0.19.0 release. Aurora 0.19.0-rc0 includes the following: --- The RELEASE NOTES for the release are available at: https://git-wip-us.apache.org/repos/asf?p=aurora.git&f=RELEASE-NOTES.md&hb=rel/0.19.0-rc0

Re: [VOTE] Release Apache Aurora 0.19.0 RC0

than a supported environment. Others are welcome to feel differently. On Tue, Nov 7, 2017 at 8:49 PM, Bill Farner wrote: > All, > > I propose that we accept the following release candidate as the official > Apache Aurora 0.19.0 release. > > Aurora 0.19.0-rc0 includes the follow

Re: [VOTE] Release Apache Aurora 0.19.0 RC0

-candidate 0.19.0-rc0 On Wed, Nov 8, 2017 at 10:48 AM, David McLaughlin wrote: > +1 from me. The Mac OS breakage is disappointing, but I'm fine with it not > being a blocker. > > On Tue, Nov 7, 2017 at 11:04 PM, Mohit Jaggi wrote: > > > +1 > > > > On Tue, Nov 7

[RESULT][VOTE] Release Apache Aurora 0.19.0 RC0

All, The vote to accept Apache Aurora 0.19.0 RC0 as the official Apache Aurora 0.19.0 release has passed. +1 (Binding) -- Bill Farner David McLaughlin Stephan Erb +1 (Non-binding) -- Mohit Jaggi There were no 0 or -1 votes. Thank you to

[VOTE] Release Apache Aurora 0.19.x packages

All, I propose that we accept the following artifacts as the official deb and rpm packaging for Apache Aurora 0.19.x: https://dl.bintray.com/bill/aurora/ The Aurora deb and rpm packaging includes the following: --- The branch used to create the packaging is: https://git1-us-west.apache.org/rep

Re: [VOTE] Release Apache Aurora 0.19.x packages

all URIs for container '48b4029a-231d- > 441a-98a6-8c6538fe0efa' with exit status: 256 > > > Did those tests work for you? > > > In addition, but most probably unrelated, the branch is missing on http > s://github.com/apache/aurora-packaging. The ASF bot might have mi

Re: [VOTE] Release Apache Aurora 0.19.x packages

Friendly reminder that the vote is due to close tomorrow! Stephan - is the issue you described reproducible? Did i run the same test command(s) as you? On Sun, Dec 10, 2017 at 8:32 PM, Bill Farner wrote: > +1 from me, as the test script passes for all artifacts > > I did not have ti

Thrift 0.10.0

After much battling with tools, tests, and jenkins; John upgraded us to thrift 0.10.0 by landing r/64290 ! The next time you pull, you will likely notice that you have some stale untracked files. You can safely clean these up: $ rm -r build-support/thrift/t

Re: [VOTE] Release Apache Aurora 0.19.x packages

just need someone to test and > verify, > > I can do that. Let me know. > > > > On Tue, Dec 12, 2017 at 9:53 AM, Bill Farner wrote: > > > > > Friendly reminder that the vote is due to close tomorrow! > > > > > > Stephan - is the issue you de

[RESULT] [VOTE] Release Apache Aurora 0.19.x packages

tu-trusty/dist > > Oddly enough, we have deployed 0.19.0 packages for trusty without any issue > on at least two of our test clusters so it may have to do with our > artifacts tests? > > I tried upgrading the trusty box to Mesos 1.2.2 and the problem persisted. > > -Renan

Re: [REPORT] Apache Aurora - December 2017

+1 Thanks, Jake! On Mon, Dec 18, 2017 at 6:34 AM, Jake Farrell wrote: > Please find below the draft report for December, if anyone has any > modifications or additions please let me know > > -Jake > > > > Apache Aurora is a stateless and fault tolerant service scheduler used to > schedule jobs

Re: executor id from task id?

Did your code search lead you here ? It should show how the executor and task IDs relate. On Tue, Jan 2, 2018 at 1:08 PM, Mohit Jaggi wrote:

Re: executor id from task id?

#x27;t want to add it to storage if it is not there to avoid > handling db migration. > > On Tue, Jan 2, 2018 at 8:05 PM, Bill Farner wrote: > > > Did your code search lead you here > > <https://github.com/apache/aurora/blob/2e1ca42887bc8ea1e8c6cddebe9d1c > > f

Re: replicated log improvement

I think it aligns well with work that plausibly follows r/64288/ , so i'd say it's a likely outcome regardless of the direction taken for storage. On Wed, Jan 3, 2018 at 11:44 PM, meghdoot bhattacharya < meghdoo...@yahoo.com.invalid> wrote: > mesos 7973 delive

Re: [RESULT] [VOTE] Release Apache Aurora 0.19.x packages

few folks on the Slack channel have been asking when the > binaries for 0.19 will be released. > > -Renan > > On Wed, Dec 13, 2017 at 5:23 PM, Bill Farner wrote: > > > I reverse my vote to -1 and am closing the vote as failed. > > > > Turns out i had some old debs i

Welcome new committers and PMC member!

Folks, I'm happy to announce that we have two new developers on the project! Renan DelValle is now a committer and PMC member Jordan Ly is now a committer Welcome aboard, we're looking forward to your continued contributions! -=Bill

Re: [VOTE] Release Apache Aurora 0.19.1 RC0

+1, binding I did encounter a unit test failure, but maintain my +1 as this test case has been notorious flaky on macOS 10.13.3 (especially for me, apparently). All other checks in the verification script pass. def _run_collector_tests(collector, target, wait): assert collector.va

Re: Scheduling improvements followups

> > How much work (and feasibility?) would be to add other filter conditions In my opinion, relatively little work. An extension point exists as a thin interface [1], injectable via a module [2]. OfferOrder [3] may look like a promising alternative, but i see that as a less flexible option. Reg

Re: [VOTE] Discontinue Official Binary Package releases

+1 > On May 18, 2018, at 6:44 PM, Renan DelValle wrote: > > +1 > > On Fri, May 18, 2018 at 6:35 PM, Mauricio Garavaglia < > mauriciogaravag...@gmail.com> wrote: > >> +1 >> >>> On Fri, May 18, 2018 at 8:01 PM, Renan DelValle wrote: >>> >>> All, >>> >>> As has been brought up before, we lack

Re: Recovery instructions updates

> > How does the site get updated? Is it auto-generated when we build releases? The source lives in the project SVN repo: $ svn co https://svn.apache.org/repos/asf/aurora/ aurora-svn Here are instructions for updating it. It's a pretty m

Re: snapshot analyze

You might be thinking of something we had at Twitter geared towards capacity planning. It intended to tell us how many more instances of a given resource shape would hypothetically “fit” in the cluster. > On Jun 6, 2018, at 1:20 AM, meghdoot bhattacharya > wrote: > > Long time back, I remembe

Re: [DISCUSS] Move project to GitBox service

+1 for taking PRs, but I’m not opinionated about how that is achieved. > On Jun 11, 2018, at 5:27 PM, Renan DelValle wrote: > > All, > > I wanted to bring up for discussion moving the project from our current > ReviewBoard based workflow to a GitHub pull request based workflow through > the use

Re: Transient task state timeout

This is expected behavior, as STARTING is not a transient state . I don't believe it ever was. The rationale is that the ASSIGNED -> STARTING transition acknowledges the

Re: Volunteers needed

I’m happy to pitch in for periodic review. Anyone is welcome to email me requesting a review. I don’t monitor incoming reviews, so unfortunately I will need to be contacted out-of-band. On Tue, Sep 18, 2018 at 10:45 AM Renan DelValle wrote: > All, > > We are in dire need of folks who would be

Re: Combining limit and dedicated constraint

I’m pretty sure I’ve seen this combination working in the (distant) past, for limit:1 and other values. As a sanity check, if you remove the host that _is_ having the task scheduled, does the task move to the other host? On Mon, Feb 4, 2019 at 5:10 PM Renan DelValle wrote: > I have two dedicate

Re: [VOTE] Move Aurora to Apache Attic

+1 Aurora has always been about pragmatism, and right now, this is the best route for new and existing users. On Fri, Jan 31, 2020 at 5:13 PM Renan DelValle wrote: > +1 (with a fair bit of sadness but hope for the future of the project) > > 2020-01-31 17:11 GMT-08:00 Renan DelValle: > > Folks,

Re: [jira] [Created] (AURORA-1212) Allow non-dedicated jobs to have static ports

My apologies for the delay, I have been out of town this week and otherwise occupied by quarter boundary work. I would like to better understand your use case and the technical barriers before we proceed. I will email you to arrange that discussion. In the meantime, you might consider running a c

Heads up - git repo URL has changed!

With graduating, we get to shed the 'incubator-' prefix from our git repository URL. Our new URL is: https://git-wip-us.apache.org/repos/asf/aurora/ You can re-clone from that URL. If you have an old clone, you will notice remote operations failing with an error like: $ git pull fatal: repositor

Aurora JIRA permissions

We've historically had trouble with people not being able to assign tickets to themselves, which was caused by permissions restrictions. I've updated the project permissions so that any JIRA user may be assigned one of our tickets. I feel that this is a more open approach to managing work, but pl

Re: Graduation checklist

Thanks, Jake! -=Bill On Wed, Apr 1, 2015 at 9:27 PM, Henry Saputra wrote: > Great news! Thanks for the update Jake. > > On Wed, Apr 1, 2015 at 5:09 PM, Jake Farrell wrote: > > All steps on the graduation checklist from the incubator are now > completed > > > > -Jake >

Re: Deprecating "restart_theshold" setting

The bright side is that you (the cluster administrator) can buffer for this in only the global task timeout setting, and it doesn't have to leak into everyone's update configurations. -=Bill On Fri, Apr 3, 2015 at 1:06 PM, Steve Niemitz wrote: > oh hm, I thought it started as soon as the task w

Re: Deprecating "restart_theshold" setting

I've prepared a minimal patch to remove this behavior from the scheduler: https://reviews.apache.org/r/32840/ -=Bill On Fri, Apr 3, 2015 at 3:50 PM, Bill Farner wrote: > The bright side is that you (the cluster administrator) can buffer for > this in only the global task timeout s

[DRAFT][REPORT] Apache Aurora -

*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 schedule jobs onto Apache Mesos. ## Activity: - Graduated from

Re: [DRAFT][REPORT] Apache Aurora -

Sweeney wrote: > > > > > +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

Re: Nuked sandbox directory and failing to run finalizers on disk exceeded

I'm fairly ignorant to some of the practicalities here - if you don't write to /mnt/mesos/sandbox, where do files land? Some other ephemeral directory that dies with the container? -=Bill On Thu, Apr 9, 2015 at 7:11 AM, Hussein Elgridly wrote: > Thanks, that's helpful. I've also just discovere

Re: Plotting state transitions

I may be going on a tangent from what's in your mind, but i think a means to visualize this stuff would be really useful. I can see value in a few different distinct, but complementary things: 1. state flow of instances in a job. This would cover transitions between states like PENDING and RUNNI

Re: Nuked sandbox directory and failing to run finalizers on disk exceeded

> anger it. > > Hussein Elgridly > Senior Software Engineer, DSDE > The Broad Institute of MIT and Harvard > > > On 9 April 2015 at 12:25, Bill Farner wrote: > > > I'm fairly ignorant to some of the practicalities here - if you don't > write > > to /mnt/

Re: Unofficial SF meetup 4/21 or 22?

+1! I can do either day, but to get the ball rolling on proposed details: Tuesday 4/21 at 5 PM Beer Hall: http://www.yelp.com/biz/the-beer-hall-san-francisco Beer hall can get crowded, so we can fall back to other options if necessary. We've also hosted at Twitter in the past, so we can utilize

Re: Removing locks for Crons

To clarify - i assume you mean you would like to have the client stop securing a lock when dealing with cron jobs? -=Bill On Mon, Apr 20, 2015 at 11:42 AM, Zameer Manji wrote: > Folks, > > As I mentioned on our IRC meeting today, I want to remove locks for cron > jobs. All cron operations are a

Re: Unofficial SF meetup 4/21 or 22?

e if you are still looking in that area. It's pretty > > divey > > > > but earlier in the evening tends to not be super crowded. > > > > > > > > Cheers, > > > > Josh > > > > > > > > On Mon, Apr 13, 2015 at 1:37 PM, Steve Ni

Re: End to end tests broken?

Try destroying the VM (vagrant destroy -f) and running again. The upstart scripts are not currently synced with the repo, so they can drift. I suspect my recent scheduler arg removal is biting you. On Friday, May 1, 2015, Benjamin Mahler wrote: > I seem to have issues running the end to end te

Re: recommended setting for max leading duration

The defaults are reasonable. I would not advise increasing max_leading_duration dramatically, as the recovery time grows linearly with the number of log writes due to MESOS-184 [1]. [1] https://issues.apache.org/jira/browse/MESOS-184 -=Bill On Tue, May 5, 2015 at 12:29 PM, Bhuvan Arumugam wro

Re: [VOTE] Release Apache Aurora 0.8.0 RC0

-1 overall +1 checksums and signatures are good +1 unit tests and end-to-end tests pass -1 changelog contains tickets that were closed as won't fix. i came up with a JIRA query [1] that seems to identify a bunch of these [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20AURORA%20AND

Re: Aurora + Docker containerizer

> > We need to pass any docker run param e.g. environment variables, volumes. > ATM we are limited by Aurora, because Mesos (correct me if I’m wrong) > provides many more options to frameworks The only technical blocker here is lack of plumbing out to our configuration language. I doubt there wi

Re: Build failed in Jenkins: Aurora #1023

Looks transient. I'll kick another build and deal with it if it recurs. -=Bill On Wed, May 6, 2015 at 12:38 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [wfarner] Updgrade to gradle 2.4. > >

[DRAFT][REPORT] Apache Aurora

*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 agreed edits.* ## Description: Aurora is a service scheduler used to schedule jobs onto Apache Mesos. ## Activity: - Vote for 0.8.0 rel

Re: [DRAFT][REPORT] Apache Aurora

> > On Thu, May 7, 2015 at 4:41 PM, 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 agreed edits.* > > > > &

Re: [VOTE] Release Apache Aurora 0.8.0 RC1

+1 Passed ./build-support/release/verify-release-candidate 0.8.0-rc1 from master, which covers signature checks, unit tests, and integration tests. 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 VOT

Re: GSOC 2015

Sorry for the delay in getting back to you - welcome aboard!! I wouldn't suggest you start with AURORA-243, as it's pretty deep in the bowels, and unclear if/how we are going to address it. I'm excited to see what you produce in AURORA-1164! Don't hesitate to ask questions here and/or in IRC!

Human-readable release notes

Now that we have started doing more regular releases, one area in need of improvement is communicating in plain language what is in a release. Our current change log [1] leaves much to be desired, as it makes it difficult for even project developers to know what happened in a release. Below i hav

Re: Human-readable release notes

RM branches off master, adds the extra prose at the top and > then tags the commit that adds the additional prose as the rc. > > On Mon, May 11, 2015 at 3:07 PM, Bill Farner wrote: > > > Now that we have started doing more regular releases, one area in need of > > improve

Heads up: Requiring java 8

Hello everyone, As previously agreed [1], we are transitioning to use Java 8 language features, thus requiring a 1.8 JVM. This aligns with oracle's end of public updates for Java 7 [2]. For those of you using builds off master, please note that this will begin as early as this week! [1] https:/

Re: Heads up: Requiring java 8

Yep, I was thinking the same thing! On Tuesday, May 12, 2015, Jake Farrell wrote: > This is a good first item to add to the NEWS file (if we are going to use a > separate file for things like this) > > -Jake > > On Tue, May 12, 2015 at 11:21 AM, Bill Farner > wrote:

Fwd: ASF Board Report - Initial Reminder for June 2015

Is anyone else willing/able to pick up the board report for this month? I am out of the country, returning the day it is due. -- Forwarded message -- From: *Marvin* Date: Sunday, June 7, 2015 Subject: ASF Board Report - Initial Reminder for June 2015 To: Bill Farner Subject

Re: ASF Board Report - Initial Reminder for June 2015

Thanks! On Monday, June 8, 2015, Jake Farrell wrote: > I'll take care of it > > -Jake > > On Sun, Jun 7, 2015 at 2:38 PM, Bill Farner > > wrote: > > > Is anyone else willing/able to pick up the board report for this month? > I > > am out

Re: Lost jobs on cluster failure

Maxim's reply is correct, elaborating Should it assume the Mesos list is complete, and assume the missing nodes > are indeed gone, and hence restart the jobs? Yes. This scenario is currently reconciled by the GC executor, which runs on an hourly interval by default. This behavior is soon to be

Re: arbitrary parameters for docker containers

Hey Mauricio! Thanks for the contribution! Please accept our apologies for the delay, there are two reasons this review slipped through the cracks: 1.) our review bot replied indicating that the patch breaks the build. Due to the review volume we deal with, reviewers tend to skim past reviews w

Re: cmdline and docker entrypoints

Did you ever figure this out? The entrypoint will indeed be replaced, and the command supplied in the Aurora configuration will be used. I can see how this might be unexpected, especially when using an off-the-shelf docker container. -=Bill On Sat, May 16, 2015 at 8:32 PM, Mauricio Garavaglia <

Re: [VOTE] Release Apache Aurora 0.8.0 API Artifacts

+1 -=Bill On Thu, Jun 18, 2015 at 12:23 PM, Zameer Manji wrote: > +1 > > On Thu, Jun 18, 2015 at 12:22 PM, Kevin Sweeney > wrote: > > > +1 > > > > On Thu, Jun 11, 2015 at 1:35 PM, Jake Farrell > wrote: > > > > > Nexus upload automatically does that > > > > > > -Jake > > > > > > On Thu, Jun 11

Culling items from 0.9.0 release

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 scenes for now and should not hold up a release. AURORA-987 Cre

Should we maintain the thermos abstraction?

Since there's been a recent uptick in development on the executor, there's a long overdue discussion that i would like to raise. Does it make sense to continue maintaining the abstraction between 'thermos' and the 'default Aurora executor'? I see this as cognitive overhead in the code, and it add

Re: Should we maintain the thermos abstraction?

bstraction barriers as they > > exist today > > > https://issues.apache.org/jira/browse/AURORA-1338?focusedCommentId=14561777&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14561777 > > > > On Wed, Jun 24, 2015 at 3:13 PM, Bill Fa

Re: Should we maintain the thermos abstraction?

onorepo. Right now it's neither > documented nor clear that it can operate in isolation from Aurora. > > On Wed, Jun 24, 2015 at 3:50 PM, Bill Farner wrote: > > > I may not be thinking hard enough about it - but wouldn't consuming it > as a > > third-party dependen

Re: Ubiquitous jobs (AURORA-1075)

Thanks for the doc! I've left some comments, but this looks good overall! -=Bill On Wed, Jun 24, 2015 at 8:11 PM, Anindya Sinha wrote: > Hi > > Reference: https://issues.apache.org/jira/browse/AURORA-1075 > > This JIRA is about a feature to schedule jobs such that there is an > instance of suc

No community meeting today

The majority of committers are tied up during the community meeting today, so i propose we cancel today's meeting and hold out for next week. -=Bill

Re: Using Prometheus with Aurora

Great work, Brian! This is awesome! -=Bill On Wed, Jul 1, 2015 at 7:54 AM, Brian Brazil wrote: > Hi, > > I've added support to Prometheus to use Twitter serversets for service > discovery, and we're now got this deployed in production. A key point is > that you can configure it to look at a tr

Re: Using a config file to support custom executors: potential paradigm shift

ything has > been done through command line up until now), a discussion is > necessary about this possible shift in paradigm due to the fact that, > if this route is taken, it will set a precedent for Aurora. > > As Bill Farner said in his comment on Jira, all in all, this is > discussion should be about how should approach this potential paradigm > shift. > > -Renan >

Re: Forking twitter-commons into our tree

I believe this came up in a previous conversation, with the same conclusion you have drawn.  Ticket: https://issues.apache.org/jira/browse/AURORA-1213 _ From: Zameer Manji Sent: Thursday, July 2, 2015 12:20 PM Subject: Forking twitter-commons into our tree To:

Re: Forking twitter-commons into our tree

Jake - i'm not fully versed on licenses, but is that true even though it's all Apache License 2.0? -=Bill On Thu, Jul 2, 2015 at 5:28 PM, Jake Farrell wrote: > no objections, but we would have to get an IP clearance doc from Twitter > for this code in order to bring this code into the ASF > > -

Re: Forking twitter-commons into our tree

onated to the > ASF > > -Jake > > [1]: http://incubator.apache.org/ip-clearance/index.html > > > > On Thu, Jul 2, 2015 at 10:41 PM, Bill Farner wrote: > > > Jake - i'm not fully versed on licenses, but is that true even though > it's > > all Apa

Re: Forking twitter-commons into our tree

libraries. On Thu, Jul 2, 2015 at 10:34 PM, Bill Farner wrote: > Thanks, Jake! > > -=Bill > > On Thu, Jul 2, 2015 at 8:10 PM, Jake Farrell wrote: > > > yes, makes it easier to donate when its Apache License 2.0, but still > > requires the IP clearance [1], wh

Re: http auth and aurora tutorial

I got as far as creating a job following the tutorial [1] and didn't encounter any issues. The client is configured for basic auth, just in a non-obvious way with a .netrc file [2]. This is certainly confusing when the clusters.json plainly suggests that there is no auth happening [3]. This is t

Re: Using a config file to support custom executors: potential paradigm shift

; +1 to #1 for the short term, but I'd like us to assess #3 in the long > term. > > > > On Thursday, July 2, 2015, Zameer Manji wrote: > > > >> I am in favor of #1 to prevent yak shaving. > >> > >> On Thu, Jul 2, 2015 at 12:10 PM, Bill Farner &

Re: Aurora React UI Demo/Prototype

I'm pretty ignorant of this space, please bear with me. You'll notice that the app is written in ES6 and not ES5 (i.e. the > javascript you're likely familiar with). As of React 0.13.x, ES6 with a > transpiler (i.e. a tool to compile the ES6 syntax into vanilla ES5 syntax) > is the preferred metho

Re: Blue Yonder is using Aurora

Thanks for the writeup, Stephan! -=Bill On Sat, Jul 18, 2015 at 11:48 PM, Erb, Stephan wrote: > Hi everyone, > > we are happy to announce that Blue Yonder (http://www.blue-yonder.com/en/) > is using Apache Aurora. > > We have published a short explanation of our current usecase [1] and are > l

Re: Aurora React UI Demo/Prototype

pat-table/es6/. As you > > can > > > see from the table Firefox and Chrome have already implemented > > significant > > > parts of the spec. Predictably IE and Safari are lagging behind, but I > > > think we're past the point where we need to be concerned ab

Re: [VOTE] Release Apache Aurora 0.9.0 RC0

+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 candidate as the official > Apache Aurora 0.9.0 release. > > > Aurora 0.9.0-rc0 includes the following: >

Re: Aurora-1288 custom executor support in client

One of the biggest challenges i foresee if we embark on making the client support custom executors is schema handling. By design, pystachio defines schemas that configurations must match, which will likely make it difficult to generalize to support swappable/arbitrary executors. I am not familiar

Re: http auth and aurora tutorial

rora/scheduler', client) > >>> [ServiceInstance.to_dict(host) for host in hosts] > [{'status': 'ALIVE', 'additionalEndpoints': {u'http': {'host': > u'*127.0.1.1*', > 'port': 8081}}, 'serviceEndpoint':

Re: Build failed in Jenkins: Aurora #1127

Looks like a flaky test leading to a timeout: test_updater.py::UpdaterTest::test_update_instances_wait_for_batch_completion_filled_batch > Build timed out > This code is on the chopping block, so i suggest we live with the flakiness for now. -=Bill On Fri, Jul 24, 2015 at 1:30 PM, Apache Jenki

[PROPOSAL] Source releases vs artifact releases

ion be to cut a new rc or would having the deb/rpm > packaging code in separate repo on its own release be more in line. i.e., > package 0.1.0-2.rpm in packaging land > > Daniel Gruno (Humbedooh) 12:07 PM > you could cut a new release and bypass the 72h rule > > Bill Farner 12:

Re: [PROPOSAL] Source releases vs artifact releases

ker files so we can automate the > build of the given release deb/rpm's and script the process for creating > tags for each 0.9.0-1.rpm or 0.9.0-2.deb ... > > -Jake > > On Mon, Jul 27, 2015 at 6:40 PM, Bill Farner wrote: > > > Hi folks, > > > > An issue

  1   2   3   4   >