Hi,
I apologize for bombarding with so many emails on the same issue. So, I
modified the acl.json as below.
1. I was able to launch the framework with authentication as users devel1
and devel2.
2. I was able to launch a task as user devel1
3. I get TASK_LOST when I try to launch task with the
On 9 March 2015 at 07:36, Sivaram Kannan sivara...@gmail.com wrote:
Hi,
I apologize for bombarding with so many emails on the same issue. So, I
modified the acl.json as below.
1. I was able to launch the framework with authentication as users devel1
and devel2.
Just so that our
Hi Vinod,
The users in below run_tasks definition - does it refer to unix users in
the machine where the framework is run or the unix users in the mesos-slave
machine. I think the fact that I run all softwares (mesos-master,
mesos-slave, marathon) as docker containers is of significance and
Hi Vinod,
Thanks, I got it. I guess I did not understand the relationship between
principals defined in authentication and in authorization. I re-read the
authentication and credentials flag, it is not clear from them that the
principals defined in authorization should match them to work
Awesome. Thanks Vinod. Let me try that.
On Fri, Mar 6, 2015 at 10:08 PM, Vinod Kone vinodk...@apache.org wrote:
Quoting form the documentation
http://mesos.apache.org/documentation/latest/authorization/:
There are couple of important things to note:
1.
ACLs are matched in the
Just to make it more clear, I want to understand in which scenario would
the task authorization will fail and framework gets a TASK_LOST error. I
would greatly appreciate If you could give an example what I should change
in the acl.json and the master or slave to get the TASK_LOST errror.
Version
Guess I don't understand then. Let me give some tests I ran for
understanding ACL, but am not clear which unix users is this. Assume I have
two nodes.
Node1 - runs Mesos-master and marathon
Node2 - runs mesos-slave
Both the above nodes have an users named devel and root.
Test1: I started the
I'm not very familiar with Marathon, but the 'user' in the 'run_tasks' ACL
is the unix user that the executor/run process runs as. This user is set by
frameworks by setting 'CommandInfo.user'.
On Thu, Mar 5, 2015 at 9:06 AM, Sivaram Kannan sivara...@gmail.com wrote:
Hi,
The user that is
Hi,
The user that is defined as part of Mesos's Authorization ACL, which user
is it? Taking marathon framework as example, the users defined as part of
run_tasks principal, is it the user that is used to run marathon executable
or the unix user available in the mesos-slave's?
Documentation in
9 matches
Mail list logo
