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




src/resource_provider/manager.cpp
Lines 270-274 (patched)
<https://reviews.apache.org/r/61181/#comment257384>

    That makes me think if it's easier to always rely on `Update` to report the 
total resources of a resource provider. `Subscribe` will just register with the 
manager with `ResourceProviderInfo`. The resource provider will send an update 
to the manager after subscription is successful?
    
    In that way, we don't have to worry about the ID injection in the manager 
any more (we do need to do validation!)



src/resource_provider/manager.cpp
Lines 271 (patched)
<https://reviews.apache.org/r/61181/#comment257383>

    Use `foreach` to be consistent with other files?


- Jie Yu


On July 27, 2017, 2:49 p.m., Benjamin Bannier wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61181/
> -----------------------------------------------------------
> 
> (Updated July 27, 2017, 2:49 p.m.)
> 
> 
> Review request for mesos, Jie Yu and Jan Schlicht.
> 
> 
> Bugs: MESOS-7837
>     https://issues.apache.org/jira/browse/MESOS-7837
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> In order to be able to always communicate the aggregated total
> resources available on all subscribed resource providers, a resource
> provider manager needs to keep track of the resources of all
> subscribed resource providers. This commit adds a field for that the
> manager's internal data structures for that purpose.
> 
> To make assigned 'ResourceProviderID's opaque to users of managers, the
> manager assigns provider ids to all resources added.
> 
> 
> Diffs
> -----
> 
>   src/resource_provider/manager.cpp 44e1576d4462295d404429d51682134306047462 
> 
> 
> Diff: https://reviews.apache.org/r/61181/diff/1/
> 
> 
> Testing
> -------
> 
> Tested as part of https://reviews.apache.org/r/61182/.
> 
> 
> Thanks,
> 
> Benjamin Bannier
> 
>

Reply via email to