> On Jan 6, 2016, at 9:18 PM, Jie Yu wrote:
>
> James, this is for filesystem/posix isolator, and has nothing to do with
> posix/disk isolator. Also, this has nothing to do with persistent volumes.
Ah right. Thanks!
>
> - Jie
>
> On Wed, Jan 6, 2016 at 8:03 PM, James
> On Jan 6, 2016, at 7:44 PM, Timothy Chen wrote:
>
> Hi James,
>
> There isn't any backward compatibility needed since we never really do
> anything with volumes with posix filesystem, now we're just making
> sure we don't allow it since it can cause problems especially
James, this is for filesystem/posix isolator, and has nothing to do with
posix/disk isolator. Also, this has nothing to do with persistent volumes.
- Jie
On Wed, Jan 6, 2016 at 8:03 PM, James Peach wrote:
>
> > On Jan 6, 2016, at 7:44 PM, Timothy Chen
Hi James,
There isn't any backward compatibility needed since we never really do
anything with volumes with posix filesystem, now we're just making
sure we don't allow it since it can cause problems especially with
volumes that has images.
Tim
On Wed, Jan 6, 2016 at 7:26 PM, James Peach
Hi Tim,
What are the backwards compatibility implications of this?
> On Jan 6, 2016, at 6:50 PM, tnac...@apache.org wrote:
>
> Repository: mesos
> Updated Branches:
> refs/heads/master c258d8af7 -> 52abf8de3
>
>
> Fixed posix filesystem isolator to not allow executors with image.
>
>