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

Guangya Liu edited comment on MESOS-6638 at 2/7/17 12:44 PM:
-------------------------------------------------------------

https://reviews.apache.org/r/56327/ Updated Suppress and Revive proto to 
support per role.
https://reviews.apache.org/r/56328/ Augmented master `Suppress` API to accept 
`Call::Suppress`.
https://reviews.apache.org/r/56330/ Enabled suppress offer per role.
https://reviews.apache.org/r/56371/ Enabled `ReviveOffersMessage` support 
revive per role.
https://reviews.apache.org/r/56373/ Augmented master `Revive` API to accept 
`Call::Revive`.
https://reviews.apache.org/r/56374/ Enabled revive offer per role.
https://reviews.apache.org/r/56376/ Updated allocator test to support create 
multi role framework.
https://reviews.apache.org/r/56378/ Added test case for suppress and revive 
with multi role framework.


was (Author: gyliu):
https://reviews.apache.org/r/56327/ Updated Suppress and Revive proto to 
support per role.
https://reviews.apache.org/r/56328/ Augmented master `Suppress` API to accept 
`Call::Suppress`.
https://reviews.apache.org/r/56330/ Enabled suppress offer per role.

> 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