aurora-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Erb <s...@apache.org>
Subject Re: Review Request 51807: Introduce a flag to treat RAM as a revocable resources
Date Mon, 12 Sep 2016 21:35:12 GMT


> On Sept. 12, 2016, 9:31 p.m., Maxim Khutornenko wrote:
> > src/main/java/org/apache/aurora/scheduler/resources/ResourceType.java, line 75
> > <https://reviews.apache.org/r/51807/diff/1/?file=1496738#file1496738line75>
> >
> >     Would be great to have a e2e test when this functionality is available in Mesos.
Perhaps drop a TODO here?
> 
> Stephan Erb wrote:
>     Acutally, it would work in Mesos out of the box even today. All we have to do is
adapt our Mesos config to also pass along memory resources https://github.com/apache/aurora/blob/master/examples/vagrant/mesos_config/etc_mesos-slave/modules#L8.
>     
>     I didn't do it because I felt like it wouldn't add any additional test coverage,
now that the entire resource handling within Aurora is generic.

Additional info: We already have an e2e test using revocable CPU resources.


- Stephan


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51807/#review148563
-----------------------------------------------------------


On Sept. 12, 2016, 3:38 p.m., Stephan Erb wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51807/
> -----------------------------------------------------------
> 
> (Updated Sept. 12, 2016, 3:38 p.m.)
> 
> 
> Review request for Aurora and Maxim Khutornenko.
> 
> 
> Repository: aurora
> 
> 
> Description
> -------
> 
> We plan to open source a very simple Mesos ResourceEstimator and QosController that supports
RAM and CPU oversubscription (ETA ~2 weeks). We have been using it internally with a patched
Aurora version where the hardcoded `isMesosRevocable` flag of RAM has been set to `true`.
This patch makes this behaviour configurable.
> 
> 
> Diffs
> -----
> 
>   RELEASE-NOTES.md bbf7198dc7ce53bb02a1bc59f75a661e23472913 
>   docs/features/resource-isolation.md 01c5b407a4964e89741d0f6c72d04ab5dc4c2f87 
>   docs/operations/configuration.md 90dde574ce517355d2d6045a5ab036c1a3838882 
>   docs/reference/scheduler-configuration.md 87d2cded0780ffa34884b52cc049c6a0ad808f0a

>   src/main/java/org/apache/aurora/scheduler/resources/ResourceSettings.java PRE-CREATION

>   src/main/java/org/apache/aurora/scheduler/resources/ResourceType.java 4c102a3d4c4bdd27a1d0536b689acd6257e77788

> 
> Diff: https://reviews.apache.org/r/51807/diff/
> 
> 
> Testing
> -------
> 
> ./gradlew -Pq build
> 
> 
> Thanks,
> 
> Stephan Erb
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message