[
https://issues.apache.org/jira/browse/MESOS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174099#comment-15174099
]
Connor Doyle commented on MESOS-4816:
-------------------------------------
Hi [~gyliu],
I agree the optional task info argument in the comment is awkward, but a list
sounds pretty good. Existing isolators could continue to look only at the
aggregated resources.
This question came up during the isolation WG meeting last week. I and others
have used this workaround while prototyping isolators for networking, but in
general people tend to pass information to isolators via task labels before
concepts become first-class in ContainerInfo or elsewhere. [~jamespeach] and
[~idownes] may be able to fill in more details.
> Expose TaskInfo to Isolators
> ----------------------------
>
> Key: MESOS-4816
> URL: https://issues.apache.org/jira/browse/MESOS-4816
> Project: Mesos
> Issue Type: Improvement
> Components: modules, slave
> Reporter: Connor Doyle
>
> Authors of custom isolator modules frequently require access to the TaskInfo
> in order to read custom metadata in task labels.
> Currently, it's possible to link containers to tasks within a module by
> implementing both an isolator and the {{slaveRunTaskLabelDecorator}} hook,
> and maintaining a shared map of containers to tasks. This way works, but
> adds unnecessary complexity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
