Re: [VOTE] Release Apache Aurora 0.18.0 RC0

> Please download, verify, and test. > > > > The vote will close on Mon Jun 12 17:12:10 PDT 2017 > > > > [ ] +1 Release this as Apache Aurora 0.18.0 > > [ ] +0 > > [ ] -1 Do not release this as Apache Aurora 0.18.0 because... > > > > Thanks, > > -Santhosh > > > > -- > Zameer Manji >

Re: schedule task instances spreading them based on a host attribute.

s are CPU bound (and > sometimes network) and the rest of our jobs are mostly memory bound. We’ve > found that if too many consumers wind up on the same EC2 instance they > don’t perform as well. It’s hard to prove this, but the gut feeling is > pretty strong. > > > > On Mar 3

Re: schedule task instances spreading them based on a host attribute.

fewer instances than expected. On > a> > >>>>> smaller scale, the former approach would also apply if you want to > >>>> spread> > >>>>> tasks in racks or availability zones. I'd like to have one instance > of a> > >>>>> job per rack (failure domain) but in the case of it going down, the> > >>>>> instance can be spawn on a different rack.> > >>>>> > >>>>> I thought we could have a scheduling constraint to "spread" > instances> > >>>>> across a particular host attribute; instead of vetoing an offer right > >>>> away> > >>>>> we check where the other instances of a task are running, looking > for a> > >>>>> particular attribute of the host. We try to maximize the different > >>>> values> > >>>>> of a particular attribute (rack, hostname, etc) on the task > instances> > >>>>> assignment.> > >>>>> > >>>>> what do you think? did something like this came up in the past? is > it> > >>>>> feasible?> > >>>>> > >>>>> > >>>>> Mauricio> > >>>>> > >>>> > >> > > -- > Zameer Manji >

Re: Future of storage in Aurora

ions for the missing ones (UpdateStore)? I'd even go further and > propose that we consider in-memory H2 and MyBatis a failed experiment and > we drop that storage layer completely. > > Cheers, > David > > -- > Zameer Manji >

Re: schedule task instances spreading them based on a host attribute.

e :) > > > > > > > > > On Mon, Mar 6, 2017 at 2:57 PM, Zameer Manji <zma...@apache.org> wrote: > > > Something similar was proposed on a Dynamic Reservations review and there > > is a ticket for it here <https://issues.apache.org/ > jira/browse/

Re: Design Doc for Mesos Maintenance in Aurora

<stephan@blue-yonder.com> wrote: > Looks good to me! > > On 08/03/2017, 02:45, "Zameer Manji" <zma...@apache.org> wrote: > > Hey, > > I have a brief design doc > <https://docs.google.com/document/d/1Z7dFAm6I1nrBE9S5WHw0D0LAp

Re: Dynamic Reservations

a user further control over the > > > reservations so that they can manage those independent of the task/job > > > lifecycle? For example, how does Borg handle this? > > > > > > b) The implementation proposal and patches include an > > > OfferReconciler, so this implies we don’t want to offer any control for > > the > > > user. The only control mechanism will be the cluster-wide offer wait > time > > > limiting the number of seconds unused reserved resources can linger > > before > > > they are un-reserved. > > > > > > c) Will we allow adhoc/cron jobs to reserve resources? Does it > even > > > matter if we don’t give control to users and just rely on the > > > OfferReconciler? > > > > > > > > > I have a couple of questions on the MVP and some implementation > details. > > I > > > will follow up with those in a separate mail. > > > > > > Thanks and best regards, > > > Stephan > > > > > > > -- > Zameer Manji >

Re: schedule task instances spreading them based on a host attribute.

ead of vetoing an offer right away > we check where the other instances of a task are running, looking for a > particular attribute of the host. We try to maximize the different values > of a particular attribute (rack, hostname, etc) on the task instances > assignment. > > what do you think? did something like this came up in the past? is it > feasible? > > > Mauricio > > -- > Zameer Manji >

Re: Idea: rolling restarts in Aurora

dditional storage changes are required. > > If this proposal seems reasonable, I’ll file a ticket and draft up a more > detailed RFC for further review. > > Cody > > -- > Zameer Manji >

Re: Design Doc: Mesos V1 API

t; > On Wed, Feb 1, 2017 at 2:23 PM, Zameer Manji <zma...@apache.org> wrote: > > > Hey, > > > > I have written a design doc > > <https://docs.google.com/document/d/1bWK8ldaQSsRXvdKwTh8tyR_ > > 0qMxAlnMW70eOKoU3myo/edit#> > > that > > ou

Design Doc: Mesos V1 API

Hey, I have written a design doc <https://docs.google.com/document/d/1bWK8ldaQSsRXvdKwTh8tyR_0qMxAlnMW70eOKoU3myo/edit#> that outlines the work required to adopt the Mesos HTTP V1 API in Aurora. Please take a look and comment. -- Zameer Manji

Re: [VOTE] Release Apache Aurora 0.17.0 RC0

ra- > > 0.17.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 Sa 4. Feb 09:35:45 CET 2017 > > > > [ ] +1 Release this as Apache Aurora 0.17.0 > > [ ] +0 > > [ ] -1 Do not release this as Apache Aurora 0.17.0 because... > > -- > Zameer Manji >

Re: Adding support for Mesos' Kill Policy when running docker executor-less tasks.

itional > > > planning? > > > > > > > > I am happy to hear what you think. > > > > > > > > > > > > On 29/12/2016, 16:48, "Nicolas Donatucci" <ndonatu...@medallia.com> > > > wrote: > > > > > > > > Hello everybody. > > > > > > > > I was thinking on adding support for the current Mesos' Grace > > Period > > > > Kill > > > > Policy when running Docker containers without Thermos. It is > > > currently > > > > the > > > > only Kill Policy implemented by Mesos. (More information can be > > found > > > > here > > > > https://github.com/apache/mesos/blob/master/CHANGELOG#L576-L585 > > and > > > > JIRA > > > > issue here https://issues.apache.org/jira/browse/MESOS-4909) > > > > > > > > My idea is to add a Kill Policy to TaskConfig in order to pass it > > on > > > to > > > > Mesos. The "finalization_wait" field of the task schema can be > used > > > to > > > > create the corresponding Kill Policy. > > > > > > > > What do you think? > > > > > > > > > > > > > > > > > > > -- > Zameer Manji >

Re: A sketch for supporting mesos maintenance

for scheduling. > > On Wed, Nov 9, 2016 at 3:09 PM Zameer Manji <zma...@apache.org> wrote: > > > Hey, > > > > This is not a design doc for supporting Mesos Maintenance, but more of a > > high level overview on how we *could* support it going forward. I just &

A sketch for supporting mesos maintenance

eduler can coordinate with the Mesos Master in an SLA aware fashion. What do folks think? -- Zameer Manji

Re: Build failed in Jenkins: Aurora #1665

Fixing the regression in https://reviews.apache.org/r/53508/ On Fri, Nov 4, 2016 at 4:14 PM, Zameer Manji <zma...@apache.org> wrote: > Looking > > On Fri, Nov 4, 2016 at 4:02 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > >> See <https

Re: Build failed in Jenkins: Aurora #1665

log_ > config.py::TestRotateOverStdout::test_log_config [31mFAILED [0m > > src/test/python/apache/thermos/core/test_runner_log_config.py > <- .pants.d/python-setup/chroots/aa8c19ee98132b1d807c9921997c09 > adcdd43a98/apache/thermos/testing/runner.py::TestRotateOverStderr::test_runner_state_reconstruction > [32mPASSED [0m > src/test/python/apache/thermos/core/test_runner_log_ > config.py::TestRotateOverStderr::test_log_config [31mFAILED [0m > > src/test/python/apache/thermos/core/test_runner_log_config.py > <- .pants.d/python-setup/chroots/aa8c19ee98132b1d807c9921997c09 > adcdd43a98/apache/thermos/testing/runner.py::TestRotateDefaulted::test_runner_state_reconstruction > [32mPASSED [0m > src/test/python/apache/thermos/core/test_runner_log_ > config.py::TestRotateDefaulted::test_log_config [31mFAILED [0m > src/test/python/apache/thermos/core/test_staged_kill. > py::TestRunnerKill::test_process_kill Build timed out (after 120 > minutes). Marking the build as failed. > Build was aborted > Recording test results > ERROR: Step ?Publish JUnit test result report? failed: No test report > files were found. Configuration error? > > -- > Zameer Manji >

Re: Aurora, Thermos, PID 1, and You

Filed a task https://issues.apache.org/jira/browse/AURORA-1808 to track this work since there are no objections. On Mon, Oct 31, 2016 at 6:42 PM, Zameer Manji <zma...@apache.org> wrote: > Re sending this from my @apache.org email in case my previous email got > caught in spam. > &

Re: Aurora, Thermos, PID 1, and You

Re sending this from my @apache.org email in case my previous email got caught in spam. On Mon, Oct 31, 2016 at 6:42 PM, Zameer Manji <zma...@uber.com> wrote: > Hey, > > Recently I have experienced a number of issues in a production environment > with the DockerContainerizer,

Aurora, Thermos, PID 1, and You

f3de5b34af/src/main/java/org/apache/aurora/scheduler/configuration/executor/ ExecutorModule.java#L109-L135 [2]: http://man7.org/linux/man-pages/man2/prctl.2.html -- Zameer Manji

Re: Need inputs on scheduling

Mangirish Wagle > Graduate Student, Indiana University Bloomington > > -- > Zameer Manji >

A mini postmortem on snapshot failures

://github.com/apache/aurora/blob/rel/0.16.0/src/main/java/org/apache/aurora/scheduler/storage/log/SnapshotStoreImpl.java#L107-L127 -- Zameer Manji

Re: [Discussion] Implementing a is_health_check_enabled function OR by checking the presence of an instance of health checker

I have no strong preference either way. On Mon, Sep 26, 2016 at 11:25 AM, Huang Kai wrote: > Hi folks, > > I'm currently blocked on the review https://reviews.apache.org/r/51876. > I was wondering if you guys can provide some insights into the two proposed > approaches

Re: [VOTE] Release Apache Aurora 0.16.0 RC2

+1 (binding) On Fri, Sep 23, 2016 at 11:22 AM, John Sirois wrote: > +1 (binding) > > Verified via ./build-support/release/verify-release-candidate 0.16.0-rc2 > > On Fri, Sep 23, 2016 at 11:01 AM, karthik padmanabhan < > treadston...@gmail.com> wrote: > > > +1 > > > > On

Re: [VOTE] Release Apache Aurora 0.16.0 RC0

-1 I discovered https://issues.apache.org/jira/browse/AURORA-1777 in this release. On Mon, Sep 19, 2016 at 12:29 PM, Joshua Cohen wrote: > All, > > I propose that we accept the following release candidate as the official > Apache Aurora 0.16.0 release. > > Aurora 0.16.0-rc0

Re: Aurora 0.16.0 release

at 11:38 AM, Joshua Cohen <jco...@apache.org> wrote: > I don't consider it a blocker for 0.16.0, so... if it's ready before I cut > the release, great. If not, we'll get it into 0.17.0? > > On Fri, Sep 9, 2016 at 8:45 PM, Zameer Manji <zma...@apache.org> wrote: > > &g

Re: Aurora 0.16.0 release

e about AURORA-1708. > > > > As for AURORA-1680, it should be very safe to fix now. > > > > On Tue, Sep 6, 2016 at 1:18 PM, Zameer Manji <zma...@apache.org> wrote: > > > Should we fix AURORA-1707 in this release or bump it to the next > > release? I > &g

Re: [PROPOSAL] New RPC `fetchJobUpdates`

that the scheduler will sustain any damage as read-only > queries don't acquire any global or table locks. > > On Fri, Sep 2, 2016 at 3:24 PM, Zameer Manji <zma...@apache.org> wrote: > > I'm not convinced by your argument about adding a read only RPC that's > not > > cove

Re: Aurora 0.16.0 release

Should we fix AURORA-1707 in this release or bump it to the next release? I noticed that it has been unloved for some time. On Tue, Sep 6, 2016 at 10:54 AM, Zameer Manji <zma...@apache.org> wrote: > + 1 > > I think we are due for a release so folks can get Mesos 1.0 and GPU > s

Re: [DRAFT][REPORT] Apache Aurora - September 2016

+1 Thanks for drafting this up so quickly. On Tue, Sep 6, 2016 at 11:52 AM, Jake Farrell wrote: > Please take a second to review the draft board report below and let me > know if there are any modifications that should be made. I will submit this > in the next couple days

Re: Aurora 0.16.0 release

+ 1 I think we are due for a release so folks can get Mesos 1.0 and GPU support. On Tue, Sep 6, 2016 at 8:36 AM, Joshua Cohen wrote: > Hi Aurorans, > > I plan to kick off the 0.16.0 release some time later this week. Please let > me know if there are any outstanding patches

Re: 答复: Discussion on review request 51536

executor, we should > rolled out a new client in order to use the health-check feature. Hence the > executor and client rolling out process seem to be coupled. > > > > > -- > *发件人:* 黄 凯 <texasred2...@hotmail.com> > *发送时间:* 2016年9月3日 7:23 &g

Re: Discussion on review request 51536

ion speed. This can ensure that users don't deploy "too fast" and end up overwhelming other services if they are deployed too quickly. > > > On Fri, Sep 2, 2016 at 2:26 PM, Zameer Manji <zma...@apache.org> wrote: > > *cc: Renan* > > > > I think there is

Re: [PROPOSAL] New RPC `fetchJobUpdates`

much after we migrated to MVStore on the H2 side. There are no table > locks acquired and the only downside would be pulling events along > with what you need. Provided the query is narrowly scoped, that should > deliver acceptable performance. > > On Thu, Sep 1, 2016 at 2:24 PM,

Re: Discussion on review request 51536

*cc: Renan* I think there is some disagreement/discussion on the review because we have not achieved consensus on the design. Since the design doc was written, Aurora adopted multiple executor support as well non HTTP based healthchecking. This invalidates some parts of the original design. I

[PROPOSAL] New RPC `fetchJobUpdates`

jobUpdateQuery) If there are no objections, I will file tickets and put up a patch to implement this. -- Zameer Manji

Re: [FEEDBACK] Transitioning Aurora leader election to Apache Curator (`-zk_use_curator`)

Could we change the default and drop the old code at the same time? I don't see any benefit of letting that hang around. I have not tested this code yet, but I hope to do it soon. On Wed, Aug 24, 2016 at 5:19 AM, Erb, Stephan wrote: > The curator backend has been

Re: [PROPOSAL] Move Aurora discussions to Slack?

I'm also +0 for the same reasons that John listed. On Tue, Aug 2, 2016 at 2:44 PM, John Sirois wrote: > I'm also +0. > > I am not a Slack fan, but that said, the barrier to entry on the face is > the same if we publicize self-signup like mesos has on their community page

Re: [DRAFT][REPORT]: Apache Aurora

Jake, Shouldn't we mention that our PMC Chair has resigned? On Fri, Jun 10, 2016 at 8:06 PM, Jake Farrell wrote: > Please take a second to review the board report below and provide any > feedback (+1 or any desired modifications). I will submit this report > pending any

Bug in pants and pex effecting python bdist resolution

issue. Once that version is released, I will be sure to upgrade pants in our repo. -- Zameer Manji

Re: [VOTE] Release Apache Aurora 0.13.0 RC0

; > > > > > > >>> > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=aurora.git=CHANGELOG=rel/0.13.0-rc0 > > > > > >>> > > > > > >>> > > > > > >>> The CHANGELOG looks light with 2 entries, but that may be > > correct. > > > > If > > > > > >>> its > > > > > >>> not correct, I'm not sure if this is an RC blocker or not ... I > > > voted > > > > > >>> assuming it was not. > > > > > >>> > > > > > >>> > > > > > >>> > > > > > > >>> > > > > > > >>> > The tag used to create the release candidate is: > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=aurora.git;a=shortlog;h=refs/tags/rel/0.13.0-rc0 > > > > > >>> > > > > > > >>> > The release candidate is available at: > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/aurora/0.13.0-rc0/apache-aurora-0.13.0-rc0.tar.gz > > > > > >>> > > > > > > >>> > The MD5 checksum of the release candidate can be found at: > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/aurora/0.13.0-rc0/apache-aurora-0.13.0-rc0.tar.gz.md5 > > > > > >>> > > > > > > >>> > The signature of the release candidate can be found at: > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/aurora/0.13.0-rc0/apache-aurora-0.13.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 Apr 14 23:24:12 EDT 2016, please > > vote > > > > > >>> > > > > > > >>> > [ ] +1 Release this as Apache Aurora 0.13.0 > > > > > >>> > [ ] +0 > > > > > >>> > [ ] -1 Do not release this as Apache Aurora 0.13.0 because... > > > > > >>> > > > > > > >>> > > > > > > >>> > I'd like to get the voting started with my own +1 > > > > > >>> > > > > > > >>> > -Jake > > > > > >>> > > > > > > >>> > > > > > >> > > > > > > > > > > > > > > > > > > > > > > -- > Zameer Manji > >

Re: Populate DiscoveryInfo in Mesos

gt; >> questionnaire about which fields would be useful for > community, > > or > > > > > what > > > > > > >> value they should take? > > > > > > >> > > > > > > >> On Mon, Mar 7, 2016 at 1:00 AM, Erb, Stephan < > > > > > > stephan@blue-yonder.com > > > > > > >> > > > > > > > >> wrote: > > > > > > >> > > > > > > >> > That sounds like a good idea! Great. > > > > > > >> > > > > > > > >> > If you go ahead with this, please be so kind and start by > > > posting > > > > a > > > > > > >> short > > > > > > >> > design document here on mailinglist (similar to those here > > > > > > >> > > > > > > > > https://github.com/apache/aurora/blob/master/docs/design-documents.md > > > > > > , > > > > > > >> > but probably shorter). > > > > > > >> > > > > > > > >> > This will allow us to split the discussion of the design > from > > > > > > discussing > > > > > > >> > the actual implementation. I believe this is necessary, as > the > > > > > > >> > DiscoveryInfo protocol is quite flexible ( > > > > > > >> > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > http://mesos.apache.org/documentation/latest/app-framework-development-guide/ > > > > > > >> > ). > > > > > > >> > > > > > > > >> > Thanks, > > > > > > >> > Stephan > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > > > >> > From: Zhitao Li <zhitaoli...@gmail.com> > > > > > > >> > Sent: Monday, March 7, 2016 00:05 > > > > > > >> > To: dev@aurora.apache.org > > > > > > >> > Subject: Populate DiscoveryInfo in Mesos > > > > > > >> > > > > > > > >> > Hi, > > > > > > >> > > > > > > > >> > It seems like Aurora does not populate the "discovery" field > > in > > > > > either > > > > > > >> > TaskInfo or ExecutorInfo in mesos.proto > > > > > > >> > < > > > > > > >> > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L438 > > > > > > >> > > > > > > > > >> > . > > > > > > >> > > > > > > > >> > I'm considering adding this to support retrieving port map > in > > > > Mesos > > > > > > >> > directly. This would enable us to discovery this information > > > > > directly > > > > > > >> from > > > > > > >> > Mesos side, and also enables us to build one universal > service > > > > > > discovery > > > > > > >> > solution for multiple frameworks including Aurora. > > > > > > >> > > > > > > > >> > If no objection, I'll create a JIRA ticket for this task. > > > > > > >> > > > > > > > >> > Thanks. > > > > > > >> > -- > > > > > > >> > Cheers, > > > > > > >> > > > > > > > >> > Zhitao Li > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> -- > > > > > > >> Cheers, > > > > > > >> > > > > > > >> Zhitao Li > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Cheers, > > > > > > > > > > > > > > Zhitao Li > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Cheers, > > > > > > > > > > > > Zhitao Li > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Cheers, > > > > > > > > Zhitao Li > > > > > > > > > > > > > > > > -- > > > Cheers, > > > > > > Zhitao Li > > > > > > > > > -- > Cheers, > > Zhitao Li > > -- > Zameer Manji > >

Re: [DISCUSS]: 0.13.0 release candidate

utting the release candidate > this > > Wednesday, April 6th, pending no blockers coming out of this discussion > > thread. Thoughts, objections? > > > > -Jake > > > > > > [1]: https://issues.apache.org/jira/browse/AURORA-1584 > > > > -- > Zameer Manji > >

Re: aurora job scalability

ize. I'm wondering if this type of a thing has potentially > > been fixed already in Aurora. > > > > > > > > > > > > > > Christopher M Luciano > > > > Staff Software Engineer, Platform Services > > > > IBM Watson Core Technology > > > > > > > > > > > > -- > Zameer Manji > >

Re: problem commiting the transaction to the log

Impl.java:267) > at > org.apache.aurora.scheduler.storage.log.LogStorage$24.apply(LogStorage.java:616) > ... 76 more > Caused by: java.util.concurrent.TimeoutException: Timed out while > attempting to append > at org.apache.mesos.Log$Writer.append(Native Method) > at > org.apache.aurora.scheduler.log.mesos.MesosLogStreamModule$5.append(MesosLogStreamModule.java:188) > at > org.apache.aurora.scheduler.log.mesos.MesosLog$LogStream$3.apply(MesosLog.java:319) > at > org.apache.aurora.scheduler.log.mesos.MesosLog$LogStream$3.apply(MesosLog.java:315) > at > org.apache.aurora.scheduler.log.mesos.MesosLog$LogStream.mutate(MesosLog.java:365) > ... 82 more > > -- > Zameer Manji > >

Re: [PROPOSAL] Change java thrift code gen

n and actually run > the > > codegen (`./gradlew api:compileJava`). > > The conversion RB (#3) is large but the changes are mainly mechanical > > conversions from the current mutable thrift + I* wrappers to pure > immutable > > thrift mutated via `.toBuilder` and `.with`'er methods. The main changes > > of note are to the portions of the codebase tightly tied to thrift as a > > technology: > > + Gson/thrift converters > > + Shiro annotated auth param interception > > + Thrift/Servlet binding > > > > [1] > > > https://github.com/apache/aurora/blob/master/src/main/python/apache/aurora/tools/java/thrift_wrapper_codegen.py > > [2] https://issues.apache.org/jira/browse/AURORA-987 > > [3] > > > https://docs.google.com/spreadsheets/d/1-CYMnEjzknAsY5_r_NVX8r85wxtrEByZ5YRiAbgMhP0/edit#gid=840229346 > > [4] https://github.com/facebook/swift > > [5] https://github.com/square/javapoet > > [6] https://github.com/google/compile-testing > > > > -- > Zameer Manji > >

Re: PROPOSAL: Host and support nightly Aurora builds on Apache servers

t some projects eg Zookeeper provide alpha > releases[1] while Mesos does not[2]. > > Thanks, > Dmitriy. > > > [1] https://www.apache.org/dist/zookeeper/ > [2] http://archive.apache.org/dist/mesos/ > > -- > Zameer Manji > > <http://archive.apache.org/dist/mesos/>

Re: [PROPOSAL] Amend 0.12.0 release goals

0.12.0 since we have an in-fight patch that looks close to completion: > >> > > >> > https://issues.apache.org/jira/browse/AURORA-1109 > >> > >> > >> +1 to the proposal, catching up would be good to do. > >> > >> I clarified the status of AURORA-987 by stopping progress and > >> un-assigning. Although I'm working towards that ticket, its by very > >> indirect means still and I'll re-assign and re-start once I'm actually > >> engaged in the meat of the API proposal that is needed assuming no one > else > >> has dived in. > >> > >> > >> > > >> > > >> > > >> > Cheers, > >> > > >> > Bill > >> > > >> > >> > >> > >> -- > >> John Sirois > >> 303-512-3301 > >> > > -- > Zameer Manji > >

Re: [PROPOSAL] Replace commons-args

public interface Params { > > > > >> > @Help("Name to identify the cluster being served.") > > > > >> > String clusterName(); > > > > >> > > > > > >> > @NotEmpty > > > > >> > @Help("ZooKeeper Server

Re: [PROPOSAL] Use standard logging practices

.util.logging, but i suggest we retain that backend > for now (since it's what we're currently using). > > -- > Zameer Manji > >

Re: [VOTE] Release Apache Aurora 0.11.0 debs

0.11.x > >> > > >> > The packages are available at: > >> > > >> > > >> > http://people.apache.org/~wfarner/aurora/distributions/0.11.0/deb/ubuntu-trusty/ > >> > > >> > The GPG keys used to sign the packages are available at: > >> > https://dist.apache.org/repos/dist/release/aurora/KEYS > >> > > >> > Please download, verify, and test. > >> > > >> > The vote will close on Wed Jan 6 20:00:00 PT 2015 > >> > > >> > [ ] +1 Release these as the deb packages for Apache Aurora 0.11.0 > >> > [ ] +0 > >> > [ ] -1 Do not release these artifacts because... > >> > > >> > I would like to get the voting started off with my own +1 > >> > > >> > > > > > > > > -- > > John Sirois > > 303-512-3301 > > > > > > -- > John Sirois > 303-512-3301 > > -- > Zameer Manji > > <303-512-3301>

Re: [VOTE] Release Apache Aurora 0.11.0 RC1

; The MD5 checksum of the release candidate can be found at: > > > > > > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/aurora/0.11.0-rc1/apache-aurora-0.11.0-rc1.tar.gz.md5 > > > > > > > > > > The signature of the release candidate can be found at: > > > > > > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/aurora/0.11.0-rc1/apache-aurora-0.11.0-rc1.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 Tue Dec 22 15:18:55 PST 2015 > > > > > > > > > > [ ] +1 Release this as Apache Aurora 0.11.0 > > > > > [ ] +0 > > > > > [ ] -1 Do not release this as Apache Aurora 0.11.0 because... > > > > > > > > > > > > > > > > > > > > > -- > > > John Sirois > > > 303-512-3301 > > > > > > -- Zameer Manji

Re: Proposal - no IRC meeting until 1/4

; suggest we reconvene IRC meetings on 1/4. > > -- > Zameer Manji > >

Re: Mac OSX brew aurora-cli support

nary we host. Is that reasonable? > > On Tue, Nov 24, 2015 at 11:44 AM, Zameer Manji <zma...@apache.org> wrote: > > > On Mon, Nov 23, 2015 at 9:16 PM, Bill Farner <wfar...@apache.org> wrote: > > > > > That's awesome, thanks for doing that! Any sense if it wou

[RESULT] [VOTE] Release Apache Aurora 0.10.0 RC2

All, The vote to accept Apache Aurora 0.10.0 RC2 as the official Apache Aurora 0.10.0 release has passed. +1 (Binding) - Zameer Manji Maxim Khutornenko Bill Farner Jake Farrell +1 Joshua Cohen There were 5 +1 votes (4 binding) and no 0 or -1 votes. Thank you to all who

Re: [VOTE] Release Apache Aurora 0.10.0 RC2

+1 (binding). I verified this release on a clean machine running OSX 10.10 using the ./build-support/release/verify-release-candidate script. On Wed, Nov 11, 2015 at 8:11 PM, Zameer Manji <zma...@apache.org> wrote: > All, > > I propose that we accept the following re

[VOTE] Release Apache Aurora 0.10.0 RC0

are available at: https://dist.apache.org/repos/dist/dev/aurora/KEYS Please download, verify, and test. The vote will close on Fri Nov 13 12:30:00 PST 2015 [ ] +1 Release this as Apache Aurora 0.10.0 [ ] +0 [ ] -1 Do not release this as Apache Aurora 0.10.0 because... -- Zameer Manji

Re: [VOTE] Release Apache Aurora 0.10.0 RC0

> ./build-support/release/verify-release-candidate 0.10.0-rc0 > > > Those of you installing Aurora in production environments, it would be wise > of you to do some live testing and report back. > > > On Tue, Nov 10, 2015 at 11:27 AM, Zameer Manji <zma...@apache.org> wr

Re: Multiple executor support

plugins/servlet/mobile#issue/AURORA-1376 > > It would help to know where we stand on this. > > Thx > > > Sent from my iPhone > > -- > Zameer Manji > >

0.10.0 Release Update

. There are dependencies of the RC ticket [0] have been resolved and I will be cutting a release within a few days. If anything must make this release please let me know ASAP. [0]: https://issues.apache.org/jira/browse/AURORA-1250 -- Zameer Manji

Re: update mesos 0.23 to 0.24

at '/mesos' in ZooKeeper > I0925 18:49:37.931046 224 detector.cpp:138] Detected a new leader: > (id='2513') > I0925 18:49:37.931131 224 group.cpp:659] Trying to get > '/mesos/json.info_002513' in ZooKeeper > Failed to detect a master: Failed to parse data of unknown label ' > json.info' > > > [1] http://mesos.apache.org/documentation/latest/upgrades/ > > -- > Zameer Manji > > <http://mesos.apache.org/documentation/latest/upgrades/>

Re: 0.10.0 Feature Requests

10, 2015 at 10:49 AM, Jake Farrell <jfarr...@apache.org> > > > > wrote: > > > > > > > > > Think that this is a great idea and agree that we need to spend > some > > > time > > > > > improving our user content, but it should not

Re: JobConfig diff API

Concerns: > >> > > - The executor data is currently treated as an opaque string blob on > >> > > the scheduler side. In reality, it's almost guaranteed to be JSON. > In > >> > > order to deliver the best UX, the scheduler would have to start > >> > > requiring ExecutorConfig.data to be a valid JSON. > >> > > > >> > > Any other concerns/objections/comments? I would like to formalize > the > >> > > proposal be EOW if we reach consensus quickly. > >> > > > >> > > Thanks, > >> > > Maxim > >> > > > >> > > [1] - > >> > > > >> > > >> > http://java-object-diff.readthedocs.org/en/latest/getting-started/#getting-started > >> > > [2] - http://javers.org/documentation/diff-examples/ > >> > > [3] - https://github.com/skyscreamer/JSONassert > >> > > > >> > > >> > > -- > Zameer Manji > >

Re: New email lists

> > Looks like one of the new lists is broken... :-/ > > <announce-subscr...@aurora.apache.org>: > > Sorry, no mailbox here by that name. (#5.1.1) > > > Chris > > -- > Zameer Manji > >

Re: Roadmap

+1 Please start the doc. Zameer Manji On Sep 8, 2015 5:11 PM, "Bill Farner" <wfar...@apache.org> wrote: > Reviving this thread - shall i go ahead and start the google doc for > discussion? > > On Wed, Sep 2, 2015 at 12:06 PM, Zameer Manji <zma...@twopensource.co

Re: Creating Aurora user@ and announcements@ lists?

> > through stats from other Apache projects and found that non-dev lists > > > tend to have a higher subscriber rate -- particularly user@ lists. > Let's > > > give a space for those members of the community. > > > > > > Thoughts? If I don't hear any objections, I'll go ahead and file an > > > INFRA ticket later this week. > > > > > > Dave > > > > > > > -- > Zameer Manji > >

Mechanics of Twitter Commons Import

and the history of files is easily available on github. Please +1 or -1 this approach. -- Zameer Manji

Re: [VOTE] Release Apache Aurora 0.9.0 RC0

with my own +1 -Jake -- Zameer Manji

Re: Forking twitter-commons into our tree

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 -Jake On Thu, Jul 2, 2015 at 3:20 PM, Zameer Manji zma...@apache.org wrote: Hey, Aurora depends heavily on twitter-commons for lots

Re: Forking twitter-commons into our tree

://issues.apache.org/jira/browse/AURORA-1213 _ From: Zameer Manji zma...@apache.org Sent: Thursday, July 2, 2015 12:20 PM Subject: Forking twitter-commons into our tree To: dev@aurora.apache.org Hey, Aurora depends heavily on twitter-commons for lots

Forking twitter-commons into our tree

move forward on this front. What are people's thoughts on this? -- Zameer Manji

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

. 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 -- Zameer Manji

Re: building aurora client on mac

, 2015 at 2:59 PM, Poppy poppyd...@gmail.com wrote: I am trying to build aurora client on mac for my cli usage. On Aurora git repo I do ./pants binary src/main/python/apache/aurora/client/cli:aurora Where does aurora client gets generated? Thx, Praveen -- Zameer Manji

Re: Human-readable release notes

/aurora/blob/master/CHANGELOG -=Bill -- Zameer Manji

Re: [DRAFT][REPORT] Apache Aurora

://s.apache.org/ytb [3] http://s.apache.org/gmt [4] http://s.apache.org/KIm -=Bill -- Kevin Sweeney @kts -- Zameer Manji