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

Ship it!



src/master/validation.cpp
<https://reviews.apache.org/r/33865/#comment135011>

    Do you want to stringify the resource for the error message here too?



src/tests/resources_tests.cpp
<https://reviews.apache.org/r/33865/#comment135010>

    Had to read the containment tests twice; maybe introduce the tests with a 
small comment on what you are testing?
    
    I see that you grabbed the tests from above, but would still be helpful 
with an intro.


- Niklas Nielsen


On May 14, 2015, 4:57 p.m., Vinod Kone wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/33865/
> -----------------------------------------------------------
> 
> (Updated May 14, 2015, 4:57 p.m.)
> 
> 
> Review request for mesos, Jie Yu, Joris Van Remoortere, and Niklas Nielsen.
> 
> 
> Bugs: MESOS-2691
>     https://issues.apache.org/jira/browse/MESOS-2691
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> RevocableInfo currently supports OVERSUBSCRIBED resources. In the future it 
> can be easily extended to use other types of revocable reosurces (e.g., 
> resources allocated to other roles).
> 
> Disabled the ability to use revocable resources for reservation or 
> persistence because the semantics seem weird. We can enable it in the future 
> if there is a use case for that.
> 
> 
> Diffs
> -----
> 
>   include/mesos/mesos.proto 15f55a3c54be3475e77d561f106e00ea6e53c2fa 
>   src/common/resources.cpp 843a06d6c4d3e9ff0d1665360bae7c57bcfecb83 
>   src/master/validation.cpp c3e96ae0e684f3f365e9aa365bccc953d32b0452 
>   src/tests/resources_tests.cpp a7ec59ea217ad71f7d1e93ca6039d5b2491b3237 
> 
> Diff: https://reviews.apache.org/r/33865/diff/
> 
> 
> Testing
> -------
> 
> make check
> 
> 
> Thanks,
> 
> Vinod Kone
> 
>

Reply via email to