> On June 6, 2013, 5:44 p.m., Benjamin Hindman wrote:
> >
> 
> Benjamin Hindman wrote:
>     I didn't give a 'Ship-It' because I think we need to briefly chat naming 
> and existing users ...

Yep, I made these changes on the assumption that we haven't yet released 
0.12.0. Once we do however, and if this isn't patched in, it will require 
action on behalf of users if they depend on the names. I'm ok keeping things 
the same, at the cost of having less nice names.


> On June 6, 2013, 5:44 p.m., Benjamin Hindman wrote:
> > include/mesos/mesos.proto, lines 272-276
> > <https://reviews.apache.org/r/11641/diff/1/?file=300801#file300801line272>
> >
> >     What's the different between "CPUs used" and "CPU resources allocated" 
> > ... if they are the same thing we should use the same language.
> >     
> >     Also, as long as we are cleaning up the stats names, it would be nice 
> > if the resource "name" matched the resource itself, i.e., s/cpu/cpus, 
> > s/memory/mem, etc. But this might be too much to ask for given existing 
> > users. (I could see cpu_user_time_secs and cpu_system_time_secs being just 
> > 'cpu' though). Thoughts?

I'll correct the descriptions to use the same language ("number of CPUs").

As for the latter comment, it boils down to whether we're ok with changing 
these names. If so, then 'mem' and 'cpus' might be nicer for consistency.


- Ben


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


On June 4, 2013, 10:14 p.m., Ben Mahler wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/11641/
> -----------------------------------------------------------
> 
> (Updated June 4, 2013, 10:14 p.m.)
> 
> 
> Review request for mesos, Benjamin Hindman and Vinod Kone.
> 
> 
> Description
> -------
> 
> This adds allocation information into the resource usage endpoint.
> This also splits up "cpu_time" into "cpu_system_time_secs" and 
> "cpu_user_time_secs".
> 
> 
> This addresses bugs MESOS-432 and MESOS-472.
>     https://issues.apache.org/jira/browse/MESOS-432
>     https://issues.apache.org/jira/browse/MESOS-472
> 
> 
> Diffs
> -----
> 
>   include/mesos/mesos.proto ece6559e4c8a3e943833be27c5fb0f02910d2d20 
>   src/slave/cgroups_isolator.hpp 7b8270d0b0f94a71da12bc123d39b44c40c3f7ed 
>   src/slave/cgroups_isolator.cpp 9b3a3a5dfec27a119fdd47a88f016e21470eb88d 
>   src/slave/monitor.cpp 5de1c15c78194ab9ec49c30b9abfb9a6d3e16344 
>   src/slave/process_isolator.hpp 9875f4a6e8e109e31ad390fbd7a84d03ad747190 
>   src/slave/process_isolator.cpp d4f7b7603452e7226189899aca7e3c94e537829f 
>   src/tests/isolator_tests.cpp aae8b2f78d6a2d5e4e3f31cce4380ef5197f4f5d 
>   src/tests/monitor_tests.cpp 53920a0d7bdc69071b64c8d315c008d501e27777 
> 
> Diff: https://reviews.apache.org/r/11641/diff/
> 
> 
> Testing
> -------
> 
> Updated the tests, make check on OSX and Linux.
> 
> 
> Thanks,
> 
> Ben Mahler
> 
>

Reply via email to