[
https://issues.apache.org/jira/browse/MESOS-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881367#comment-15881367
]
Benjamin Mahler commented on MESOS-7158:
----------------------------------------
This includes the change to the endpoints and the agent test:
{noformat}
commit 2ee98b040927ec80371f1850717fe4add91b8b77
Author: Jay Guo <[email protected]>
Date: Thu Feb 23 13:26:43 2017 -0800
Added allocation role to tasks/executors in v0 /state API.
Added allocation role of tasks/executors to the /state v0 API. Unlike
v1 API where allocation_info is nested in each one of resources, we
add that information at task/executor level for v0 API since the JSON
format for resources cannot be extended to support allocation role.
Note that resources of one task/executor are guaranteed to have same
allocation role.
Review: https://reviews.apache.org/r/56938/
{noformat}
[~guoger] Leaving this open until we have the master's state endpoint test
updated as well.
> Add `role` to task/executor to indicate allocation role of their resources
> --------------------------------------------------------------------------
>
> Key: MESOS-7158
> URL: https://issues.apache.org/jira/browse/MESOS-7158
> Project: Mesos
> Issue Type: Bug
> Reporter: Jay Guo
> Assignee: Jay Guo
>
> As we added {{allocation_info}} to {{resource}}, v1 API inherently shows
> those information when {{getState}} is invoked. However, we need to
> explicitly add {{allocation_info}} to {{/state}} v0 API. Hence, we need to
> add a {{role}} section to {{task}}/{{executor}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
