> On Oct. 18, 2017, 3:40 a.m., Jie Yu wrote: > > include/mesos/authorizer/acls.proto > > Lines 435-437 (patched) > > <https://reviews.apache.org/r/60891/diff/3/?file=1858661#file1858661line435> > > > > hum, i got confused. How do you get the user of a container? And it's > > not consistent with below? > > Joseph Wu wrote: > Note: The user is specified in the call to launch standalone/nested > containers.
but this is kill standalone container. Do we set 'user' in the `ObjectApprover::Object` for kill action? - Jie ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/60891/#review188447 ----------------------------------------------------------- On Oct. 16, 2017, 11:42 p.m., Joseph Wu wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/60891/ > ----------------------------------------------------------- > > (Updated Oct. 16, 2017, 11:42 p.m.) > > > Review request for mesos, Alexander Rojas, Gilbert Song, and Jie Yu. > > > Bugs: MESOS-7305 > https://issues.apache.org/jira/browse/MESOS-7305 > > > Repository: mesos > > > Description > ------- > > This defines some coarse-grained AuthZ for launching and managing > standalone containers. Each HTTP principal can be given the right > to Launch, Wait upon, Kill, or Remove standalone containers under > a given (posix) user. > > > Diffs > ----- > > include/mesos/authorizer/acls.proto > 587b71489730f9a1252c73c0239e3d9892b3ae8e > include/mesos/authorizer/authorizer.proto > 87a805794f430fc8b2e47de6d624b95deef162b4 > src/authorizer/local/authorizer.cpp > 2fe7b879e649b13322cfcb300c21ef1ed0fea410 > > > Diff: https://reviews.apache.org/r/60891/diff/4/ > > > Testing > ------- > > See later in chain. > > > Thanks, > > Joseph Wu > >
