Re: HTTP Basic Auth for Mesos UI

[Michał Łowicki]

On Thu, Mar 24, 2016 at 11:02 PM, Pradeep Chhetri <
pradeep.chhetr...@gmail.com> wrote:

> Hi Michal,
>
> A simple workaround will be to use a reverse proxy (Nginx or Apache) in
> front of mesos master URL and enable corresponding htpasswd based
> authentication module.
>

Yes, but since it isn't critical for us we'll probably wait for MESOS-5027.
We're using reverse proxy for some other tools so it's definitely an option
if can't wait for built-in support in Mesos WebUI.


>
> On Thu, Mar 24, 2016 at 8:00 PM, Michał Łowicki 
> wrote:
>
>>
>>
>> On Thu, Mar 24, 2016 at 8:41 PM, Greg Mann  wrote:
>>
>>> Mi Michal,
>>> We have recently enabled authentication on many master/agent endpoints,
>>> but authentication doesn't yet work on the webui. Once all the relevant
>>> endpoints have authentication enabled, we still need to add a login
>>> mechanism to the webui. You can find a ticket for the webui improvement
>>> here: https://issues.apache.org/jira/browse/MESOS-5027
>>>
>>
>> Thanks. Looking forward to it. It isn't something critical but eventually
>> we would like to have a built-in way to enable authentication to restrict
>> access at our company.
>>
>>
>>>
>>> Cheers,
>>> Greg
>>>
>>> On Thu, Mar 24, 2016 at 11:21 AM, haosdent  wrote:
>>>
 Yes, I saw @Greg and @Joerg add the auth to http endpoints recently.
 The related tickets is https://issues.apache.org/jira/browse/MESOS-4844
 and https://issues.apache.org/jira/browse/MESOS-4847

 On Fri, Mar 25, 2016 at 2:08 AM, Michał Łowicki 
 wrote:

> Hi,
>
> Is there any built-in support for it in Mesos UI (port 5050 by
> default)? There is --authenticate_http but it seems to apply to HTTP
> API? Found MESOS-1923
>  but ticket is very
> old.
>
> --
> BR,
> Michał Łowicki
>



 --
 Best Regards,
 Haosdent Huang

>>>
>>>
>>
>>
>> --
>> BR,
>> Michał Łowicki
>>
>
>
>
> --
> Regards,
> Pradeep Chhetri
>



-- 
BR,
Michał Łowicki

Re: HTTP Basic Auth for Mesos UI

[Pradeep Chhetri]

Hi Michal,

A simple workaround will be to use a reverse proxy (Nginx or Apache) in
front of mesos master URL and enable corresponding htpasswd based
authentication module.

On Thu, Mar 24, 2016 at 8:00 PM, Michał Łowicki  wrote:

>
>
> On Thu, Mar 24, 2016 at 8:41 PM, Greg Mann  wrote:
>
>> Mi Michal,
>> We have recently enabled authentication on many master/agent endpoints,
>> but authentication doesn't yet work on the webui. Once all the relevant
>> endpoints have authentication enabled, we still need to add a login
>> mechanism to the webui. You can find a ticket for the webui improvement
>> here: https://issues.apache.org/jira/browse/MESOS-5027
>>
>
> Thanks. Looking forward to it. It isn't something critical but eventually
> we would like to have a built-in way to enable authentication to restrict
> access at our company.
>
>
>>
>> Cheers,
>> Greg
>>
>> On Thu, Mar 24, 2016 at 11:21 AM, haosdent  wrote:
>>
>>> Yes, I saw @Greg and @Joerg add the auth to http endpoints recently. The
>>> related tickets is https://issues.apache.org/jira/browse/MESOS-4844 and
>>> https://issues.apache.org/jira/browse/MESOS-4847
>>>
>>> On Fri, Mar 25, 2016 at 2:08 AM, Michał Łowicki 
>>> wrote:
>>>
 Hi,

 Is there any built-in support for it in Mesos UI (port 5050 by
 default)? There is --authenticate_http but it seems to apply to HTTP
 API? Found MESOS-1923
  but ticket is very
 old.

 --
 BR,
 Michał Łowicki

>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Haosdent Huang
>>>
>>
>>
>
>
> --
> BR,
> Michał Łowicki
>



-- 
Regards,
Pradeep Chhetri

Re: HTTP Basic Auth for Mesos UI

[Michał Łowicki]

On Thu, Mar 24, 2016 at 8:41 PM, Greg Mann  wrote:

> Mi Michal,
> We have recently enabled authentication on many master/agent endpoints,
> but authentication doesn't yet work on the webui. Once all the relevant
> endpoints have authentication enabled, we still need to add a login
> mechanism to the webui. You can find a ticket for the webui improvement
> here: https://issues.apache.org/jira/browse/MESOS-5027
>

Thanks. Looking forward to it. It isn't something critical but eventually
we would like to have a built-in way to enable authentication to restrict
access at our company.


>
> Cheers,
> Greg
>
> On Thu, Mar 24, 2016 at 11:21 AM, haosdent  wrote:
>
>> Yes, I saw @Greg and @Joerg add the auth to http endpoints recently. The
>> related tickets is https://issues.apache.org/jira/browse/MESOS-4844 and
>> https://issues.apache.org/jira/browse/MESOS-4847
>>
>> On Fri, Mar 25, 2016 at 2:08 AM, Michał Łowicki 
>> wrote:
>>
>>> Hi,
>>>
>>> Is there any built-in support for it in Mesos UI (port 5050 by default)?
>>> There is --authenticate_http but it seems to apply to HTTP API? Found
>>> MESOS-1923  but
>>> ticket is very old.
>>>
>>> --
>>> BR,
>>> Michał Łowicki
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>
>


-- 
BR,
Michał Łowicki

Re: HTTP Basic Auth for Mesos UI

[Greg Mann]

Mi Michal,
We have recently enabled authentication on many master/agent endpoints, but
authentication doesn't yet work on the webui. Once all the relevant
endpoints have authentication enabled, we still need to add a login
mechanism to the webui. You can find a ticket for the webui improvement
here: https://issues.apache.org/jira/browse/MESOS-5027

Cheers,
Greg

On Thu, Mar 24, 2016 at 11:21 AM, haosdent  wrote:

> Yes, I saw @Greg and @Joerg add the auth to http endpoints recently. The
> related tickets is https://issues.apache.org/jira/browse/MESOS-4844 and
> https://issues.apache.org/jira/browse/MESOS-4847
>
> On Fri, Mar 25, 2016 at 2:08 AM, Michał Łowicki 
> wrote:
>
>> Hi,
>>
>> Is there any built-in support for it in Mesos UI (port 5050 by default)?
>> There is --authenticate_http but it seems to apply to HTTP API? Found
>> MESOS-1923  but ticket
>> is very old.
>>
>> --
>> BR,
>> Michał Łowicki
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: HTTP Basic Auth for Mesos UI

[Michał Łowicki]

Yes, this is it. Thanks.

On Thu, Mar 24, 2016 at 7:21 PM, haosdent  wrote:

> Yes, I saw @Greg and @Joerg add the auth to http endpoints recently. The
> related tickets is https://issues.apache.org/jira/browse/MESOS-4844 and
> https://issues.apache.org/jira/browse/MESOS-4847
>
> On Fri, Mar 25, 2016 at 2:08 AM, Michał Łowicki 
> wrote:
>
>> Hi,
>>
>> Is there any built-in support for it in Mesos UI (port 5050 by default)?
>> There is --authenticate_http but it seems to apply to HTTP API? Found
>> MESOS-1923  but ticket
>> is very old.
>>
>> --
>> BR,
>> Michał Łowicki
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>



-- 
BR,
Michał Łowicki

Re: HTTP Basic Auth for Mesos UI

[haosdent]

Yes, I saw @Greg and @Joerg add the auth to http endpoints recently. The
related tickets is https://issues.apache.org/jira/browse/MESOS-4844 and
https://issues.apache.org/jira/browse/MESOS-4847

On Fri, Mar 25, 2016 at 2:08 AM, Michał Łowicki  wrote:

> Hi,
>
> Is there any built-in support for it in Mesos UI (port 5050 by default)?
> There is --authenticate_http but it seems to apply to HTTP API? Found
> MESOS-1923  but ticket
> is very old.
>
> --
> BR,
> Michał Łowicki
>



-- 
Best Regards,
Haosdent Huang

HTTP Basic Auth for Mesos UI

[Michał Łowicki]

Hi,

Is there any built-in support for it in Mesos UI (port 5050 by default)?
There is --authenticate_http but it seems to apply to HTTP API? Found
MESOS-1923  but ticket is
very old.

-- 
BR,
Michał Łowicki

Re: [VOTE] Release Apache Mesos 0.24.2 (rc2)

[Michael Park]

Will do. Thanks!

On 23 March 2016 at 23:43, Benjamin Mahler 
wrote:

> Also, I tagged https://issues.apache.org/jira/browse/MESOS-5021 with a
> fix version of 0.24.2. Can you include it?
>
> On Sat, Mar 19, 2016 at 6:30 AM, Michael Park  wrote:
>
>> As there are insufficient votes on this rc along with a request
>> from Evan Krall to include additional fixes:
>> https://www.mail-archive.com/user@mesos.apache.org/msg06205.html,
>> I'm declaring this rc failed, and will cut be cutting an rc3 early next
>> week.
>>
>> Thanks,
>>
>> MPark
>>
>> On 13 March 2016 at 20:57, Michael Park  wrote:
>>
>>> +1 (binding)
>>>
>>> Internal CI results with the corresponding JIRA tickets for the failed
>>> tests:
>>>
>>> CentOS 6 (non-SSL):
>>> CentOS 6 (SSL):
>>>   - Failed with MESOS-2017
>>> 
>>>
>>> CentOS 7 (non-SSL):
>>> CentOS 7 (SSL):
>>>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>>> (MESOS-4039 )
>>>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>>> (MESOS-3215 )
>>>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>>>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
>>> (MESOS-3296 )
>>>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
>>> (MESOS-3410 )
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>>> (MESOS-4047 ,
>>> MESOS-4053 )
>>>   - PerfTest.ROOT_SamplePid
>>> (MESOS-3079 )
>>>
>>> Debian 8 (non-SSL):
>>> Debian 8 (SSL):
>>>   - Failed with MESOS-3964
>>> 
>>>
>>> Ubuntu 12 (non-SSL):
>>> Ubuntu 12 (SSL):
>>> Ubuntu 14 (non-SSL):
>>> Ubuntu 14 (SSL):
>>>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>>>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
>>> (MESOS-4035 )
>>>
>>> Ubuntu 15 (non-SSL):
>>>   - DockerContainerizerTest.ROOT_DOCKER_Logs
>>> (MESOS-4676 )
>>>   - LimitedCpuIsolatorTest.ROOT_CGROUPS_Pids_and_Tids
>>> (MESOS-4677 )
>>>
>>> Ubuntu 15 (SSL): Success!
>>>
>>> On 13 March 2016 at 18:42, Michael Park  wrote:
>>>
 While the vote for this release was open until Fri Mar 11 23:59:59 EST
 2016,
 I'm going to give it another 3 days since there has not been any -1
 votes.

 The vote is extended until Wed Mar 16 23:59:59 EST 2016.

 On 10 March 2016 at 12:49, Greg Mann  wrote:

> +1 (non-binding)
>
> Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL
> enabled. All tests pass.
>
> I was also able to successfully test a simple upgrade scenario from
> 0.23.1 to 0.24.2-rc2 using the script found here:
> https://reviews.apache.org/r/44229/
>
> Cheers,
> Greg
>
>
> On Tue, Mar 8, 2016 at 6:50 PM, Michael Park  wrote:
>
>> The link to the commit above points to the one on the master branch.
>> The following is the one on the `0.24.2-rc2` branch: Fixed compiler
>> warning
>> in values tests.
>> <
>> https://github.com/apache/mesos/commit/afb8a0cffaf8bc235ce45087c80bafe87488dcd0
>> >
>>
>> On 8 March 2016 at 21:21, Michael Park  wrote:
>>
>> > Hi all,
>> >
>> > Please vote on releasing the following candidate as Apache Mesos
>> 0.24.2.
>> >
>> >
>> > 0.24.2 includes the following:
>> >
>> >
>> 
>> >
>> > The only diff with RC1 is the following: Fixed compiler warning in
>> values
>> > tests.
>> > <
>> https://github.com/apache/mesos/commit/bfeb070a2aef52f445eb057076d344fd184eb461
>> >
>>
>> > As I described in the RC1 [VOTE] thread, even though this is a
>> trivial
>> > compile fix,
>> > I decided to cut an RC2 in order to avoid breaking those who
>> compile Mesos
>> > from source.
>> >
>> > * Improvements
>> > - Allocator filter performance
>> > - Port Ranges performance
>> > - UUID performance
>> > - `/state` endpoint performance
>> >   - GLOG performance
>> >   - Configurable task/framework history
>> >   - Offer filter timeout fix for backlogged allocator
>> >
>> > * Bugs
>> >   - SSL
>> > 

Re: [VOTE] Release Apache Mesos 0.25.1 (rc2)

[Michael Park]

Will do. Thanks!

On 23 March 2016 at 23:43, Benjamin Mahler 
wrote:

> Also, I tagged https://issues.apache.org/jira/browse/MESOS-5021 with a
> fix version of 0.25.1. Can you include it?
>
> On Sat, Mar 19, 2016 at 6:33 AM, Michael Park  wrote:
>
>> As there are insufficient votes on this rc along with a request
>> from Evan Krall to include additional fixes:
>> https://www.mail-archive.com/user@mesos.apache.org/msg06204.html
>> ,
>> I'm declaring this rc failed, and will cut be cutting an rc3 early next
>> week.
>>
>> Thanks,
>>
>> MPark
>>
>> On 13 March 2016 at 19:55, Michael Park  wrote:
>>
>>> +1 (binding)
>>>
>>> Internal CI results with the corresponding JIRA tickets for the failed
>>> tests:
>>>
>>> CentOS 6 (non-SSL):
>>> CentOS 6 (SSL):
>>>   - Failed with MESOS-2017
>>> 
>>>
>>> CentOS 7 (non-SSL):
>>>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>>> (MESOS-4039 )
>>>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>>> (MESOS-3215 )
>>>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>>>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>>>   - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
>>> (MESOS-3296 )
>>>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
>>> (MESOS-3410 )
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>>> (MESOS-4047 ,
>>> MESOS-4053 )
>>>
>>> CentOS 7 (SSL):
>>>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>>> (MESOS-4039 )
>>>   - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
>>> (MESOS-2672 )
>>>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>>> (MESOS-3215 )
>>>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>>>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>>>   - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
>>> (MESOS-3296 )
>>>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
>>> (MESOS-3410 )
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>>> (MESOS-4047 ,
>>> MESOS-4053 )
>>>
>>> Debian 8 (non-SSL):
>>> Debian 8 (SSL):
>>>   - Failed with MESOS-3964
>>> 
>>>
>>> Ubuntu 12 (non-SSL):
>>>   - DockerContainerizerTest.ROOT_DOCKER_Logs
>>> (MESOS-4676 )
>>>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>>>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
>>> (MESOS-4035 )
>>>
>>> Ubuntu 12 (SSL):
>>>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>>>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
>>> (MESOS-4035 )
>>>   - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
>>> (MESOS-2672 )
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>>> (MESOS-4047 ,
>>> MESOS-4053 )
>>>
>>> Ubuntu 14 (non-SSL):
>>>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>>>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
>>> (MESOS-4035 )
>>>
>>> Ubuntu 14 (SSL):
>>>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>>>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
>>> (MESOS-403

Re: [VOTE] Release Apache Mesos 0.26.1 (rc2)

[Michael Park]

Will do. Thanks!

On 23 March 2016 at 23:43, Benjamin Mahler  wrote:

> Also, I tagged https://issues.apache.org/jira/browse/MESOS-5021 with a
> fix version of 0.26.1. Can you include it?
>
> On Mon, Mar 21, 2016 at 1:59 PM, Benjamin Mahler 
> wrote:
>
>> Yes it has existed for a long time but has only been discovered recently.
>>
>> The way this was discovered was that garbage collection of user sandboxes
>> fails, which can result in the disk eventually filling up. This occurs when
>> there are special files in the sandbox (e.g. socket file).
>>
>> IMO it's a critical issue to fix.
>>
>> On Sat, Mar 19, 2016 at 6:39 AM, Michael Park  wrote:
>>
>>> Ben,
>>>
>>> Do I understand correctly that this is not a regression, but a fix
>>> important enough for us to backport?
>>> I'm curious as to what makes it significant. Could you elaborate a
>>> little as to what the consequences are?
>>>
>>> Thanks!
>>>
>>> MPark
>>>
>>> On 18 March 2016 at 16:20, Benjamin Mahler  wrote:
>>>
 These are be captured under:
 https://issues.apache.org/jira/browse/MESOS-4979

 On Thu, Mar 17, 2016 at 5:04 PM, Benjamin Mahler 
 wrote:

> Thanks for the hard work! Do we need to backport the rmdir fixes on
> the outstanding release candidates?
>
> commit 5278e5cc50544ed7af28b15a1acd2b2e96a15a47
> Author: Jojy Varghese 
> Date:   Tue Mar 15 17:12:01 2016 -0700
>
> Added support for FTS_SLNONE in rmdir.
>
> Review: https://reviews.apache.org/r/44874/
>
> commit fbe1f37f65fd9f1d4f2c30a3cfd7a50df92ccc2c
> Author: Alex Clemmer 
> Date:   Tue Mar 1 23:29:21 2016 -0800
>
> Stout:[1/2] Fixed error reporting bug in `os::rmdir`.
>
> Review: https://reviews.apache.org/r/43907/
>
> commit f8b7ac28b1a918864a06b3f99f45b0257c7b6f68
> Author: Jojy Varghese 
> Date:   Tue Mar 1 14:32:13 2016 -0800
>
> Added FS_DEFAULT case in rmdir.
>
> We currently dont handle special files like device files in rmdir.
> This
> change adds FS_DEFAULT as one of the cases where we try to unlink a
> file. Reference: http://man7.org/linux/man-pages/man3/fts.3.html
>
> Review: https://reviews.apache.org/r/44230/
>
> On Wed, Mar 16, 2016 at 8:21 PM, Vinod Kone 
> wrote:
>
>> +1 (binding)
>>
>> Tested on ASF CI.
>>
>> On Sun, Mar 13, 2016 at 4:33 PM, Michael Park 
>> wrote:
>>
>> > +1 (binding)
>> >
>> > Internal CI results with the corresponding JIRA tickets for the
>> failed
>> > tests:
>> >
>> > CentOS 6 (non-SSL):
>> >   - MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
>> > (MESOS-3049 )
>> >   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>> > (MESOS-4039 )
>> >   - UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
>> > (MESOS-4035 )
>> >   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>> > (MESOS-3215 )
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>> > (MESOS-4047 ,
>> > MESOS-4053 )
>> >
>> > CentOS 6 (SSL):
>> >   - MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
>> > (MESOS-3049 )
>> >   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>> > (MESOS-4039 )
>> >   - UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
>> > (MESOS-4035 )
>> >   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>> > (MESOS-3215 )
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>> > (MESOS-4047 ,
>> > MESOS-4053 )
>> >
>> > CentOS 7 (non-SSL):
>> >   - LimitedCpuIsolatorTest.ROOT_CGROUPS_Pids_and_Tids
>> > (MESOS-4677 )
>> >   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>> > (MESOS-4039 )
>> >   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>> > (MESOS-3215 )
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>> > (MESOS-4047 

Re: limit swap usage with docker containeriser

[Guangya Liu]

The reason is that DockerContainerizer is using doker CLI to create
container, Docker performs the initial container configuration, while
modifying resources (CPU, memory, etc.) and the DockerContainerizer cannot
compose with other existing and future Mesos isolators, such as the cgroups/mem
isolator which is required by you.

I think that you can have a try for MesosContainerizer with docker image,
you can refer to a simple tutorial here:
https://github.com/apache/mesos/blob/master/docs/container-image.md#test-it-out

Thanks,

Guangya


On Thu, Mar 24, 2016 at 5:03 PM, David Keijser 
wrote:

> On Thu, Mar 24, 2016 at 12:12:56AM +0800, haosdent wrote:
> > Yes, this flag only available in mesos containerizer.
> >
>
> Why? :)
>
> I can't imagine why this wouldn't be desired when using the docker
> containeriser. Is this something that would be hard to support for
> docker and that's why it was not added?
>

Re: limit swap usage with docker containeriser

[David Keijser]

On Thu, Mar 24, 2016 at 12:12:56AM +0800, haosdent wrote:
> Yes, this flag only available in mesos containerizer.
> 

Why? :)

I can't imagine why this wouldn't be desired when using the docker
containeriser. Is this something that would be hard to support for
docker and that's why it was not added?


signature.asc
Description: PGP signature