[jira] [Commented] (MESOS-6638) Update Suppress and Revive to be per-role.

["James DeFelice (JIRA)" <ji...@apache.org>]

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

James DeFelice commented on MESOS-6638:
---------------------------------------

https://github.com/mesos/mesos-go/pull/304#issuecomment-311060962

SUPPRESS and REVIVE were already members of the scheduler Call.Type prior to 1.2; now that they have corresponding message object types, it's unclear if the message objects are actually required if there's no role to set. The docs are unclear on this

> 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: scheduler api
>            Reporter: Benjamin Mahler
>            Assignee: Guangya Liu
>             Fix For: 1.2.0
>
>
> 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.4.14#64029)