Hi Vinod:
Yeah, `CLEAR_FILTERS` sounds good.
UNSUPPRESS should be used whenever currently suppressed framework wants to
resume getting offers after a previous SUPPRESS call.
As for `CLEAR_FILTERS`, the short (but not very useful) suggestion is to
call it whenever the framework wants to clear
See my comments inline.
On Mon, Dec 3, 2018 at 5:43 PM Vinod Kone wrote:
> Thanks Meng for the explanation.
>
> I imagine most frameworks do not remember what stuff they filtered much
> less figure out how previously filtered stuff can satisfy new operations.
> That sounds complicated!
>
Thanks Meng for the explanation.
I imagine most frameworks do not remember what stuff they filtered much
less figure out how previously filtered stuff can satisfy new operations.
That sounds complicated!
But I like your example. So a suggestion we could make to frameworks could
be to use
On Thu, Nov 29, 2018 at 1:22 AM Vinod Kone wrote:
> Cameron and Michal: I would love to understand your motivations and use
> cases for a k8s Mesos framework in a bit more detail. Looks like you are
> willing to rewrite your existing app definitions into k8s API spec. At this
> point, why are
Hi:
tl;dr: We are proposing to add two new V1 scheduler APIs: unsuppress and
clear_filter in order to decouple the dual-semantics of the current revive
call.
As pointed out in the Mesos framework scalability guide
Hi Meng,
What would be the recommendation for framework authors on when to use
UNSUPPRESS vs CLEAR_FILTER?
Also, should it CLEAR_FILTERS instead of CLEAR_FILTER?
On Mon, Dec 3, 2018 at 2:26 PM Meng Zhu wrote:
> Hi:
>
> tl;dr: We are proposing to add two new V1 scheduler APIs: unsuppress and
>
