Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Mon, 14 Apr 2014 07:49:16 +0000 (UTC)
From: "Adam B (JIRA)" <jira@apache.org>
To: dev@mesos.apache.org
Message-ID: <JIRA.12703230.1395677102963.108923.1397461756966@arcas>
In-Reply-To: <JIRA.12703230.1395677102963@arcas>
References: <JIRA.12703230.1395677102963@arcas>
Subject: [jira] [Commented] (MESOS-1141) Add a 'user' field to CommandInfo.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/MESOS-1141?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1396=
8145#comment-13968145 ]=20

Adam B commented on MESOS-1141:
-------------------------------

M=C3=A1rton provided a proof-of-concept that we will clean up and post for =
review soon.

> Add a 'user' field to CommandInfo.
> ----------------------------------
>
>                 Key: MESOS-1141
>                 URL: https://issues.apache.org/jira/browse/MESOS-1141
>             Project: Mesos
>          Issue Type: Improvement
>          Components: framework, master, slave
>            Reporter: Benjamin Hindman
>            Assignee: Adam B
>
> A framework must specify the 'user' it wants to use at the time of regist=
ration by filling in the 'user' field of FrameworkInfo. Instead, a framewor=
k should be able to specify a user per task or executor by including the us=
er in CommandInfo. The source of truth for the user from the slave's perspe=
ctive should be CommandInfo.user and the master should validate (and possib=
ly update) CommandInfo.user when a task is launched. We'll also need to aut=
horize each user a framework attempts to use during task validation.


--
This message was sent by Atlassian JIRA
(v6.2#6252)