You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joerg Schad (JIRA)" <ji...@apache.org> on 2016/07/05 15:06:11 UTC
[jira] [Comment Edited] (MESOS-5757) Authorize orphaned tasks
[ https://issues.apache.org/jira/browse/MESOS-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361699#comment-15361699 ]
Joerg Schad edited comment on MESOS-5757 at 7/5/16 3:06 PM:
------------------------------------------------------------
Extended install() to support 7 arguments.
https://reviews.apache.org/r/49606/
Added support for recovered frameworks.
https://reviews.apache.org/r/49607/
Added filtering for orphaned tasks in /state endpoint.
https://reviews.apache.org/r/49609/
Test
https://reviews.apache.org/r/49639/
was (Author: js84):
Extended install() to support 7 arguments.
https://reviews.apache.org/r/49606/
Added support for recovered frameworks.
https://reviews.apache.org/r/49607/
Added filtering for orphaned tasks in /state endpoint.
https://reviews.apache.org/r/49609/
(test are almost ready and will follow tomorrow)
> Authorize orphaned tasks
> ------------------------
>
> Key: MESOS-5757
> URL: https://issues.apache.org/jira/browse/MESOS-5757
> Project: Mesos
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.0
> Reporter: Vinod Kone
> Assignee: Joerg Schad
> Labels: mesosphere, security
> Fix For: 1.0.0
>
>
> Currently, orphaned tasks are not filtered (i.e., using authorization) when a request is made to /state endpoint. This is inconsistent (and unexpected) with how we filter un-orphaned tasks.
> This is tricky because master and hence the authorizer do not have FrameworkInfos for these orphaned tasks, until after the corresponding frameworks re-register.
> One option is for the agent to include FrameworkInfos of all its tasks and executors in its re-registration message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)