[ 
https://issues.apache.org/jira/browse/MESOS-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858772#comment-15858772
 ] 

Guangya Liu commented on MESOS-6638:
------------------------------------

{code}
commit 748675352964ccfbf4e45d6cd7b4b4cacb1c58bf
Author: Guangya Liu gy...@apache.org
Date:   Thu Feb 9 08:28:43 2017 +0800

Updated Suppress and Revive proto to support per role.

Updated Suppress and Revive proto to support per role.

Review: https://reviews.apache.org/r/56327/

commit 348c06bb0f06c3229ba897fc7fd568473c5bd11b
Author: Guangya Liu gy...@apache.org
Date:   Thu Feb 9 08:30:21 2017 +0800

Augmented master `Suppress` API to accept `Call::Suppress`.

Augmented master `Suppress` API to accept `Call::Suppress`.

Review: https://reviews.apache.org/r/56328/
{code}

> Update Suppress and Revive to be per-role.
> ------------------------------------------
>
>                 Key: MESOS-6638
>                 URL: https://issues.apache.org/jira/browse/MESOS-6638
>             Project: Mesos
>          Issue Type: Task
>          Components: framework api
>            Reporter: Benjamin Mahler
>            Assignee: Guangya Liu
>
> The {{SUPPRESS}} and {{REVIVE}} calls need to be updated to be per-role. I.e. 
> Include {{Revive.role}} and {{Suppress.role}} fields, indicating which role 
> the operation is being applied to.
> {{Revive}} and {{Suppress}} messages do not currently exist, so these need to 
> be added. To support the old-style schedulers, we will make the role fields 
> optional.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to