> On Feb. 2, 2015, 9:20 p.m., Ian Downes wrote:
> > src/slave/containerizer/mesos/containerizer.cpp, lines 1161-1167
> > <https://reviews.apache.org/r/30510/diff/1/?file=843874#file843874line1161>
> >
> >     How can we ensure that such a filesystem isolator is being used? 
> > Shouldn't all of this functionality be in one place!?
> 
> Jie Yu wrote:
>     For now, in master, we will only allow relative non-nested container path.

Revised the comments.


- Jie


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/30510/#review70617
-----------------------------------------------------------


On Feb. 9, 2015, 6 p.m., Jie Yu wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/30510/
> -----------------------------------------------------------
> 
> (Updated Feb. 9, 2015, 6 p.m.)
> 
> 
> Review request for mesos, Ben Mahler, Ian Downes, Michael Park, and Vinod 
> Kone.
> 
> 
> Bugs: MESOS-2031
>     https://issues.apache.org/jira/browse/MESOS-2031
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> Allowed Mesos containerizer to prepare and update volumes.
> 
> Mesos containerizer setup volumes for the container.
> 
> 
> Diffs
> -----
> 
>   src/slave/containerizer/mesos/containerizer.hpp 
> b3aafe4efa9f3469d7a3fd39243ad66b46d6a54d 
>   src/slave/containerizer/mesos/containerizer.cpp 
> fa40d47aee7803833bcde6cce1e86a21d7cf27d0 
> 
> Diff: https://reviews.apache.org/r/30510/diff/
> 
> 
> Testing
> -------
> 
> make check
> 
> 
> Thanks,
> 
> Jie Yu
> 
>

Reply via email to