----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44570/#review122721 -----------------------------------------------------------
Does it a typo in Description? s/archived/achieved src/tests/master_validation_tests.cpp (lines 1180 - 1192) <https://reviews.apache.org/r/44570/#comment184819> What about update logic as following, this can make sure no need to call `set_owner` twice. ExecutorInfo executor; executor.set_owner("foo"); task.mutable_executor()->CopyFrom(executor); // A task with a set owner and an executor with a set owner is invalid. EXPECT_SOME(task::internal::validateOwner(task)); task.clear_owner(); // A task with an executor that has a set owner is valid. EXPECT_NONE(task::internal::validateOwner(task)); - Guangya Liu On 三月 9, 2016, 2:21 p.m., Jan Schlicht wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/44570/ > ----------------------------------------------------------- > > (Updated 三月 9, 2016, 2:21 p.m.) > > > Review request for mesos, Adam B and Joerg Schad. > > > Bugs: MESOS-4772 > https://issues.apache.org/jira/browse/MESOS-4772 > > > Repository: mesos > > > Description > ------- > > To be able to authenticate HTTP requests for tasks, the authorizer has to > determine who owns the tasks. This is archived by adding an owner field to > TaskInfo and ExecutorInfo. > > > Diffs > ----- > > include/mesos/mesos.proto 3d22ec32655dca741169e1f0e382303e061c38b7 > src/master/validation.hpp 29dbdf1da540db4966ff9e86037badde06e69a4b > src/master/validation.cpp 820a9faee6fde09a98317854b181fe897167e2ca > src/tests/master_validation_tests.cpp > c9bc38ce604d2d44d6e6b1286507d1c45e5e9e25 > > Diff: https://reviews.apache.org/r/44570/diff/ > > > Testing > ------- > > make check > > > Thanks, > > Jan Schlicht > >
