Re: /etc/passwd in containers

e aurora role? If it did, we > would be able to solve this problem by having mesos generate a sensible > /etc/passwd for containers. > > Thanks! > Jay > > [1] > > https://github.com/apache/incubator-aurora/blob/master/src/main/python/apache/aurora/executor/common/sandbox.

Re: Data processing pipeline workflow management

27;m not aware of any batch/workflow Mesos framework. If you want some or all of the above features on top of Mesos, I think you would be venturing into writing your own framework. Aurora doesn't have the concept of DAG and it can't make scheduling decisions based on job progress or HDFS state. -- Zameer Manji

Re: Shepherding new contributions

that we > generally > > have a policy that you need a ship it from everyone on the People line > of a > > review. If that's the case than the default people need to be cognizant > of > > their default status and be sure to remove themselves when appropriate >

Re: Shepherding new contributions

t; active committers or result in a subset of committers being on the hook > > for > > > all reviews from first time contributors. > > > > > > Establishing Shepherds seems like a good compromise. > > > > > > On Mon, Feb 23, 2015 at 11:53 AM, Za

Re: [proposal] Deprecate the Thermos CLI

Possibly. Without the CLI I don't see how we can access the data. On Mon, Feb 23, 2015 at 4:01 PM, Bill Farner wrote: > Couldn't (yet-to-be-surfaced) information in the sandbox satisfy #2? > > -=Bill > > On Mon, Feb 23, 2015 at 3:58 PM, Zameer Manji wrote: > &g

Re: [proposal] Deprecate the Thermos CLI

.org > > > > > >>> > wrote: > > > > > >>> > > > > > >>>>> Moving parts should either provide value or be obliterated > from > > > our > > > > > >>>> source tree. > > > >

Re: Shepherding new contributions

rds seems like a good compromise. > > On Mon, Feb 23, 2015 at 11:53 AM, Zameer Manji wrote: > > > Hey, > > > > With the increased interest in Aurora, the project has started to receive > > more contributions from non-committers. By default we do not populate the > &

Shepherding new contributions

establish Shepherds, who are responsible for dealing with reviews that don't have established reviewers. The responsibility could be limited to finding committers who are willing to review the code. What do people think about this idea? -- Zameer Manji

Re: Build failed in Jenkins: Aurora #889

thon.apache.aurora.config.test_constraint_parsing > . SUCCESS > src.test.python.apache.aurora.config.test_loader > . SUCCESS > src.test.python.apache.aurora.config.test_thrift > . SUCCESS > > src.test.python.apache.aurora.executor.common.announcer > . SUCCESS > > src.test.python.apache.aurora.executor.common.directory_sandbox > . SUCCESS > > src.test.python.apache.aurora.executor.common.executor_detector > . SUCCESS > > src.test.python.apache.aurora.executor.common.executor_timeout > . SUCCESS > > src.test.python.apache.aurora.executor.common.health_checker > . FAILURE > > src.test.python.apache.aurora.executor.common.path_detector > . SUCCESS > > src.test.python.apache.aurora.executor.common.task_info > . SUCCESS > src.test.python.apache.aurora.executor.executor_base > . SUCCESS > src.test.python.apache.aurora.executor.executor_vars > . SUCCESS > > src.test.python.apache.aurora.executor.status_manager > . SUCCESS > > src.test.python.apache.aurora.executor.thermos_task_runner > . SUCCESS > src.test.python.apache.thermos.common.test_pathspec >. SUCCESS > > src.test.python.apache.thermos.core.test_runner_integration > . SUCCESS > src.test.python.apache.thermos.monitoring.test_disk >. SUCCESS > > FAILURE > > [31m >FAILURE [0m > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Re: Soliciting feature requests for 0.8.0

arrell has volunteered to act as Release Manager for 0.8.0 > (thanks, > > > Jake!), but if any other PPMC member would like to cut their teeth at > > this, > > > he will happily be relieved of the duty :-) > > > > > > So with that, please feel free to +/-1, +0 individual features listed > > > above, or suggest additional features we should target! > > > > > > > > > -=Bill > > > > > > > -- > Zameer Manji > >

Re: [VOTE] Graduate Apache Aurora as a TLP

urther > > > > RESOLVED, that the persons listed immediately below be and > > hereby are appointed to serve as the initial members of the > > Apache Aurora Project: > > > >* Mark Chu-Carroll > >* William Farner > >* Jake Farrell > &

Re: [proposal] Deprecate the Thermos CLI

it absolutely is- ideally as we deprecate the Observer, we can > then lean on the Mesos Slave for this information instead. This will > further decrease the number of moving pieces, simplifying the operation of > an Aurora/Mesos cluster. > > > On Feb 17, 2015, at 6:33 PM

Re: [proposal] Deprecate the Thermos CLI

also forces people to > remember + learn the port the Observer is running on in order to get > information about tasks. > > Any thoughts and opinions would be much appreciated! > > Thanks! > Joe > > -- > Zameer Manji > >

Re: Build issues: Thermos executor not working

> >> I have attached the pants build log. It seems like pants is pulling in a > >> wrong protobuf version (protobuf-3.0.0_alpha_1 instead of protobuf > 2.6.1). > >> > >> The issue can even be simulated locally: > >> * pip install mesos.interface with an old virtualenv 1.11 (including pip > >> 1.5 and setuptools 2.0.2) pulls in protobuf-3.0.0-alpha-1 > >> * pip install mesos.interface with the latest and greatest pip 6.0.8 and > >> setuptools 12.2 pulls protobuf-2.6.1 > >> > >> How can this happen? Isn't the "build-support/virtualenv" script > supposed > >> to prevent that? I also tried patching the setuptools_version in > pants.ini, > >> but it did not help. > >> > >> Any ideas? > >> > >> Best Regards, > >> Stephan > >> > >> > >> > >> > >> > > > -- Zameer Manji

Re: [DISCUSS] Use the Apache Shiro framework for scheduler security

ey session) { … > } > > They'd become > > @RequiresPermission("maintenance:create") > > public Response startMaintenance(Set hosts) { … } > Client-side changes > > No changes are necessary to use HTTP Basic Auth - requests will > automatically use a .netrc file today. > > An optional dependency on kerberos and requests-kerberos can be added to > support SPNEGO authentication. > Timeline > > I would like to land support for HTTP Basic Auth and SPNEGO in 0.8.0 and > deprecate the SessionKey-based API for authentication in favor of fully > transport-based authentication. > > In 0.9.0 I propose removing SessionKey from the API entirely along with > SessionValidator from the scheduler. > -- Zameer Manji

Re: Feature proposal: ability to apply a block on all updates in the scheduler

ery simple (reject new RPCs but > allow > > existing operations to continue) or it can start to get complicated (also > > pause all in-progress updates and other reschedule events). > > > > Would welcome feedback on this idea before I create a ticket. > > > > > > Thanks, > > David > > -- > Zameer Manji > >

Re: thermos observer resource monitoring

rver as well > (we find it burns 2-4% CPU per box in practice.) > > ~brian > > -- > Zameer Manji > >

Re: Gsoc 2015

Apache Aurora. How > can I get involved ? > > Thank you very much, > > Cheers, > Abhinav Gupta. > -- Zameer Manji

Re: Subject: [VOTE] Release Apache Aurora 0.7.0 (incubating) RC3

/dist/dev/incubator/aurora/0.7.0-rc3/apache-aurora-0.7.0-rc3-incubating.tar.gz.md5 > > > > > > The signature of the release candidate can be found at: > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/aurora/0.7.0-rc3/apache-aurora-0.7.0-rc3-incubating.tar.gz.asc > > > > > > The GPG key used to sign the release are available at: > > > https://dist.apache.org/repos/dist/dev/incubator/aurora/KEYS > > > > > > Please download, verify, and test. > > > > > > The vote will close on Wed Feb 4 19:50:47 PST 2015 > > > > > > [ ] +1 Release this as Apache Aurora 0.7.0 > > > [ ] +0 > > > [ ] -1 Do not release this as Apache Aurora 0.7.0 because... > > > > > > > -- > Zameer Manji > >

Re: [VOTE] Release Apache Aurora 0.7.0 (incubating) RC2

ating.tar.gz > > >>> > > >>> The MD5 checksum of the release candidate can be found at: > > >>> > > > https://dist.apache.org/repos/dist/dev/incubator/aurora/0.7.0-rc2/apache-aurora-0.7.0-rc2-incubating.tar.gz.md5 > > >>> > > >>> The signature of the release candidate can be found at: > > >>> > > > https://dist.apache.org/repos/dist/dev/incubator/aurora/0.7.0-rc2/apache-aurora-0.7.0-rc2-incubating.tar.gz.asc > > >>> > > >>> The GPG key used to sign the release are available at: > > >>> https://dist.apache.org/repos/dist/dev/incubator/aurora/KEYS > > >>> > > >>> Please download, verify, and test. > > >>> > > >>> The vote will close on Fri Jan 30 17:23:36 PST 2015 > > >>> > > >>> [ ] +1 Release this as Apache Aurora 0.7.0 > > >>> [ ] +0 > > >>> [ ] -1 Do not release this as Apache Aurora 0.7.0 because... > > >>> > > >>> Thanks, > > >>> Maxim > > > -- Zameer Manji

Re: [VOTE] Release Apache Aurora 0.7.0 (incubating) RC2

7:23:36 PST 2015 > > [ ] +1 Release this as Apache Aurora 0.7.0 > [ ] +0 > [ ] -1 Do not release this as Apache Aurora 0.7.0 because... > > Thanks, > Maxim > > -- > Zameer Manji > >

Re: When (if ever) should we require JDK 8?

side-effect of using java 8 > > > > language features is that it requires a >= 1.8 runtime, This means > > users > > > > currently running the scheduler with java 1.7 would need to upgrade > > their > > > > JRE. We have a ticket [1] to track adopting JDK 8 on our end. > > > > > > > > Does anyone have an opinion on which release we should aim to include > > > this > > > > change in, if at all? > > > > > > > > [1] https://issues.apache.org/jira/browse/AURORA-274 > > > > > > > > > > > > -=Bill > > > > > > > > > > -- Zameer Manji

Re: Welcome, Zameer! New committer/PMC member

Thanks everyone! On Wed, Jan 14, 2015 at 3:32 PM, Joseph Smith wrote: > Huzzah! Well deserved! > > > On Jan 14, 2015, at 3:18 PM, Bill Farner wrote: > > > > I'm proud to announce that Zameer Manji has accepted the Apache Aurora > > PMC's invitati

Re: Should we continue to maintain fine-grained python BUILD targets?

ot convinced these benefits outweigh the maintenance burden of these > > files. I propose we reduce our BUILD targets to ~equal to the number of > > binaries we produce, possibly with a few for libraries shared between > > components. > > > > Does anyone else have opinions on this? Is there something i'm > > overlooking? > > > > > > -=Bill > > > -- Zameer Manji

Re: api vs apibeta

, variance was small in each case): >>> > >>> > 1) aurora2 client: ./aurora2 job status cluster//prod > /dev/null >>> > 126.0sec >>> > >>> > 2) golang thrift API >>> > 584.3sec (I might be able make a better task query, but still... this >>> is >>> > for only ~120 calls) >>> > >>> > 3) Pure json apibeta client in golang >>> > 13.4sec (again, might be able to optimize query strategy) >>> > >>> > As a side note, getting the golang thrift client to work was a very >>> painful >>> > and illuminating experience. >>> > >>> > I'm inclined to stick with apibeta. It's fast and the documentation is >>> > great. If api changes become a concern, well after today I'd honestly >>> > prefer rolling my own binding generator. >>> > >>> > Are there plans for /apibeta wrt /api? >>> > >>> >> >> > -- Zameer Manji

Re: Using immutables.org for Java code

wrote: > > It looks quite interesting as a general case for immutability. As for > replacing our immutable thrift implementation, is there anything in > particular you noticed in immutables.org that we currently lack? > -- Zameer Manji

Using immutables.org for Java code

ion methods. What are people's thoughts on this library? -- Zameer Manji

Re: some questions

h only > appears on /slaves. > > Noted on separate zookeepers. > > thanks > > On Mon, Dec 15, 2014 at 3:19 PM, Zameer Manji > wrote: > > > > The output of /slaves is not in a machine readable format. I believe > there > > is a ticket somewhere that tracks

Re: some questions

Annoucer. what is the recommended > practice for which zookeepers to use? should I use the same ones for > aurora+mesos? or a separate set for this service? > > thanks in advance. > -- Zameer Manji

0.7.0 Release Manager

release process to spread knowledge about the release process around. Do we have any takers? -- Zameer Manji

Simplifying the logging code in the Aurora client

Hey, I have put up a review[1] which changes out the client does logging. If you care about how that works please chime in on the review with your thoughts. [1]: https://reviews.apache.org/r/28742/ -- Zameer Manji

Re: [DISCUSS] Features for 0.7.0

> > - begin phasing out the 'v1' client > > > > - promote server-side updates, phase out client-side job update > > behavior > > > > > > > > With that in mind, what else would you all (non-committers welcome) > > like > > > to > > > > see in 0.7.0? > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/AURORA-872 > > > > [2] https://issues.apache.org/jira/browse/AURORA-423 > > > > > > > > > > > > -=Bill > > > > > > > > > > -- Zameer Manji

Re: Build failed in Jenkins: Aurora #747

e.aurora.client.commands.run > . SUCCESS > src.test.python.apache.aurora.client.commands.ssh > . SUCCESS > src.test.python.apache.aurora.client.config > . SUCCESS > src.test.python.apache.aurora.client.hooks.hooked_api > . SUCCESS > src.test.python.apache.aurora.client.hooks.non_hooked_api > . SUCCESS > src.test.python.apache.aurora.common.test_aurora_job_key > . SUCCESS > src.test.python.apache.aurora.common.test_cluster > . SUCCESS > src.test.python.apache.aurora.common.test_cluster_option > . SUCCESS > src.test.python.apache.aurora.common.test_clusters > . SUCCESS > src.test.python.apache.aurora.common.test_http_signaler > . SUCCESS > src.test.python.apache.aurora.common.test_shellify > . SUCCESS > src.test.python.apache.aurora.common.test_transport > . SUCCESS > src.test.python.apache.aurora.config.test_base > . SUCCESS > src.test.python.apache.aurora.config.test_constraint_parsing > . SUCCESS > src.test.python.apache.aurora.config.test_loader > . SUCCESS > src.test.python.apache.aurora.config.test_thrift > . SUCCESS > src.test.python.apache.aurora.executor.executor_base > . SUCCESS > src.test.python.apache.aurora.executor.executor_detector > . SUCCESS > src.test.python.apache.aurora.executor.executor_vars > . SUCCESS > src.test.python.apache.aurora.executor.status_manager > . SUCCESS > src.test.python.apache.aurora.executor.thermos_task_runner > . FAILURE > Build step 'Execute shell' marked build as failure > Recording test results > Updating AURORA-933 > -- Zameer Manji

Re: [VOTE] Release Apache Aurora 0.6.0 (incubating) RC2

1 Release this as Apache Aurora 0.6.0 > [ ] +0 > [ ] -1 Do not release this as Apache Aurora 0.6.0 because... > > > -=Bill > -- Zameer Manji

Re: [VOTE] Release Apache Aurora 0.6.0 (incubating) RC1

ing.tar.gz.asc > > > > > > The GPG key used to sign the release are available at: > > > https://dist.apache.org/repos/dist/dev/incubator/aurora/KEYS > > > > > > Please download, verify, and test. > > > > > > The vote will close on Thu Nov 13 14:21:00 PST 2014 > > > > > > [ ] +1 Release this as Apache Aurora 0.6.0 > > > [ ] +0 > > > [ ] -1 Do not release this as Apache Aurora 0.6.0 because... > > > > > > > > > -=Bill > > > > > > -- Zameer Manji

Re: Build failed in Jenkins: Aurora #666

ttps://pypi.python.org/simple/pytest/ :: Opening (uncached) :: Fetching > https://pypi.python.org/simple/pytest/ :: Resolving pypi.python.org > twitter.common.python.http: Timed out resolving pypi.python.org > twitter.common.python.http: Failed to fetch > https://pypi.python.org/simple/pytest/: Could not reach > https://pypi.python.org/simple/pytest/ within deadline. > Traceback (most recent call last): > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/bin/pex";,> > line 9, in > load_entry_point('twitter.common.python==0.5.9', 'console_scripts', > 'pex')() > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 320, in main > pex_builder = build_pex(args, options) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 284, in build_pex > platform=options.platform) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/resolver.py";,> > line 98, in resolve > raise Unsatisfiable('Cannot satisfy requirements: %s' % > requirement_set[requirement.key]) > twitter.common.python.resolver.Unsatisfiable: Cannot satisfy requirements: > [Requirement.parse('pytest>=2.6,<2.7')] > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Re: executor build issue

n interpreters to use. Uses > Requirement format from pkg_resources, e.g. > 'CPython>=2.6,<3' or 'PyPy'. By default, no > constraints are used. Multiple constraints may be > added. They will be ORed together. > -v, --verbose Show verbose output. > -f, --fastRun tests in a single chroot. > > Builds the specified Python target(s). Use ./pants goal for JVM and other > targets. > Build operating on top level addresses: > > set([BuildFileAddress(/mnt/data1/apache/incubator-aurora/src/main/python/apache/aurora/executor/bin/BUILD, > thermos_runner)]) > Building PythonBinary > > PythonBinary(BuildFileAddress(/mnt/data1/apache/incubator-aurora/src/main/python/apache/aurora/executor/bin/BUILD, > thermos_runner)): > Wrote /mnt/data1/apache/incubator-aurora/dist/thermos_runner.pex > :4: UserWarning: Duplicate name: > 'apache/aurora/executor/resources/__init__.py' > :5: UserWarning: Duplicate name: > 'apache/aurora/executor/resources/thermos_runner.pex' > > /*** > Joe Stein > Founder, Principal Consultant > Big Data Open Source Security LLC > http://www.stealth.ly > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > / > -- Zameer Manji

Re: Storage is not READY

ine.java:91) > > > at > > > > > > com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62) > > > at > > > > > > com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168) > > > at > > > > > > com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58) > > > at > > > > > > com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168) > > > > > > > > > /*** > > > Joe Stein > > > Founder, Principal Consultant > > > Big Data Open Source Security LLC > > > http://www.stealth.ly > > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > > / > > > -- Zameer Manji

Re: Health Check Disabler Discussion

y, and is no > > longer there to re-enable the health checks. > > > > I would like to invite anyone interested to voice your opinions and chime > > in. > > > > Thanks, > > > > David Pan > -- Zameer Manji

Re: Build failed in Jenkins: Aurora #636

d? > > On Thu, Oct 9, 2014 at 11:48 AM, Zameer Manji > wrote: > > > I think to fix this problem we might need to get pex to do HTTP retries. > > > > On Thu, Oct 9, 2014 at 11:43 AM, Apache Jenkins Server < > > jenk...@builds.apache.org> wrote: > > &g

Re: Build failed in Jenkins: Aurora #636

twitter.common.python.http: Failed to fetch > https://pypi.python.org/simple/twitter.common.log/: Could not reach > https://pypi.python.org/simple/twitter.common.log/ within deadline. > Traceback (most recent call last): > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/bin/pex";,> > line 9, in > load_entry_point('twitter.common.python==0.5.9', 'console_scripts', > 'pex')() > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 320, in main > pex_builder = build_pex(args, options) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 284, in build_pex > platform=options.platform) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/resolver.py";,> > line 98, in resolve > raise Unsatisfiable('Cannot satisfy requirements: %s' % > requirement_set[requirement.key]) > twitter.common.python.resolver.Unsatisfiable: Cannot satisfy requirements: > [Requirement.parse('twitter.common.log>=0.3.1,<0.4')] > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Re: Build failed in Jenkins: Aurora #633

https://issues.apache.org/jira/browse/AURORA-819 On Wed, Oct 8, 2014 at 2:10 PM, Bill Farner wrote: > Can you? > > -=Bill > > On Wed, Oct 8, 2014 at 2:04 PM, Zameer Manji > wrote: > >> Bill, I think you added code coverage to gradle. Can you check what is >> g

Re: Build failed in Jenkins: Aurora #633

t; build_gsqlbkk7l35mk455mp7a81015$_run_closure24_closure62_closure63_closure64.doCall(< > https://builds.apache.org/job/Aurora/ws/build.gradle>:595) > at > build_gsqlbkk7l35mk455mp7a81015$_run_closure24_closure62_closure63.doCall(< > https://builds.apache.org/job/Aurora/ws/build.gradle>:589) > at > build_gsqlbkk7l35mk455mp7a81015$_run_closure24_closure62.doCall(< > https://builds.apache.org/job/Aurora/ws/build.gradle>:588) > at > org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:548) > at > org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:529) > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80) > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61) > ... 47 more > > > BUILD FAILED > > Total time: 6 mins 0.964 secs > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Re: Build failed in Jenkins: Aurora #622

; https://pypi.python.org/simple/cov-core/ :: Opening (uncached) :: > Fetching https://pypi.python.org/simple/cov-core/ > twitter.common.python.http: Crawling > https://pypi.python.org/simple/cov-core/ :: Opening (uncached) :: > Fetching https://pypi.python.org/simple/cov-core/ :: Resolving > pypi.python.org > twitter.common.python.http: Timed out resolving pypi.python.org > twitter.common.python.http: Failed to fetch > https://pypi.python.org/simple/cov-core/: Could not reach > https://pypi.python.org/simple/cov-core/ within deadline. > Traceback (most recent call last): > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/bin/pex";,> > line 9, in > load_entry_point('twitter.common.python==0.5.9', 'console_scripts', > 'pex')() > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 320, in main > pex_builder = build_pex(args, options) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 284, in build_pex > platform=options.platform) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/resolver.py";,> > line 98, in resolve > raise Unsatisfiable('Cannot satisfy requirements: %s' % > requirement_set[requirement.key]) > twitter.common.python.resolver.Unsatisfiable: Cannot satisfy requirements: > [Requirement.parse('cov-core>=1.14.0')] > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Re: Removing Aurora's special handling of the 'rack' attribute

nd avoid the need for 2 deprecation cycles? > With that change folks with existing Mesos clusters would be able to deploy > Aurora without changing the attributes flag on every slave (which requires > rebooting the entire cluster to take effect). > > On Mon, Oct 6, 2014 at 5:24 PM, Zameer M

Re: Removing Aurora's special handling of the 'rack' attribute

I currently don't plan on removing 'host' right now or in the future. If there is a need to remove it I would prefer to tackle it later. On Mon, Oct 6, 2014 at 5:13 PM, Kevin Sweeney wrote: > Will 'host' be deprecated as well? > > On Mon, Oct 6, 2014 at 4:30

Re: Build failed in Jenkins: Aurora #620

> to pypi.python.org > twitter.common.python.http: Failed to connect to > https://pypi.python.org/simple/twitter.common.decorators/ within deadline > twitter.common.python.http: Failed to fetch > https://pypi.python.org/simple/twitter.common.decorators/: Could not > reach https://pypi.python.org/simple/twitter.common.decorators/ within > deadline. > Traceback (most recent call last): > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/bin/pex";,> > line 9, in > load_entry_point('twitter.common.python==0.5.9', 'console_scripts', > 'pex')() > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 320, in main > pex_builder = build_pex(args, options) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 284, in build_pex > platform=options.platform) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/resolver.py";,> > line 98, in resolve > raise Unsatisfiable('Cannot satisfy requirements: %s' % > requirement_set[requirement.key]) > twitter.common.python.resolver.Unsatisfiable: Cannot satisfy requirements: > [Requirement.parse('twitter.common.decorators>=0.3.1,<0.4')] > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Removing Aurora's special handling of the 'rack' attribute

and if so explicitly encode a rack limit of 1 in the job's aurora config. ​ -- Zameer Manji

Re: Build failed in Jenkins: Aurora #618

pi.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:218) > at > org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:211) > at > org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:200) > at > org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:579) > at > org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:562) > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80) > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61) > ... 47 more > > > BUILD FAILED > > Total time: 5 mins 2.011 secs > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Re: Build failed in Jenkins: Aurora #608

or actually > working on a fix too. > > On Wed, Oct 1, 2014 at 1:45 PM, Zameer Manji > wrote: > > > Yet another build failure because pants is unable to download a package > > within a deadline. What can we do to make this less flakey? > > > > On Wed, Oc

Re: Build failed in Jenkins: Aurora #613

whl/pants/backend/python/python_chroot.py", > line 187, in dump > conn_timeout=self._conn_timeout) > File > "/home/jenkins/.pex/install/pantsbuild.pants-0.0.23-py2-none-any.whl.af8b963f45e605d010162c9eaf00a47412e75d6e/pantsbuild.pants-0.0.23-py2-none-any.whl/pants/backend/python/resolver.py", > line 100, in resolve_multi > platform=platform) > File > "/home/jenkins/.pex/install/pex-0.7.0-py2.py3-none-any.whl.1528dd6e325a4178651c50d45cba558709e6df75/pex-0.7.0-py2.py3-none-any.whl/pex/resolver.py", > line 110, in resolve > new_requirements.update(requires(highest_package, requirement)) > File > "/home/jenkins/.pex/install/pex-0.7.0-py2.py3-none-any.whl.1528dd6e325a4178651c50d45cba558709e6df75/pex-0.7.0-py2.py3-none-any.whl/pex/resolver.py", > line 84, in requires > raise Untranslateable('Package %s is not translateable.' % package) > Untranslateable: Package SourcePackage(u' > https://pypi.python.org/packages/source/t/twitter.common.lang/twitter.common.lang-0.3.0.tar.gz#md5=3774fb318d8b634a021cccbd81a8fb2f') > is not translateable. > Build operating on top level addresses: set([BuildFileAddress(< > https://builds.apache.org/job/Aurora/ws/src/test/python/BUILD,> all)]) > Failed to run test! > src.test.python.apache.aurora.client.hooks.non_hooked_api > . EXCEPTION > src.test.python.apache.thermos.common.test_pathspec > . SUCCESS > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Re: Proposal: remove v1 client as part of 0.6.0 release

default use of old client than pulling the rug > out > > from people - we can keep the build target and code in place for another > > cycle as a fallback option. > > > > +/-1? > > > > > > [1] https://issues.apache.org/jira/browse/AURORA-775 > > > > > > -=Bill > > > -- Zameer Manji

Re: Build failed in Jenkins: Aurora #608

2ce7b3c9cee89bddec74be62af827 > to /tmp/tmpFH9cuV: Could not reach > https://pypi.python.org/packages/source/t/twitter.common.log/twitter.common.log-0.3.1.tar.gz#md5=9982ce7b3c9cee89bddec74be62af827 > within deadline. > Traceback (most recent call last): > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/bin/pex";,> > line 9, in > load_entry_point('twitter.common.python==0.5.9', 'console_scripts', > 'pex')() > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 320, in main > pex_builder = build_pex(args, options) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/bin/pex.py";,> > line 284, in build_pex > platform=options.platform) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/resolver.py";,> > line 107, in resolve > new_requirements.update(requires(highest_package, requirement)) > File "< > https://builds.apache.org/job/Aurora/ws/build-support/pex.venv/local/lib/python2.7/site-packages/twitter/common/python/resolver.py";,> > line 81, in requires > raise Untranslateable('Package %s is not translateable.' % package) > twitter.common.python.resolver.Untranslateable: Package SourcePackage(u' > https://pypi.python.org/packages/source/t/twitter.common.log/twitter.common.log-0.3.1.tar.gz#md5=9982ce7b3c9cee89bddec74be62af827') > is not translateable. > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Re: Build failed in Jenkins: Aurora #602

/.pex/install/pex-0.7.0-py2.py3-none-any.whl.1528dd6e325a4178651c50d45cba558709e6df75/pex-0.7.0-py2.py3-none-any.whl/pex/resolver.py", > line 110, in resolve > new_requirements.update(requires(highest_package, requirement)) > File > "/home/jenkins/.pex/install/pex-0.7.0-py2.py3-none-any.whl.1528dd6e325a4178651c50d45cba558709e6df75/pex-0.7.0-py2.py3-none-any.whl/pex/resolver.py", > line 84, in requires > raise Untranslateable('Package %s is not translateable.' % package) > Untranslateable: Package SourcePackage(u' > http://argparse.googlecode.com/files/argparse-1.2.1.tar.gz#md5=2fbef8cb61e506c706957ab6e135840c') > is not translateable. > Build operating on top level addresses: set([BuildFileAddress(< > https://builds.apache.org/job/Aurora/ws/src/test/python/BUILD,> all)]) > Failed to run test! > src.test.python.apache.aurora.client.api.updater_util > . SUCCESS > src.test.python.apache.aurora.client.cli.config > . EXCEPTION > src.test.python.apache.aurora.client.hooks.non_hooked_api > . SUCCESS > src.test.python.apache.thermos.common.test_pathspec > . SUCCESS > src.test.python.apache.thermos.monitoring.test_disk > . SUCCESS > Build step 'Execute shell' marked build as failure > Recording test results > -- Zameer Manji

Re: H2 database admin console

directly on the command line, or from a file > referenced on the command line. However, i'm open to ideas i haven't > thought of. > > [1] http://www.h2database.com/html/quickstart.html#h2_console > (ignore the windows/launching instructions - we will embed it as a servlet) > > > -=Bill > -- Zameer Manji

Re: Mesos 12.04 Python2.7 Egg

gt; >> >> It looks like the issue is it was built with a non-standard glibc (if >> I'm following right): >> >> vagrant@192:~/mesos-0.20.0$ /lib/x86_64-linux-gnu/libc.so.6 | grep >> release\ version >> GNU C Library (Ubuntu EGLIBC 2.15-0ubuntu10) stable release version >> 2.15, by Roland McGrath et al. >> >> Any feedback or suggestions would be greatly appreciated! >> >> Thanks, >> Joe >> >> [1] https://reviews.apache.org/r/25208/ >> [2] https://issues.apache.org/jira/browse/AURORA-674 >> > > > > > -- Zameer Manji

Removing default 'rack' constraint

7;rack' attribute set. Does anyone object to this? [1]: https://github.com/apache/incubator-aurora/blob/900a2b299347c71f7c7601a3a3d0a3f0f0afbcb7/src/main/java/org/apache/aurora/scheduler/configuration/ConfigurationManager.java#L142-L153 -- Zameer Manji

Re: Unable to assign Jira issue to myself?

I think Chris Lambert needs to give you some some sort of extra permission. On Thu, Sep 4, 2014 at 3:58 PM, Joshua Cohen wrote: > Anyone know if I need to get a permission in Jira in order to do this? > > Thanks! > > Joshua > -- Zameer Manji

Fetching and Caching Binaries from HDFS

brief explanation on how it works can be found in this gist: https://gist.github.com/zmanji/f41df77510ef9d00265a. I hope it serves as a good example on how this problem can be mitigated. -- Zameer Manji

Re: Instruction on setting up dev environment on my Mac machine

wap_mb 8063 > > system_load_avg 2.22 > > task_queries_all 45 > > task_queries_by_id 3668 > > task_queries_by_job 183 > > task_schedule_attempt_events 135 > > task_schedule_attempt_events_per_sec 0.0 > > task_schedule_attempt_nanos_per_event 0.0 > > task_schedule_attempt_nanos_total 6289005821 > > task_schedule_attempt_nanos_total_per_sec 0.0 > > task_store_ASSIGNED 0 > > task_store_FAILED 0 > > task_store_FINISHED 200 > > task_store_INIT 0 > > task_store_KILLED 0 > > task_store_KILLING 0 > > task_store_LOST 0 > > task_store_PENDING 1 > > task_store_PREEMPTING 0 > > task_store_RESTARTING 0 > > task_store_RUNNING 0 > > task_store_STARTING 0 > > task_store_THROTTLED 0 > > task_store_UNKNOWN 0 > > timed_out_tasks 0 > > timeout_queue_size 338 > > transient_states 0 > > uncaught_exceptions 0 > > variable_scrape_events 38778 > > variable_scrape_events_per_sec 1.103021061324 > > variable_scrape_micros_per_event 455.0001369564521 > > variable_scrape_micros_total 18809481 > > variable_scrape_micros_total_per_sec 455.00482441615327 > > work_queue_depth 0 > > write_lock_wait_nanos 13138744 > > > > > > > > > > On Fri, Dec 20, 2013 at 9:07 AM, Maxim Khutornenko > >wrote: > > > > > Hi Yingbo, > > > > > > Do you mind sharing your .aurora file? Perhaps your are requesting > > > Resources or Constraints that are infeasible for your local setup to > > > satisfy? > > > > > > Also, you might want to check that your scheduler is receiving offers > > from > > > mesos master. You could check your scheduler log file to see if any > > offers > > > are coming. Alternatively, you might want to look at > > > "scheduler_resource_offers" stat exposed by the scheduler /vars > endpoint > > > (http:///vars). > > > > > > Thanks, > > > Maxim > > > > > > > > > > > > On Dec 19, 2013, at 11:20 PM, Yingbo Wang wrote: > > > > > > > hi, > > > >Hope you guys have a fun night at city hall. > > > >While you might be drunk, can anyone help me a little bit on > setting > > > up > > > > the local dev environment to debug aurora ? > > > > My current set up. > > > > Machine A: 64bit ubuntu server running mesos-master, > > > > Machine B: 64bit ubuntu server running mesos-slave, thermo > > > > observer server; > > > > Machine C: 32bit ubuntu server running zookeeper. > > > > Machine D: Mac air for developing aurora. > > > > > > > > I tried to run aurora-scheduler on Machine A and also created a > > > hello > > > > job from machine A. the job was submitted successfully. however the > job > > > > keeps staying at "PENDING" status. i checked thermo observer from > port > > > > 1336, it says "No matching hosts". > > > > > > > >I spent a couple of hours and still can't figure out the > reason > > so > > > > I decided to settup the dev environment on my Mac so that I can trace > > the > > > > error in IntelliJ. Can someone give me some hint on that? I am not > > quite > > > > familiar with IntelliJ and java. > > > > > > > > > > > > > > > > best > > > > Yingbo > > > > > > > > > -- Zameer Manji

Re: Review Request 16355: Fixing checkstyle for tests.

- > > (Updated Dec. 18, 2013, 2:11 p.m.) > > > Review request for Aurora, Bill Farner and Zameer Manji. > > > Repository: aurora > > > Description > --- > > Adding checkstyle for tests. > > > Diffs > - > > build.gra

Re: Review Request 16355: Fixing checkstyle for tests.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16355/#review30639 --- Ship it! Ship It! - Zameer Manji On Dec. 18, 2013, 12:39 p.m

[jira] [Resolved] (AURORA-11) Aurora preemptor should reserve resources feed for PENDING task.

[ https://issues.apache.org/jira/browse/AURORA-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zameer Manji resolved AURORA-11. Resolution: Fixed This was committed from the review to master by [~wfarner]. > Aurora preemp

Re: Review Request 16353: Skip building the Apache Thrift 0.9.1 tests

> On Dec. 18, 2013, 11:26 a.m., Bill Farner wrote: > > build-support/thrift/Makefile, line 27 > > > > > > I'm probably ignorant, but --without-java seems like it would cut the > > compiler support we need. Is it doing

Re: Review Request 16344: Wholesale dependency updates.

more headaches down the road. - Zameer Manji On Dec. 17, 2013, 10:06 p.m., Bill Farner wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.a

Re: Review Request 16343: Add 'about' and 'versions' gradle plugins.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16343/#review30625 --- Ship it! Ship It! - Zameer Manji On Dec. 17, 2013, 9:36 p.m

Re: Review Request 16353: Skip building the Apache Thrift 0.9.1 tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16353/#review30624 --- Ship it! LGTM - Zameer Manji On Dec. 18, 2013, 9:19 a.m., Jake

Re: Review Request 16232: Add offer reservations to preemption flow

a747f2b1ecbad7263931aeec3b12711096d2469d src/test/java/com/twitter/aurora/scheduler/state/PubsubTestUtil.java f9d7fb64728008d0ea6eb424283b58e956e1d50a Diff: https://reviews.apache.org/r/16232/diff/ Testing --- ./gradlew clean build Thanks, Zameer Manji

Re: Review Request 16334: Bumping up snapshot version to 0.3.0

you should just bump it without a review. I think Kevin's script will do that for us though. - Zameer Manji On Dec. 17, 2013, 3:48 p.m., Maxim Khutornenko wrote: > > --- > This is an automatically generated e-mail. T

Re: Review Request 16232: Add offer reservations to preemption flow

be in place to avoid exposing this, can you > > try to make it private? This has the added benefit of sidestepping > > exposing TaskSchedulerImpl in AsyncModule. > > Zameer Manji wrote: > It just makes the tests too hard to read IMHO. Even creating test helper > me

Re: Review Request 16232: Add offer reservations to preemption flow

a747f2b1ecbad7263931aeec3b12711096d2469d src/test/java/com/twitter/aurora/scheduler/state/PubsubTestUtil.java f9d7fb64728008d0ea6eb424283b58e956e1d50a Diff: https://reviews.apache.org/r/16232/diff/ Testing --- ./gradlew clean build Thanks, Zameer Manji

Re: how to copy a package to thermo's working directory and run it

You need to fetch your package/binary into the sandbox. A sample aurora config could look like this: hello = Process( name = 'hello', cmdline = "./hello") fetch_hello = Process( name = 'fetch_hello', cmdline = "wget http://packages.local/hello && chmod +x ./hello") task = SequentialTask(

[jira] [Assigned] (AURORA-12) thermos.py trying to len() a generator

[ https://issues.apache.org/jira/browse/AURORA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zameer Manji reassigned AURORA-12: -- Assignee: brian wickman I'm not sure if this is a bug, but I am assigning this to Bria

Re: Review Request 16232: Add offer reservations to preemption flow

.java a747f2b1ecbad7263931aeec3b12711096d2469d src/test/java/com/twitter/aurora/scheduler/state/PubsubTestUtil.java f9d7fb64728008d0ea6eb424283b58e956e1d50a Diff: https://reviews.apache.org/r/16232/diff/ Testing --- ./gradlew clean build Thanks, Zameer Manji

Re: Review Request 16232: Add offer reservations to preemption flow

, 2013, 3:23 p.m., Bill Farner wrote: > > src/main/java/com/twitter/aurora/scheduler/async/TaskScheduler.java, line > > 249 > > <https://reviews.apache.org/r/16232/diff/5/?file=398504#file398504line249> > > > > s/this.// done. - Zameer --- This is an aut

Re: Review Request 16232: Add offer reservations to preemption flow

a747f2b1ecbad7263931aeec3b12711096d2469d src/test/java/com/twitter/aurora/scheduler/state/PubsubTestUtil.java f9d7fb64728008d0ea6eb424283b58e956e1d50a Diff: https://reviews.apache.org/r/16232/diff/ Testing --- ./gradlew clean build Thanks, Zameer Manji

Re: Review Request 16232: Add offer reservations to preemption flow

you've exposed the key you're binding > > against (i suspect that's _why_ you exposed it), but can you confirm that a > > test fails if this is not wired properly? > > Zameer Manji wrote: > I ran into some problems doing this, lets talk offline. The current dif

Re: Review Request 16232: Add offer reservations to preemption flow

performance: check if the old state was PENDING. > > This way you do the O(n) map walk far less frequently. > > Zameer Manji wrote: > this breaks my tests for some reason, punting on this. > > Bill Farner wrote: > Do you really think i'll accept that response?

Re: Review Request 16232: Add offer reservations to preemption flow

a747f2b1ecbad7263931aeec3b12711096d2469d src/test/java/com/twitter/aurora/scheduler/state/PubsubTestUtil.java f9d7fb64728008d0ea6eb424283b58e956e1d50a Diff: https://reviews.apache.org/r/16232/diff/ Testing --- ./gradlew clean build Thanks, Zameer Manji

Re: Review Request 16232: Add offer reservations to preemption flow

performance: check if the old state was PENDING. > > This way you do the O(n) map walk far less frequently. > > Zameer Manji wrote: > this breaks my tests for some reason, punting on this. > > Bill Farner wrote: > Do you really think i'll accept that response?

Re: Review Request 16232: Add offer reservations to preemption flow

you've exposed the key you're binding > > against (i suspect that's _why_ you exposed it), but can you confirm that a > > test fails if this is not wired properly? > > Zameer Manji wrote: > I ran into some problems doing this, lets talk offline. The current

Re: Review Request 16232: Add offer reservations to preemption flow

performance: check if the old state was PENDING. > > This way you do the O(n) map walk far less frequently. > > Zameer Manji wrote: > this breaks my tests for some reason, punting on this. > > Bill Farner wrote: > Do you really think i'll acc

Re: Review Request 16267: Adding a script to run an isolated scheduler.

> On Dec. 13, 2013, 5:30 p.m., Bill Farner wrote: > > I would much rather see further investment in local runs through vagrant. > > Have you considered focusing there instead? > > Suman Karumuri wrote: > Yes, I have considered it and found vagrant to be too slow for iterative > edit-build

Re: Tagging process

h the tag was created on). > > What does everyone think of this process? > -- > Kevin Sweeney > @kts > -- Zameer Manji

Re: Review Request 16232: Add offer reservations to preemption flow

.java a747f2b1ecbad7263931aeec3b12711096d2469d src/test/java/com/twitter/aurora/scheduler/state/PubsubTestUtil.java f9d7fb64728008d0ea6eb424283b58e956e1d50a Diff: https://reviews.apache.org/r/16232/diff/ Testing --- ./gradlew clean build Thanks, Zameer Manji

Re: Review Request 16232: Add offer reservations to preemption flow

ps://reviews.apache.org/r/16232/diff/2/?file=397891#file397891line246> > > > > Looks like you'd benefit in test readability by introducing a helper > > function: > > > > private Capture>> > > expectLaunchAttempt(b

Re: Review Request 16232: Add offer reservations to preemption flow

re gap here — if the task _is_ assigned, the > > reservation should be cleared so we can promptly schedule others. It may > > be tempting to call the O(n) invalidateTask(), but i suggest adding the > > O(1) invalidateSlave(). > > > > Please write a failin

Re: Review Request 16232: Add offer reservations to preemption flow

/TaskSchedulerTest.java a747f2b1ecbad7263931aeec3b12711096d2469d src/test/java/com/twitter/aurora/scheduler/state/PubsubTestUtil.java f9d7fb64728008d0ea6eb424283b58e956e1d50a Diff: https://reviews.apache.org/r/16232/diff/ Testing --- ./gradlew clean build Thanks, Zameer Manji

Re: Review Request 16232: Add offer reservations to preemption flow

eduler.java, line > > 146 > > <https://reviews.apache.org/r/16232/diff/1/?file=397101#file397101line146> > > > > There's a bit of a feature gap here — if the task _is_ assigned, the > > reservation should be cleared so we can pr

Re: Review Request 16257: Fix gradle to include same version as artifact in generated distribution tarball

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16257/#review30378 --- Ship it! Ship It! - Zameer Manji On Dec. 13, 2013, 1:49 p.m

[jira] [Resolved] (AURORA-9) Maintenance servlet should expose information about DRAINED hosts

[ https://issues.apache.org/jira/browse/AURORA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zameer Manji resolved AURORA-9. --- Resolution: Fixed My patch was committed by [~wfarner]. Marking as fixed. > Maintenance serv

Re: Review Request 16220: Output all states in maintenance endpoint.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16220/#review30329 --- Please commit my code. - Zameer Manji On Dec. 12, 2013, 5:49 p.m

Re: Review Request 16220: Output all states in maintenance endpoint.

/MaintenanceControllerImplTest.java 8acb716c733ec9d3cc3b1ec74c85f958082ae139 Diff: https://reviews.apache.org/r/16220/diff/ Testing --- ./gradlew clean build Thanks, Zameer Manji

Re: Review Request 16220: Output all states in maintenance endpoint.

e previous line done. - Zameer --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16220/#review30324 --- On Dec. 12, 20

Re: Review Request 16220: Output all states in maintenance endpoint.

state/MaintenanceControllerImplTest.java 8acb716c733ec9d3cc3b1ec74c85f958082ae139 Diff: https://reviews.apache.org/r/16220/diff/ Testing --- ./gradlew clean build Thanks, Zameer Manji

Re: Review Request 16220: Output all states in maintenance endpoint.

291> > > > > please kindly give intellij a smack and revert done. - Zameer --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/16220/#review30316

[jira] [Commented] (AURORA-11) Aurora preemptor should reserve resources feed for PENDING task.

[ https://issues.apache.org/jira/browse/AURORA-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847013#comment-13847013 ] Zameer Manji commented on AURORA-11: Review: https://reviews.apache.org/r/1

[jira] [Commented] (AURORA-9) Maintenance servlet should expose information about DRAINED hosts

[ https://issues.apache.org/jira/browse/AURORA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847014#comment-13847014 ] Zameer Manji commented on AURORA-9: --- Review: https://reviews.apache.org/r/1

Review Request 16232: Add offer reservations to preemption flow

--- ./gradlew clean build Thanks, Zameer Manji

[jira] [Created] (AURORA-11) Aurora preemptor should reserve resources feed for PENDING task.

Zameer Manji created AURORA-11: -- Summary: Aurora preemptor should reserve resources feed for PENDING task. Key: AURORA-11 URL: https://issues.apache.org/jira/browse/AURORA-11 Project: Aurora

  1   2   >