mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anindya Sinha <anindya_si...@apple.com>
Subject Re: Review Request 57815: Added `deactivated_roles` field in `FrameworkInfo`.
Date Fri, 05 May 2017 00:34:22 GMT


> On April 17, 2017, 6:28 p.m., Vinod Kone wrote:
> > include/mesos/scheduler/scheduler.proto
> > Lines 249-250 (original), 249-250 (patched)
> > <https://reviews.apache.org/r/57815/diff/1-3/?file=1670985#file1670985line249>
> >
> >     Hmm, I was hoping that we could re-use the `Call::Suppress` message here instead
of re-defining it. That way any changes to suppress would be in sync.
> 
> Anindya Sinha wrote:
>     Currently, `Call::Suppress` is:
>     ```
>       message Suppress {
>         optional string role = 1;
>       }
>     ```
>     
>     So, the `SUPPRESS` call currently allows suppressing offers for a framework on a
per-role basis (or all roles if `role` is not set). Since we now support multiple roles for
a frameework, and if we want to suppress offers for a subset of roles at the time of `SUBSCRIBE`,
using `Call::Suppress` would not satisfy that use case. It would only satisfy suppressing
for all roles (i.e. `Suppress::role` is not set) or for a specific role.
>     
>     Is there any plans of extending `SUPPRESS` to suppress offers for a subset of roles
(>0, and < all roles) in a single call? Do you think we should consider that also?
>     
>     One such approach could be to have the following:
>     ```
>       message Suppress {
>         repeated string roles = 1;
>       }
>     
>       optional Suppress suppress;
>     ```
>     
>     If suppress is not set, then we do not suppress for any roles. Otherwise, we suppress
for the set of roles specified in `suppress.roles`. If `suppress` is set but `suppress.roles`
is empty, we suppress for all roles of the framework.
>     
>     Thoughts?

So based on discussion in the Slack channel, this modified review chain does the following:

1. Add `repeated string deactivated_roles` to `FrameworkInfo` which represents a subset of
roles which are deactivated. Offers pertaining to the deactivated roles shall not be sent
out.
2. `SUPPRESS` and `REVIVE` calls will toggle the (de)activation mode of the roles.
3. Allocator's `activateFramework()` call will activate all roles of the framework which are
not in `FrameworkInfo::deactivated+roles`. Similarly, in `deactivateFramework()` call will
deactivate all roles that are not deactivated already.


- Anindya


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


On May 5, 2017, 12:34 a.m., Anindya Sinha wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57815/
> -----------------------------------------------------------
> 
> (Updated May 5, 2017, 12:34 a.m.)
> 
> 
> Review request for mesos, James Peach, Vinod Kone, and Jiang Yan Xu.
> 
> 
> Bugs: MESOS-7015
>     https://issues.apache.org/jira/browse/MESOS-7015
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> This field is a subset of roles the framework registered as for which
> the framework does not want any resources offere to.
> 
> 
> Diffs
> -----
> 
>   include/mesos/mesos.proto 1935f47a52840f6b395ecb2d28296666551fa691 
>   include/mesos/v1/mesos.proto c7f0bec5c96f2f41344d4261d0696f9fe0421db7 
> 
> 
> Diff: https://reviews.apache.org/r/57815/diff/4/
> 
> 
> Testing
> -------
> 
> All tests passed.
> 
> 
> Thanks,
> 
> Anindya Sinha
> 
>


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