[jira] [Updated] (MESOS-5977) Remove CgroupsDevicesIsolator

[haosdent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

haosdent updated MESOS-5977:

Description: 
Remove the dependencies of

{code}
src/slave/containerizer/mesos/isolators/cgroups/devices.cpp
src/slave/containerizer/mesos/isolators/cgroups/devices.hpp
{code}

and update test cases.

  was:
Remove the dependencies of

{code}
src/slave/containerizer/mesos/isolators/cgroups/mem.cpp
src/slave/containerizer/mesos/isolators/cgroups/mem.hpp
{code}

and update test cases.


> Remove CgroupsDevicesIsolator
> -
>
> Key: MESOS-5977
> URL: https://issues.apache.org/jira/browse/MESOS-5977
> Project: Mesos
>  Issue Type: Task
>  Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Remove the dependencies of
> {code}
> src/slave/containerizer/mesos/isolators/cgroups/devices.cpp
> src/slave/containerizer/mesos/isolators/cgroups/devices.hpp
> {code}
> and update test cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5976) Remove CgroupsNetClsIsolator

[haosdent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

haosdent updated MESOS-5976:

Description: 
Remove the dependencies of

{code}
src/slave/containerizer/mesos/isolators/cgroups/net_cls.cpp
src/slave/containerizer/mesos/isolators/cgroups/net_cls.hpp
{code}

and update test cases.

  was:Enable the cgroups unified isolator in Mesos containerizer.


> Remove CgroupsNetClsIsolator
> 
>
> Key: MESOS-5976
> URL: https://issues.apache.org/jira/browse/MESOS-5976
> Project: Mesos
>  Issue Type: Task
>  Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Remove the dependencies of
> {code}
> src/slave/containerizer/mesos/isolators/cgroups/net_cls.cpp
> src/slave/containerizer/mesos/isolators/cgroups/net_cls.hpp
> {code}
> and update test cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5974) Remove CgroupsMemIsolator

[haosdent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

haosdent updated MESOS-5974:

Description: 
Remove the dependencies of

{code}
src/slave/containerizer/mesos/isolators/cgroups/mem.cpp
src/slave/containerizer/mesos/isolators/cgroups/mem.hpp
{code}

and update test cases.

  was:Enable the cgroups unified isolator in Mesos containerizer.


> Remove CgroupsMemIsolator
> -
>
> Key: MESOS-5974
> URL: https://issues.apache.org/jira/browse/MESOS-5974
> Project: Mesos
>  Issue Type: Task
>  Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Remove the dependencies of
> {code}
> src/slave/containerizer/mesos/isolators/cgroups/mem.cpp
> src/slave/containerizer/mesos/isolators/cgroups/mem.hpp
> {code}
> and update test cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5973) Remove CgroupsCpushareIsolator

[haosdent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

haosdent updated MESOS-5973:

Description: 
Remove the dependencies of

{code}
src/slave/containerizer/mesos/isolators/cgroups/cpu.cpp
src/slave/containerizer/mesos/isolators/cgroups/cpu.hpp
{code}

and update test cases.

  was:Enable the cgroups unified isolator in Mesos containerizer.


> Remove CgroupsCpushareIsolator
> --
>
> Key: MESOS-5973
> URL: https://issues.apache.org/jira/browse/MESOS-5973
> Project: Mesos
>  Issue Type: Task
>  Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Remove the dependencies of
> {code}
> src/slave/containerizer/mesos/isolators/cgroups/cpu.cpp
> src/slave/containerizer/mesos/isolators/cgroups/cpu.hpp
> {code}
> and update test cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5975) Remove CgroupsPerfEventIsolator

[haosdent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

haosdent updated MESOS-5975:

Description: 
Remove the dependencies of

{code}
src/slave/containerizer/mesos/isolators/cgroups/perf_event.cpp
src/slave/containerizer/mesos/isolators/cgroups/perf_event.hpp
{code}

and update test cases.

  was:Enable the cgroups unified isolator in Mesos containerizer.


> Remove CgroupsPerfEventIsolator
> ---
>
> Key: MESOS-5975
> URL: https://issues.apache.org/jira/browse/MESOS-5975
> Project: Mesos
>  Issue Type: Task
>  Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Remove the dependencies of
> {code}
> src/slave/containerizer/mesos/isolators/cgroups/perf_event.cpp
> src/slave/containerizer/mesos/isolators/cgroups/perf_event.hpp
> {code}
> and update test cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5977) Remove CgroupsDevicesIsolator

[haosdent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

haosdent updated MESOS-5977:

Description: 
Remove the dependencies of

{code}
src/slave/containerizer/mesos/isolators/cgroups/mem.cpp
src/slave/containerizer/mesos/isolators/cgroups/mem.hpp
{code}

and update test cases.

  was:Enable the cgroups unified isolator in Mesos containerizer.


> Remove CgroupsDevicesIsolator
> -
>
> Key: MESOS-5977
> URL: https://issues.apache.org/jira/browse/MESOS-5977
> Project: Mesos
>  Issue Type: Task
>  Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>
> Remove the dependencies of
> {code}
> src/slave/containerizer/mesos/isolators/cgroups/mem.cpp
> src/slave/containerizer/mesos/isolators/cgroups/mem.hpp
> {code}
> and update test cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5977) Remove CgroupsDevicesIsolator

[haosdent (JIRA)]

haosdent created MESOS-5977:
---

 Summary: Remove CgroupsDevicesIsolator
 Key: MESOS-5977
 URL: https://issues.apache.org/jira/browse/MESOS-5977
 Project: Mesos
  Issue Type: Task
  Components: cgroups, isolation
Reporter: haosdent
Assignee: haosdent


Enable the cgroups unified isolator in Mesos containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5976) Remove CgroupsNetClsIsolator

[haosdent (JIRA)]

haosdent created MESOS-5976:
---

 Summary: Remove CgroupsNetClsIsolator
 Key: MESOS-5976
 URL: https://issues.apache.org/jira/browse/MESOS-5976
 Project: Mesos
  Issue Type: Task
  Components: cgroups, isolation
Reporter: haosdent
Assignee: haosdent


Enable the cgroups unified isolator in Mesos containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5975) Remove CgroupsPerfEventIsolator

[haosdent (JIRA)]

haosdent created MESOS-5975:
---

 Summary: Remove CgroupsPerfEventIsolator
 Key: MESOS-5975
 URL: https://issues.apache.org/jira/browse/MESOS-5975
 Project: Mesos
  Issue Type: Task
  Components: cgroups, isolation
Reporter: haosdent
Assignee: haosdent


Enable the cgroups unified isolator in Mesos containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5974) Remove CgroupsMemIsolator

[haosdent (JIRA)]

haosdent created MESOS-5974:
---

 Summary: Remove CgroupsMemIsolator
 Key: MESOS-5974
 URL: https://issues.apache.org/jira/browse/MESOS-5974
 Project: Mesos
  Issue Type: Task
  Components: cgroups, isolation
Reporter: haosdent
Assignee: haosdent


Enable the cgroups unified isolator in Mesos containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5973) Remove CgroupsCpushareIsolator

[haosdent (JIRA)]

haosdent created MESOS-5973:
---

 Summary: Remove CgroupsCpushareIsolator
 Key: MESOS-5973
 URL: https://issues.apache.org/jira/browse/MESOS-5973
 Project: Mesos
  Issue Type: Task
  Components: cgroups, isolation
Reporter: haosdent
Assignee: haosdent


Enable the cgroups unified isolator in Mesos containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5972) SharedResourcesTest failing on macOS

[Anindya Sinha (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405165#comment-15405165
 ] 

Anindya Sinha commented on MESOS-5972:
--

Posted https://reviews.apache.org/r/50732/.

> SharedResourcesTest failing on macOS
> 
>
> Key: MESOS-5972
> URL: https://issues.apache.org/jira/browse/MESOS-5972
> Project: Mesos
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.1.0
> Environment: $ g++ --version
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 7.0.2 (clang-700.1.81)
> Target: x86_64-apple-darwin14.5.0
> Thread model: posix
>Reporter: Yan Xu
>Assignee: Anindya Sinha
>
> The following consistently fail in the specified environment.
> {noformat:title=}
> [ RUN  ] SharedResourcesTest.ScalarSubtractionShared
> ../../src/tests/resources_tests.cpp:2504: Failure
> Value of: (r2 - r1).count(disk)
>   Actual: 18446744073709551615
> Expected: 0u
> Which is: 0
> [  FAILED  ] SharedResourcesTest.ScalarSubtractionShared (0 ms)
> [ RUN  ] SharedResourcesTest.ScalarSharedCompoundExpressions
> ../../src/tests/resources_tests.cpp:2527: Failure
> Value of: r1
>   Actual: { cpus(*):2, mem(*):10, disk(role1)[1:path]:50<4> }
> Expected: r2 - r1 + r1
> Which is: { disk(role1)[1:path]:50<3>, cpus(*):2, mem(*):10 }
> ../../src/tests/resources_tests.cpp:2531: Failure
> Value of: (r2 - r1).empty()
>   Actual: false
> Expected: true
> [  FAILED  ] SharedResourcesTest.ScalarSharedCompoundExpressions (0 ms)
> {noformat}
> /cc [~kaysoky]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5972) SharedResourcesTest failing on macOS

[Anindya Sinha (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405114#comment-15405114
 ] 

Anindya Sinha commented on MESOS-5972:
--

Yes, confirmed this issue is introduced with the change 
https://reviews.apache.org/r/50569/.

With shared resources ({{Resource_}} abstraction in {{Resources}}), we need to 
check for sharedCount to be < 0 (for shared resources) or check for scalar 
value to be < 0 (for non-shared resources).

> SharedResourcesTest failing on macOS
> 
>
> Key: MESOS-5972
> URL: https://issues.apache.org/jira/browse/MESOS-5972
> Project: Mesos
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.1.0
> Environment: $ g++ --version
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 7.0.2 (clang-700.1.81)
> Target: x86_64-apple-darwin14.5.0
> Thread model: posix
>Reporter: Yan Xu
>Assignee: Anindya Sinha
>
> The following consistently fail in the specified environment.
> {noformat:title=}
> [ RUN  ] SharedResourcesTest.ScalarSubtractionShared
> ../../src/tests/resources_tests.cpp:2504: Failure
> Value of: (r2 - r1).count(disk)
>   Actual: 18446744073709551615
> Expected: 0u
> Which is: 0
> [  FAILED  ] SharedResourcesTest.ScalarSubtractionShared (0 ms)
> [ RUN  ] SharedResourcesTest.ScalarSharedCompoundExpressions
> ../../src/tests/resources_tests.cpp:2527: Failure
> Value of: r1
>   Actual: { cpus(*):2, mem(*):10, disk(role1)[1:path]:50<4> }
> Expected: r2 - r1 + r1
> Which is: { disk(role1)[1:path]:50<3>, cpus(*):2, mem(*):10 }
> ../../src/tests/resources_tests.cpp:2531: Failure
> Value of: (r2 - r1).empty()
>   Actual: false
> Expected: true
> [  FAILED  ] SharedResourcesTest.ScalarSharedCompoundExpressions (0 ms)
> {noformat}
> /cc [~kaysoky]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5915) When start Mesos container and docker images, it does not work.

[Gilbert Song (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405092#comment-15405092
 ] 

Gilbert Song commented on MESOS-5915:
-

I am closing this JIRA since it duplicates the MESOS-5896, and most likely this 
is a configuration issue. 

> When start Mesos container and docker images, it does not work.
> ---
>
> Key: MESOS-5915
> URL: https://issues.apache.org/jira/browse/MESOS-5915
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Affects Versions: 1.0.0
>Reporter: Sunzhe
>  Labels: containerizer, docker
>
> The agent flags:
> {code}
> ./bin/mesos-agent.sh --master=:5050\
> --work_dir=/var/lib/mesos \
> 
> --isolation=cgroups/devices,gpu/nvidia,disk/du,docker/runtime,filesystem/linux
> \
> --enforce_container_disk_quota\
> --containerizers=mesos,docker \
> --image_providers=appc,docker
> {code}
> And when I create Mesos container with docker image, like this:
> {code}
> {
>   "id": "test-mesos-container-docker-image",
>   "cmd": "while [ true ]; do uname -a; sleep 3; done",
>   "cpus": 1,
>   "mem": 32.0,
>   "container": {
>   "type": "MESOS",
>   "mesos": {
>   "image": {
>   "type": "DOCKER",
>   "docker": {
>   "name": "ubuntu:14.04"
>   }
>   },
>   "network": "BRIDGE",
> "portMappings": [
>   {
> "containerPort": 8080,
> "hostPort": 0,
> "servicePort": 10008,
> "protocol": "tcp",
> "labels": {}
>   }
> ],
> "privileged": false,
> "parameters": [],
> "forcePullImage": false
>   }
>   }
> }
> {code}
> It does not wok! The result seems Docker image does not work, the container 
> uses host filesystem not the Docker image.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5825) Support mounting image volume in mesos containerizer.

[Gilbert Song (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gilbert Song updated MESOS-5825:

Sprint: Mesosphere Sprint 39  (was: Mesosphere Sprint 39, Mesosphere Sprint 
40)

> Support mounting image volume in mesos containerizer.
> -
>
> Key: MESOS-5825
> URL: https://issues.apache.org/jira/browse/MESOS-5825
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Reporter: Gilbert Song
>Assignee: Gilbert Song
>  Labels: containerizer, filesystem, isolator, mesosphere
>
> Mesos containerizer should be able to support mounting image volume type. 
> Specifically, both image rootfs and default manifest should be reachable 
> inside container's mount namespace.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5825) Support mounting image volume in mesos containerizer.

[Gilbert Song (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405082#comment-15405082
 ] 

Gilbert Song commented on MESOS-5825:
-

Sure. Thanks [~xds2000] :)

> Support mounting image volume in mesos containerizer.
> -
>
> Key: MESOS-5825
> URL: https://issues.apache.org/jira/browse/MESOS-5825
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Reporter: Gilbert Song
>Assignee: Gilbert Song
>  Labels: containerizer, filesystem, isolator, mesosphere
>
> Mesos containerizer should be able to support mounting image volume type. 
> Specifically, both image rootfs and default manifest should be reachable 
> inside container's mount namespace.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5972) SharedResourcesTest failing on macOS

[Joseph Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Wu updated MESOS-5972:
-
Assignee: Anindya Sinha

> SharedResourcesTest failing on macOS
> 
>
> Key: MESOS-5972
> URL: https://issues.apache.org/jira/browse/MESOS-5972
> Project: Mesos
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.1.0
> Environment: $ g++ --version
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 7.0.2 (clang-700.1.81)
> Target: x86_64-apple-darwin14.5.0
> Thread model: posix
>Reporter: Yan Xu
>Assignee: Anindya Sinha
>
> The following consistently fail in the specified environment.
> {noformat:title=}
> [ RUN  ] SharedResourcesTest.ScalarSubtractionShared
> ../../src/tests/resources_tests.cpp:2504: Failure
> Value of: (r2 - r1).count(disk)
>   Actual: 18446744073709551615
> Expected: 0u
> Which is: 0
> [  FAILED  ] SharedResourcesTest.ScalarSubtractionShared (0 ms)
> [ RUN  ] SharedResourcesTest.ScalarSharedCompoundExpressions
> ../../src/tests/resources_tests.cpp:2527: Failure
> Value of: r1
>   Actual: { cpus(*):2, mem(*):10, disk(role1)[1:path]:50<4> }
> Expected: r2 - r1 + r1
> Which is: { disk(role1)[1:path]:50<3>, cpus(*):2, mem(*):10 }
> ../../src/tests/resources_tests.cpp:2531: Failure
> Value of: (r2 - r1).empty()
>   Actual: false
> Expected: true
> [  FAILED  ] SharedResourcesTest.ScalarSharedCompoundExpressions (0 ms)
> {noformat}
> /cc [~kaysoky]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5972) SharedResourcesTest failing on macOS

[Joseph Wu (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405070#comment-15405070
 ] 

Joseph Wu commented on MESOS-5972:
--

Potentially introduced by: https://reviews.apache.org/r/50569/

> SharedResourcesTest failing on macOS
> 
>
> Key: MESOS-5972
> URL: https://issues.apache.org/jira/browse/MESOS-5972
> Project: Mesos
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.1.0
> Environment: $ g++ --version
> Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 7.0.2 (clang-700.1.81)
> Target: x86_64-apple-darwin14.5.0
> Thread model: posix
>Reporter: Yan Xu
>
> The following consistently fail in the specified environment.
> {noformat:title=}
> [ RUN  ] SharedResourcesTest.ScalarSubtractionShared
> ../../src/tests/resources_tests.cpp:2504: Failure
> Value of: (r2 - r1).count(disk)
>   Actual: 18446744073709551615
> Expected: 0u
> Which is: 0
> [  FAILED  ] SharedResourcesTest.ScalarSubtractionShared (0 ms)
> [ RUN  ] SharedResourcesTest.ScalarSharedCompoundExpressions
> ../../src/tests/resources_tests.cpp:2527: Failure
> Value of: r1
>   Actual: { cpus(*):2, mem(*):10, disk(role1)[1:path]:50<4> }
> Expected: r2 - r1 + r1
> Which is: { disk(role1)[1:path]:50<3>, cpus(*):2, mem(*):10 }
> ../../src/tests/resources_tests.cpp:2531: Failure
> Value of: (r2 - r1).empty()
>   Actual: false
> Expected: true
> [  FAILED  ] SharedResourcesTest.ScalarSharedCompoundExpressions (0 ms)
> {noformat}
> /cc [~kaysoky]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5388) MesosContainerizerLaunch flags execute arbitrary commands via shell.

[Gilbert Song (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gilbert Song updated MESOS-5388:

Affects Version/s: 1.0.0
 Story Points: 5  (was: 3)
   Labels: containerizer isolator mesosphere security  (was: 
mesosphere security)
Fix Version/s: 1.0.1

> MesosContainerizerLaunch flags execute arbitrary commands via shell.
> 
>
> Key: MESOS-5388
> URL: https://issues.apache.org/jira/browse/MESOS-5388
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Affects Versions: 1.0.0
>Reporter: James DeFelice
>Assignee: Gilbert Song
>  Labels: containerizer, isolator, mesosphere, security
> Fix For: 1.0.1
>
>
> For example, the docker volume isolator's containerPath is appended (without 
> sanitation) to a command that's executed in this manner. As such, it's 
> possible to inject arbitrary shell commands to be executed by mesos.
> https://github.com/apache/mesos/blob/17260204c833c643adf3d8f36ad8a1a606ece809/src/slave/containerizer/mesos/launch.cpp#L206
> Perhaps instead of strings these commands could/should be sent as string 
> arrays that could be passed as argv arguments w/o shell interpretation?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5388) MesosContainerizerLaunch flags execute arbitrary commands via shell.

[Gilbert Song (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405039#comment-15405039
 ] 

Gilbert Song commented on MESOS-5388:
-

commit 9c77899431f8e414f5965a424888a889f6327135
Author: Gilbert Song 
Date:   Tue Aug 2 15:21:38 2016 -0700

Removed unused user variable in filesystem linux isolator prepare.

Review: https://reviews.apache.org/r/50580/

commit 9579a298d1b3e38d9e70261ebe2c893893282d72
Author: Gilbert Song 
Date:   Tue Aug 2 15:46:31 2016 -0700

Added logs for pre-exec commands to sandbox in MesosContainerizerLaunch.

Review: https://reviews.apache.org/r/50581/

> MesosContainerizerLaunch flags execute arbitrary commands via shell.
> 
>
> Key: MESOS-5388
> URL: https://issues.apache.org/jira/browse/MESOS-5388
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Reporter: James DeFelice
>Assignee: Gilbert Song
>  Labels: mesosphere, security
>
> For example, the docker volume isolator's containerPath is appended (without 
> sanitation) to a command that's executed in this manner. As such, it's 
> possible to inject arbitrary shell commands to be executed by mesos.
> https://github.com/apache/mesos/blob/17260204c833c643adf3d8f36ad8a1a606ece809/src/slave/containerizer/mesos/launch.cpp#L206
> Perhaps instead of strings these commands could/should be sent as string 
> arrays that could be passed as argv arguments w/o shell interpretation?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5927) Unable to run "scratch" Dockerfiles with Unified Containerizer.

[Gilbert Song (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gilbert Song updated MESOS-5927:

Summary: Unable to run "scratch" Dockerfiles with Unified Containerizer.  
(was: Unable to run "scratch" Dockerfiles with Unified Containerizer)

> Unable to run "scratch" Dockerfiles with Unified Containerizer.
> ---
>
> Key: MESOS-5927
> URL: https://issues.apache.org/jira/browse/MESOS-5927
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Affects Versions: 1.0.0
>Reporter: Philip Winder
>Assignee: Gilbert Song
>  Labels: containerizer, filesystem, mesosphere
> Fix For: 0.28.3, 1.0.1
>
>
> It is not possible to run Docker containers that are based upon the "scratch" 
> container.
> Setup: Mesos 1.0.0 with the following Mesos settings:
> {code:none}
> echo 'docker' | sudo tee /etc/mesos-slave/image_providers
> echo 'filesystem/linux,docker/runtime' | sudo tee /etc/mesos-slave/isolation
> {code}
> Recreate: From a Master or Slave, run:
> {code:none}
> mesos-execute --command='echo ok' --docker_image=hello-seattle 
> --master=localhost:5050 --name=test
> {code}
> Effect: The container will crash with messages from Mesos reporting it can't 
> mount folder x/y/z. E.g. can't mount /tmp. This means you can't run any 
> container that is not a "fat" container (i.e. one with a full OS). E.g. 
> error: 
> bq. Failed to enter chroot 
> '/var/lib/mesos/provisioner/containers/fed6add8-0126-40e6-ae81-5859a0c1a2d4/backends/copy/rootfses/4feefc8b-fd5a-4835-95db-165e675f11cd':
>  /tmp in chroot does not existI0729 07:49:56.753474  4362 exec.cpp:413] 
> Executor asked to shutdown
> Expected: Run without issues.
> Use case: We use scratch based containers with static binaries to keep the 
> image size down. This is a common practice.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5972) SharedResourcesTest failing on macOS

[Yan Xu (JIRA)]

Yan Xu created MESOS-5972:
-

 Summary: SharedResourcesTest failing on macOS
 Key: MESOS-5972
 URL: https://issues.apache.org/jira/browse/MESOS-5972
 Project: Mesos
  Issue Type: Bug
  Components: tests
Affects Versions: 1.1.0
 Environment: $ g++ --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 7.0.2 (clang-700.1.81)
Target: x86_64-apple-darwin14.5.0
Thread model: posix
Reporter: Yan Xu


The following consistently fail in the specified environment.

{noformat:title=}
[ RUN  ] SharedResourcesTest.ScalarSubtractionShared
../../src/tests/resources_tests.cpp:2504: Failure
Value of: (r2 - r1).count(disk)
  Actual: 18446744073709551615
Expected: 0u
Which is: 0
[  FAILED  ] SharedResourcesTest.ScalarSubtractionShared (0 ms)
[ RUN  ] SharedResourcesTest.ScalarSharedCompoundExpressions
../../src/tests/resources_tests.cpp:2527: Failure
Value of: r1
  Actual: { cpus(*):2, mem(*):10, disk(role1)[1:path]:50<4> }
Expected: r2 - r1 + r1
Which is: { disk(role1)[1:path]:50<3>, cpus(*):2, mem(*):10 }
../../src/tests/resources_tests.cpp:2531: Failure
Value of: (r2 - r1).empty()
  Actual: false
Expected: true
[  FAILED  ] SharedResourcesTest.ScalarSharedCompoundExpressions (0 ms)
{noformat}

/cc [~kaysoky]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5388) MesosContainerizerLaunch flags execute arbitrary commands via shell.

[Gilbert Song (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gilbert Song updated MESOS-5388:

Summary: MesosContainerizerLaunch flags execute arbitrary commands via 
shell.  (was: MesosContainerizerLaunch flags execute arbitrary commands via 
shell)

> MesosContainerizerLaunch flags execute arbitrary commands via shell.
> 
>
> Key: MESOS-5388
> URL: https://issues.apache.org/jira/browse/MESOS-5388
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Reporter: James DeFelice
>Assignee: Gilbert Song
>  Labels: mesosphere, security
>
> For example, the docker volume isolator's containerPath is appended (without 
> sanitation) to a command that's executed in this manner. As such, it's 
> possible to inject arbitrary shell commands to be executed by mesos.
> https://github.com/apache/mesos/blob/17260204c833c643adf3d8f36ad8a1a606ece809/src/slave/containerizer/mesos/launch.cpp#L206
> Perhaps instead of strings these commands could/should be sent as string 
> arrays that could be passed as argv arguments w/o shell interpretation?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MESOS-5388) MesosContainerizerLaunch flags execute arbitrary commands via shell

[Gilbert Song (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386938#comment-15386938
 ] 

Gilbert Song edited comment on MESOS-5388 at 8/2/16 10:47 PM:
--

https://reviews.apache.org/r/50215/
https://reviews.apache.org/r/50214/
https://reviews.apache.org/r/50534/
https://reviews.apache.org/r/50535/
https://reviews.apache.org/r/50216/
https://reviews.apache.org/r/50580/
https://reviews.apache.org/r/50581/


was (Author: gilbert):
https://reviews.apache.org/r/50214/
https://reviews.apache.org/r/50215/
https://reviews.apache.org/r/50216/

> MesosContainerizerLaunch flags execute arbitrary commands via shell
> ---
>
> Key: MESOS-5388
> URL: https://issues.apache.org/jira/browse/MESOS-5388
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Reporter: James DeFelice
>Assignee: Gilbert Song
>  Labels: mesosphere, security
>
> For example, the docker volume isolator's containerPath is appended (without 
> sanitation) to a command that's executed in this manner. As such, it's 
> possible to inject arbitrary shell commands to be executed by mesos.
> https://github.com/apache/mesos/blob/17260204c833c643adf3d8f36ad8a1a606ece809/src/slave/containerizer/mesos/launch.cpp#L206
> Perhaps instead of strings these commands could/should be sent as string 
> arrays that could be passed as argv arguments w/o shell interpretation?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5971) Better handling for docker credentials

[Michael Gummelt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Gummelt updated MESOS-5971:
---
Component/s: docker
 containerization

> Better handling for docker credentials
> --
>
> Key: MESOS-5971
> URL: https://issues.apache.org/jira/browse/MESOS-5971
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization, docker
>Affects Versions: 1.0.0
>Reporter: Michael Gummelt
>
> Users often want to run Spark jobs in custom docker images that reside in 
> private registries.  We can adapt the marathon approach of passing docker 
> configs as fetcher URIs: 
> https://mesosphere.github.io/marathon/docs/native-docker-private-registry.html
> But this is a hack.  It would be nice if I could configure a mesos agent with 
> docker credentials beforehand.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5913) Stale socket FD usage when using libevent + SSL.

[Benjamin Mahler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Mahler updated MESOS-5913:
---
Affects Version/s: 0.27.3

> Stale socket FD usage when using libevent + SSL.
> 
>
> Key: MESOS-5913
> URL: https://issues.apache.org/jira/browse/MESOS-5913
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Affects Versions: 0.27.3, 0.28.2, 1.0.0
>Reporter: Benjamin Mahler
>Assignee: Benjamin Mahler
>Priority: Blocker
> Fix For: 0.28.3, 1.0.1, 0.27.4
>
>
> [~jgehrcke] reported seeing garbage data being sent on sockets when hitting 
> the master or agents with a lot of HTTP requests.
> I was able to reproduce this locally by running HTTP requests while hammering 
> the code with HTTPS requests.
> Looking at the code, it appears that accepted SSL sockets may be used after 
> they are closed (see 
> [here|https://github.com/apache/mesos/blob/dbc5a19149655cde2b76dca4af73c4a7b22529dd/3rdparty/libprocess/src/libevent_ssl_socket.cpp#L94-L156]).
> This code may call {{SSL_shutdown}} after {{Socket::~Impl}} closes the fd. 
> This means that if the fd is re-used, we may accidentally write a TLS Alert 
> message to the re-used fd.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5971) Better handling for docker credentials

[Michael Gummelt (JIRA)]

Michael Gummelt created MESOS-5971:
--

 Summary: Better handling for docker credentials
 Key: MESOS-5971
 URL: https://issues.apache.org/jira/browse/MESOS-5971
 Project: Mesos
  Issue Type: Improvement
Affects Versions: 1.0.0
Reporter: Michael Gummelt


Users often want to run Spark jobs in custom docker images that reside in 
private registries.  We can adapt the marathon approach of passing docker 
configs as fetcher URIs: 
https://mesosphere.github.io/marathon/docs/native-docker-private-registry.html

But this is a hack.  It would be nice if I could configure a mesos agent with 
docker credentials beforehand.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5913) Stale socket FD usage when using libevent + SSL.

[Benjamin Mahler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Mahler updated MESOS-5913:
---
Fix Version/s: 0.27.4

> Stale socket FD usage when using libevent + SSL.
> 
>
> Key: MESOS-5913
> URL: https://issues.apache.org/jira/browse/MESOS-5913
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Affects Versions: 0.27.3, 0.28.2, 1.0.0
>Reporter: Benjamin Mahler
>Assignee: Benjamin Mahler
>Priority: Blocker
> Fix For: 0.28.3, 1.0.1, 0.27.4
>
>
> [~jgehrcke] reported seeing garbage data being sent on sockets when hitting 
> the master or agents with a lot of HTTP requests.
> I was able to reproduce this locally by running HTTP requests while hammering 
> the code with HTTPS requests.
> Looking at the code, it appears that accepted SSL sockets may be used after 
> they are closed (see 
> [here|https://github.com/apache/mesos/blob/dbc5a19149655cde2b76dca4af73c4a7b22529dd/3rdparty/libprocess/src/libevent_ssl_socket.cpp#L94-L156]).
> This code may call {{SSL_shutdown}} after {{Socket::~Impl}} closes the fd. 
> This means that if the fd is re-used, we may accidentally write a TLS Alert 
> message to the re-used fd.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5913) Stale socket FD usage when using libevent + SSL.

[Benjamin Mahler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Mahler updated MESOS-5913:
---
Affects Version/s: 0.28.2
   1.0.0

> Stale socket FD usage when using libevent + SSL.
> 
>
> Key: MESOS-5913
> URL: https://issues.apache.org/jira/browse/MESOS-5913
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Affects Versions: 0.28.2, 1.0.0
>Reporter: Benjamin Mahler
>Assignee: Benjamin Mahler
>Priority: Blocker
> Fix For: 0.28.3, 1.0.1
>
>
> [~jgehrcke] reported seeing garbage data being sent on sockets when hitting 
> the master or agents with a lot of HTTP requests.
> I was able to reproduce this locally by running HTTP requests while hammering 
> the code with HTTPS requests.
> Looking at the code, it appears that accepted SSL sockets may be used after 
> they are closed (see 
> [here|https://github.com/apache/mesos/blob/dbc5a19149655cde2b76dca4af73c4a7b22529dd/3rdparty/libprocess/src/libevent_ssl_socket.cpp#L94-L156]).
> This code may call {{SSL_shutdown}} after {{Socket::~Impl}} closes the fd. 
> This means that if the fd is re-used, we may accidentally write a TLS Alert 
> message to the re-used fd.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5913) Stale socket FD usage when using libevent + SSL.

[Benjamin Mahler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Mahler updated MESOS-5913:
---
Fix Version/s: 0.28.3

> Stale socket FD usage when using libevent + SSL.
> 
>
> Key: MESOS-5913
> URL: https://issues.apache.org/jira/browse/MESOS-5913
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Reporter: Benjamin Mahler
>Assignee: Benjamin Mahler
>Priority: Blocker
> Fix For: 0.28.3, 1.0.1
>
>
> [~jgehrcke] reported seeing garbage data being sent on sockets when hitting 
> the master or agents with a lot of HTTP requests.
> I was able to reproduce this locally by running HTTP requests while hammering 
> the code with HTTPS requests.
> Looking at the code, it appears that accepted SSL sockets may be used after 
> they are closed (see 
> [here|https://github.com/apache/mesos/blob/dbc5a19149655cde2b76dca4af73c4a7b22529dd/3rdparty/libprocess/src/libevent_ssl_socket.cpp#L94-L156]).
> This code may call {{SSL_shutdown}} after {{Socket::~Impl}} closes the fd. 
> This means that if the fd is re-used, we may accidentally write a TLS Alert 
> message to the re-used fd.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MESOS-5943) Incremental http parsing of URLs leads to decoder error

[Joris Van Remoortere (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404647#comment-15404647
 ] 

Joris Van Remoortere edited comment on MESOS-5943 at 8/2/16 9:05 PM:
-

{code}
commit 2776a09cbcd836080241a5ad8c1e003984e5a146
Author: Joris Van Remoortere 
Date:   Sat Jul 30 12:58:28 2016 -0700

Libprocess: Fixed decoder to support incremental URL parsing.

Review: https://reviews.apache.org/r/50634
{code}


was (Author: jvanremoortere):
{code}
commit f291d5023e9f2e471c11d4f20590901d9bfc1de4
Author: Joris Van Remoortere 
Date:   Mon Aug 1 17:14:37 2016 -0700

Libprocess: Removed old http_parser code.

We remove the code that supported the `HTTP_PARSER_VERSION_MAJOR` < 2
path.

Review: https://reviews.apache.org/r/50683

commit 2776a09cbcd836080241a5ad8c1e003984e5a146
Author: Joris Van Remoortere 
Date:   Sat Jul 30 12:58:28 2016 -0700

Libprocess: Fixed decoder to support incremental URL parsing.

Review: https://reviews.apache.org/r/50634
{code}

> Incremental http parsing of URLs leads to decoder error
> ---
>
> Key: MESOS-5943
> URL: https://issues.apache.org/jira/browse/MESOS-5943
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess, scheduler driver
>Affects Versions: 1.0.0
>Reporter: Joris Van Remoortere
>Assignee: Joris Van Remoortere
>Priority: Blocker
>  Labels: mesosphere
> Fix For: 0.28.3, 1.0.1, 0.27.4
>
>
> When requests arrive to the decoder in pieces (e.g. {{mes}} followed by a 
> separate chunk of {{os.apache.org}}) the http parser is not able to handle 
> this case if the split is within the URL component.
> This causes the decoder to error out, and can lead to connection invalidation.
> The scheduler driver is susceptible to this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5970) Remove HTTP_PARSER_VERSION_MAJOR < 2 code in decoder.

[Joris Van Remoortere (JIRA)]

Joris Van Remoortere created MESOS-5970:
---

 Summary: Remove HTTP_PARSER_VERSION_MAJOR < 2 code in decoder.
 Key: MESOS-5970
 URL: https://issues.apache.org/jira/browse/MESOS-5970
 Project: Mesos
  Issue Type: Task
  Components: libprocess
Reporter: Joris Van Remoortere
Assignee: Joris Van Remoortere
 Fix For: 1.0.1, 1.1.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (MESOS-5943) Incremental http parsing of URLs leads to decoder error

[Joris Van Remoortere (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404647#comment-15404647
 ] 

Joris Van Remoortere edited comment on MESOS-5943 at 8/2/16 9:03 PM:
-

{code}
commit f291d5023e9f2e471c11d4f20590901d9bfc1de4
Author: Joris Van Remoortere 
Date:   Mon Aug 1 17:14:37 2016 -0700

Libprocess: Removed old http_parser code.

We remove the code that supported the `HTTP_PARSER_VERSION_MAJOR` < 2
path.

Review: https://reviews.apache.org/r/50683

commit 2776a09cbcd836080241a5ad8c1e003984e5a146
Author: Joris Van Remoortere 
Date:   Sat Jul 30 12:58:28 2016 -0700

Libprocess: Fixed decoder to support incremental URL parsing.

Review: https://reviews.apache.org/r/50634
{code}


was (Author: jvanremoortere):
{code}
commit f291d5023e9f2e471c11d4f20590901d9bfc1de4
Author: Joris Van Remoortere 
Date:   Mon Aug 1 17:14:37 2016 -0700

Libprocess: Removed old http_parser code.

We remove the code that supported the `HTTP_PARSER_VERSION_MAJOR` < 2
path.

Review: https://reviews.apache.org/r/50683

commit 2776a09cbcd836080241a5ad8c1e003984e5a146
Author: Joris Van Remoortere 
Date:   Sat Jul 30 12:58:28 2016 -0700

Libprocess: Fixed decoder to support incremental URL parsing.

Review: https://reviews.apache.org/r/50634
{code}

> Incremental http parsing of URLs leads to decoder error
> ---
>
> Key: MESOS-5943
> URL: https://issues.apache.org/jira/browse/MESOS-5943
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess, scheduler driver
>Affects Versions: 1.0.0
>Reporter: Joris Van Remoortere
>Assignee: Joris Van Remoortere
>Priority: Blocker
>  Labels: mesosphere
> Fix For: 0.28.3, 1.0.1, 0.27.4
>
>
> When requests arrive to the decoder in pieces (e.g. {{mes}} followed by a 
> separate chunk of {{os.apache.org}}) the http parser is not able to handle 
> this case if the split is within the URL component.
> This causes the decoder to error out, and can lead to connection invalidation.
> The scheduler driver is susceptible to this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5943) Incremental http parsing of URLs leads to decoder error

[Joris Van Remoortere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joris Van Remoortere updated MESOS-5943:

Fix Version/s: 0.27.4
   0.28.3

> Incremental http parsing of URLs leads to decoder error
> ---
>
> Key: MESOS-5943
> URL: https://issues.apache.org/jira/browse/MESOS-5943
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess, scheduler driver
>Affects Versions: 1.0.0
>Reporter: Joris Van Remoortere
>Assignee: Joris Van Remoortere
>Priority: Blocker
>  Labels: mesosphere
> Fix For: 0.28.3, 1.0.1, 0.27.4
>
>
> When requests arrive to the decoder in pieces (e.g. {{mes}} followed by a 
> separate chunk of {{os.apache.org}}) the http parser is not able to handle 
> this case if the split is within the URL component.
> This causes the decoder to error out, and can lead to connection invalidation.
> The scheduler driver is susceptible to this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5958) Reviewbot failing due to python files not being cleaned up after distclean

[Joseph Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Wu updated MESOS-5958:
-
  Sprint: Mesosphere Sprint 40
Story Points: 2

> Reviewbot failing due to python files not being cleaned up after distclean
> --
>
> Key: MESOS-5958
> URL: https://issues.apache.org/jira/browse/MESOS-5958
> Project: Mesos
>  Issue Type: Bug
> Environment: ASF CI
>Reporter: Vinod Kone
>Assignee: Joseph Wu
>Priority: Critical
>
> This is on ASF CI. 
> https://builds.apache.org/job/mesos-reviewbot/14573/consoleFull
> {code}
> find python -name "build" -o -name "dist" -o -name "*.pyc"\
> -o -name "*.egg-info" -exec rm -rf '{}' \+
> test -z "libmesos_no_3rdparty.la libbuild.la liblog.la libstate.la libjava.la 
> libexamplemodule.la libtestallocator.la libtestanonymous.la 
> libtestauthentication.la libtestauthorizer.la libtestcontainer_logger.la 
> libtesthook.la libtesthttpauthenticator.la libtestisolator.la 
> libtestmastercontender.la libtestmasterdetector.la libtestqos_controller.la 
> libtestresource_estimator.la" || rm -f libmesos_no_3rdparty.la libbuild.la 
> liblog.la libstate.la libjava.la libexamplemodule.la libtestallocator.la 
> libtestanonymous.la libtestauthentication.la libtestauthorizer.la 
> libtestcontainer_logger.la libtesthook.la libtesthttpauthenticator.la 
> libtestisolator.la libtestmastercontender.la libtestmasterdetector.la 
> libtestqos_controller.la libtestresource_estimator.la
> test -z "liblogrotate_container_logger.la libfixed_resource_estimator.la 
> libload_qos_controller.la " || rm -f liblogrotate_container_logger.la 
> libfixed_resource_estimator.la libload_qos_controller.la 
>  rm -f mesos-fetcher mesos-executor mesos-containerizer 
> mesos-logrotate-logger mesos-health-check mesos-usage mesos-docker-executor
>  rm -f mesos-agent mesos-master mesos-slave
> rm -f ./so_locations
> rm -f *.o
> rm -f *.lo
> rm -f ../include/mesos/*.o
> rm -f ./so_locations
> rm -f *.tab.c
> test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f ./so_locations
> rm -f ../include/mesos/*.lo
> test . = "../../src" || test -z "" || rm -f 
> rm -f ../include/mesos/.deps/.dirstamp
> rm -f ../include/mesos/agent/*.o
> rm -f ../include/mesos/agent/*.lo
> rm -f ../include/mesos/.dirstamp
> rm -f ../include/mesos/allocator/*.o
> rm -f ../include/mesos/agent/.deps/.dirstamp
> rm -f ../include/mesos/allocator/*.lo
> rm -f ../include/mesos/agent/.dirstamp
> rm -f ../include/mesos/appc/*.o
> rm -f ../include/mesos/allocator/.deps/.dirstamp
> rm -f ../include/mesos/appc/*.lo
> rm -f ../include/mesos/allocator/.dirstamp
> rm -f ../include/mesos/authentication/*.o
> rm -f ../include/mesos/appc/.deps/.dirstamp
> rm -f ../include/mesos/authentication/*.lo
> rm -f ../include/mesos/appc/.dirstamp
> rm -f ../include/mesos/authorizer/*.o
> rm -f ../include/mesos/authentication/.deps/.dirstamp
> rm -f ../include/mesos/authorizer/*.lo
> rm -f ../include/mesos/authentication/.dirstamp
> rm -f ../include/mesos/containerizer/*.o
> rm -f ../include/mesos/authorizer/.deps/.dirstamp
> rm -f ../include/mesos/containerizer/*.lo
> rm -f ../include/mesos/authorizer/.dirstamp
> rm -f ../include/mesos/docker/*.o
> rm -f ../include/mesos/containerizer/.deps/.dirstamp
> rm -f ../include/mesos/docker/*.lo
> rm: cannot remove 'python/cli/build': Is a directory
> rm: cannot remove 'python/executor/build': Is a directory
> rm: cannot remove 'python/interface/build': Is a directory
> rm: cannot remove 'python/native/build': Is a directory
> rm: cannot remove 'python/scheduler/build': Is a directory
> rm -f ../include/mesos/containerizer/.dirstamp
> make[2]: [clean-generic] Error 1 (ignored)
> rm -f ../include/mesos/executor/*.o
> rm -f ../include/mesos/docker/.deps/.dirstamp
> rm -f ../include/mesos/executor/*.lo
> rm -f ../include/mesos/docker/.dirstamp
> rm -f ../include/mesos/fetcher/*.o
> rm -f ../include/mesos/executor/.deps/.dirstamp
> rm -f ../include/mesos/fetcher/*.lo
> rm -f ../include/mesos/executor/.dirstamp
> rm -f ../include/mesos/maintenance/*.o
> rm -f ../include/mesos/fetcher/.deps/.dirstamp
> rm -f ../include/mesos/maintenance/*.lo
> rm -f ../include/mesos/fetcher/.dirstamp
> rm -f ../include/mesos/master/*.o
> rm -f ../include/mesos/maintenance/.deps/.dirstamp
> rm -f ../include/mesos/master/*.lo
> rm -f ../include/mesos/module/*.o
> rm -f ../include/mesos/maintenance/.dirstamp
> rm -f ../include/mesos/module/*.lo
> rm -f ../include/mesos/master/.deps/.dirstamp
> rm -f ../include/mesos/master/.dirstamp
> rm -f ../include/mesos/quota/*.o
> rm -f ../include/mesos/module/.deps/.dirstamp
> rm -f ../include/mesos/quota/*.lo
> rm -f ../include/mesos/module/.dirstamp
> rm -f ../include/mesos/scheduler/*.o
> rm -f 

[jira] [Assigned] (MESOS-5958) Reviewbot failing due to python files not being cleaned up after distclean

[Joseph Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Wu reassigned MESOS-5958:


Assignee: Joseph Wu

> Reviewbot failing due to python files not being cleaned up after distclean
> --
>
> Key: MESOS-5958
> URL: https://issues.apache.org/jira/browse/MESOS-5958
> Project: Mesos
>  Issue Type: Bug
> Environment: ASF CI
>Reporter: Vinod Kone
>Assignee: Joseph Wu
>Priority: Critical
>
> This is on ASF CI. 
> https://builds.apache.org/job/mesos-reviewbot/14573/consoleFull
> {code}
> find python -name "build" -o -name "dist" -o -name "*.pyc"\
> -o -name "*.egg-info" -exec rm -rf '{}' \+
> test -z "libmesos_no_3rdparty.la libbuild.la liblog.la libstate.la libjava.la 
> libexamplemodule.la libtestallocator.la libtestanonymous.la 
> libtestauthentication.la libtestauthorizer.la libtestcontainer_logger.la 
> libtesthook.la libtesthttpauthenticator.la libtestisolator.la 
> libtestmastercontender.la libtestmasterdetector.la libtestqos_controller.la 
> libtestresource_estimator.la" || rm -f libmesos_no_3rdparty.la libbuild.la 
> liblog.la libstate.la libjava.la libexamplemodule.la libtestallocator.la 
> libtestanonymous.la libtestauthentication.la libtestauthorizer.la 
> libtestcontainer_logger.la libtesthook.la libtesthttpauthenticator.la 
> libtestisolator.la libtestmastercontender.la libtestmasterdetector.la 
> libtestqos_controller.la libtestresource_estimator.la
> test -z "liblogrotate_container_logger.la libfixed_resource_estimator.la 
> libload_qos_controller.la " || rm -f liblogrotate_container_logger.la 
> libfixed_resource_estimator.la libload_qos_controller.la 
>  rm -f mesos-fetcher mesos-executor mesos-containerizer 
> mesos-logrotate-logger mesos-health-check mesos-usage mesos-docker-executor
>  rm -f mesos-agent mesos-master mesos-slave
> rm -f ./so_locations
> rm -f *.o
> rm -f *.lo
> rm -f ../include/mesos/*.o
> rm -f ./so_locations
> rm -f *.tab.c
> test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f ./so_locations
> rm -f ../include/mesos/*.lo
> test . = "../../src" || test -z "" || rm -f 
> rm -f ../include/mesos/.deps/.dirstamp
> rm -f ../include/mesos/agent/*.o
> rm -f ../include/mesos/agent/*.lo
> rm -f ../include/mesos/.dirstamp
> rm -f ../include/mesos/allocator/*.o
> rm -f ../include/mesos/agent/.deps/.dirstamp
> rm -f ../include/mesos/allocator/*.lo
> rm -f ../include/mesos/agent/.dirstamp
> rm -f ../include/mesos/appc/*.o
> rm -f ../include/mesos/allocator/.deps/.dirstamp
> rm -f ../include/mesos/appc/*.lo
> rm -f ../include/mesos/allocator/.dirstamp
> rm -f ../include/mesos/authentication/*.o
> rm -f ../include/mesos/appc/.deps/.dirstamp
> rm -f ../include/mesos/authentication/*.lo
> rm -f ../include/mesos/appc/.dirstamp
> rm -f ../include/mesos/authorizer/*.o
> rm -f ../include/mesos/authentication/.deps/.dirstamp
> rm -f ../include/mesos/authorizer/*.lo
> rm -f ../include/mesos/authentication/.dirstamp
> rm -f ../include/mesos/containerizer/*.o
> rm -f ../include/mesos/authorizer/.deps/.dirstamp
> rm -f ../include/mesos/containerizer/*.lo
> rm -f ../include/mesos/authorizer/.dirstamp
> rm -f ../include/mesos/docker/*.o
> rm -f ../include/mesos/containerizer/.deps/.dirstamp
> rm -f ../include/mesos/docker/*.lo
> rm: cannot remove 'python/cli/build': Is a directory
> rm: cannot remove 'python/executor/build': Is a directory
> rm: cannot remove 'python/interface/build': Is a directory
> rm: cannot remove 'python/native/build': Is a directory
> rm: cannot remove 'python/scheduler/build': Is a directory
> rm -f ../include/mesos/containerizer/.dirstamp
> make[2]: [clean-generic] Error 1 (ignored)
> rm -f ../include/mesos/executor/*.o
> rm -f ../include/mesos/docker/.deps/.dirstamp
> rm -f ../include/mesos/executor/*.lo
> rm -f ../include/mesos/docker/.dirstamp
> rm -f ../include/mesos/fetcher/*.o
> rm -f ../include/mesos/executor/.deps/.dirstamp
> rm -f ../include/mesos/fetcher/*.lo
> rm -f ../include/mesos/executor/.dirstamp
> rm -f ../include/mesos/maintenance/*.o
> rm -f ../include/mesos/fetcher/.deps/.dirstamp
> rm -f ../include/mesos/maintenance/*.lo
> rm -f ../include/mesos/fetcher/.dirstamp
> rm -f ../include/mesos/master/*.o
> rm -f ../include/mesos/maintenance/.deps/.dirstamp
> rm -f ../include/mesos/master/*.lo
> rm -f ../include/mesos/module/*.o
> rm -f ../include/mesos/maintenance/.dirstamp
> rm -f ../include/mesos/module/*.lo
> rm -f ../include/mesos/master/.deps/.dirstamp
> rm -f ../include/mesos/master/.dirstamp
> rm -f ../include/mesos/quota/*.o
> rm -f ../include/mesos/module/.deps/.dirstamp
> rm -f ../include/mesos/quota/*.lo
> rm -f ../include/mesos/module/.dirstamp
> rm -f ../include/mesos/scheduler/*.o
> rm -f ../include/mesos/quota/.deps/.dirstamp
> rm -f 

[jira] [Created] (MESOS-5969) Linux 'MountTable' not sorted as expected

[Kevin Klues (JIRA)]

Kevin Klues created MESOS-5969:
--

 Summary: Linux 'MountTable' not sorted as expected
 Key: MESOS-5969
 URL: https://issues.apache.org/jira/browse/MESOS-5969
 Project: Mesos
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Kevin Klues
Assignee: Kevin Klues
 Fix For: 1.0.1


Many places in the codebase assume that the mount table is sorted according to 
the order: {{parent mount point < child mount point}}.

However, in some cases this may not be true if (for example), a parent mount 
point (say {{/}}) is remounted to add some extra flags to it.  When this 
happens, the remounted file system will appear in the mount table at the point 
where it was remounted.

We actually encountered this problem in the wild for the case of {{/}} being 
remounted after {{/run}} was mounted -- causing problems in the 
{{NvidiaVolume}} which assumes the {{parent  < child}} ordering.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5958) Reviewbot failing due to python files not being cleaned up after distclean

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404551#comment-15404551
 ] 

ASF GitHub Bot commented on MESOS-5958:
---

Github user vinodkone commented on the issue:

https://github.com/apache/mesos/pull/36
  
I think this broke the ReviewBot. See 
https://issues.apache.org/jira/browse/MESOS-5958


> Reviewbot failing due to python files not being cleaned up after distclean
> --
>
> Key: MESOS-5958
> URL: https://issues.apache.org/jira/browse/MESOS-5958
> Project: Mesos
>  Issue Type: Bug
> Environment: ASF CI
>Reporter: Vinod Kone
>Priority: Critical
>
> This is on ASF CI. 
> https://builds.apache.org/job/mesos-reviewbot/14573/consoleFull
> {code}
> find python -name "build" -o -name "dist" -o -name "*.pyc"\
> -o -name "*.egg-info" -exec rm -rf '{}' \+
> test -z "libmesos_no_3rdparty.la libbuild.la liblog.la libstate.la libjava.la 
> libexamplemodule.la libtestallocator.la libtestanonymous.la 
> libtestauthentication.la libtestauthorizer.la libtestcontainer_logger.la 
> libtesthook.la libtesthttpauthenticator.la libtestisolator.la 
> libtestmastercontender.la libtestmasterdetector.la libtestqos_controller.la 
> libtestresource_estimator.la" || rm -f libmesos_no_3rdparty.la libbuild.la 
> liblog.la libstate.la libjava.la libexamplemodule.la libtestallocator.la 
> libtestanonymous.la libtestauthentication.la libtestauthorizer.la 
> libtestcontainer_logger.la libtesthook.la libtesthttpauthenticator.la 
> libtestisolator.la libtestmastercontender.la libtestmasterdetector.la 
> libtestqos_controller.la libtestresource_estimator.la
> test -z "liblogrotate_container_logger.la libfixed_resource_estimator.la 
> libload_qos_controller.la " || rm -f liblogrotate_container_logger.la 
> libfixed_resource_estimator.la libload_qos_controller.la 
>  rm -f mesos-fetcher mesos-executor mesos-containerizer 
> mesos-logrotate-logger mesos-health-check mesos-usage mesos-docker-executor
>  rm -f mesos-agent mesos-master mesos-slave
> rm -f ./so_locations
> rm -f *.o
> rm -f *.lo
> rm -f ../include/mesos/*.o
> rm -f ./so_locations
> rm -f *.tab.c
> test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f ./so_locations
> rm -f ../include/mesos/*.lo
> test . = "../../src" || test -z "" || rm -f 
> rm -f ../include/mesos/.deps/.dirstamp
> rm -f ../include/mesos/agent/*.o
> rm -f ../include/mesos/agent/*.lo
> rm -f ../include/mesos/.dirstamp
> rm -f ../include/mesos/allocator/*.o
> rm -f ../include/mesos/agent/.deps/.dirstamp
> rm -f ../include/mesos/allocator/*.lo
> rm -f ../include/mesos/agent/.dirstamp
> rm -f ../include/mesos/appc/*.o
> rm -f ../include/mesos/allocator/.deps/.dirstamp
> rm -f ../include/mesos/appc/*.lo
> rm -f ../include/mesos/allocator/.dirstamp
> rm -f ../include/mesos/authentication/*.o
> rm -f ../include/mesos/appc/.deps/.dirstamp
> rm -f ../include/mesos/authentication/*.lo
> rm -f ../include/mesos/appc/.dirstamp
> rm -f ../include/mesos/authorizer/*.o
> rm -f ../include/mesos/authentication/.deps/.dirstamp
> rm -f ../include/mesos/authorizer/*.lo
> rm -f ../include/mesos/authentication/.dirstamp
> rm -f ../include/mesos/containerizer/*.o
> rm -f ../include/mesos/authorizer/.deps/.dirstamp
> rm -f ../include/mesos/containerizer/*.lo
> rm -f ../include/mesos/authorizer/.dirstamp
> rm -f ../include/mesos/docker/*.o
> rm -f ../include/mesos/containerizer/.deps/.dirstamp
> rm -f ../include/mesos/docker/*.lo
> rm: cannot remove 'python/cli/build': Is a directory
> rm: cannot remove 'python/executor/build': Is a directory
> rm: cannot remove 'python/interface/build': Is a directory
> rm: cannot remove 'python/native/build': Is a directory
> rm: cannot remove 'python/scheduler/build': Is a directory
> rm -f ../include/mesos/containerizer/.dirstamp
> make[2]: [clean-generic] Error 1 (ignored)
> rm -f ../include/mesos/executor/*.o
> rm -f ../include/mesos/docker/.deps/.dirstamp
> rm -f ../include/mesos/executor/*.lo
> rm -f ../include/mesos/docker/.dirstamp
> rm -f ../include/mesos/fetcher/*.o
> rm -f ../include/mesos/executor/.deps/.dirstamp
> rm -f ../include/mesos/fetcher/*.lo
> rm -f ../include/mesos/executor/.dirstamp
> rm -f ../include/mesos/maintenance/*.o
> rm -f ../include/mesos/fetcher/.deps/.dirstamp
> rm -f ../include/mesos/maintenance/*.lo
> rm -f ../include/mesos/fetcher/.dirstamp
> rm -f ../include/mesos/master/*.o
> rm -f ../include/mesos/maintenance/.deps/.dirstamp
> rm -f ../include/mesos/master/*.lo
> rm -f ../include/mesos/module/*.o
> rm -f ../include/mesos/maintenance/.dirstamp
> rm -f ../include/mesos/module/*.lo
> rm -f ../include/mesos/master/.deps/.dirstamp
> rm -f ../include/mesos/master/.dirstamp
> rm -f ../include/mesos/quota/*.o
> rm -f ../include/mesos/module/.deps/.dirstamp

[jira] [Updated] (MESOS-5958) Reviewbot failing due to python files not being cleaned up after distclean

[Vinod Kone (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kone updated MESOS-5958:
--
Priority: Critical  (was: Major)

> Reviewbot failing due to python files not being cleaned up after distclean
> --
>
> Key: MESOS-5958
> URL: https://issues.apache.org/jira/browse/MESOS-5958
> Project: Mesos
>  Issue Type: Bug
> Environment: ASF CI
>Reporter: Vinod Kone
>Priority: Critical
>
> This is on ASF CI. 
> https://builds.apache.org/job/mesos-reviewbot/14573/consoleFull
> {code}
> find python -name "build" -o -name "dist" -o -name "*.pyc"\
> -o -name "*.egg-info" -exec rm -rf '{}' \+
> test -z "libmesos_no_3rdparty.la libbuild.la liblog.la libstate.la libjava.la 
> libexamplemodule.la libtestallocator.la libtestanonymous.la 
> libtestauthentication.la libtestauthorizer.la libtestcontainer_logger.la 
> libtesthook.la libtesthttpauthenticator.la libtestisolator.la 
> libtestmastercontender.la libtestmasterdetector.la libtestqos_controller.la 
> libtestresource_estimator.la" || rm -f libmesos_no_3rdparty.la libbuild.la 
> liblog.la libstate.la libjava.la libexamplemodule.la libtestallocator.la 
> libtestanonymous.la libtestauthentication.la libtestauthorizer.la 
> libtestcontainer_logger.la libtesthook.la libtesthttpauthenticator.la 
> libtestisolator.la libtestmastercontender.la libtestmasterdetector.la 
> libtestqos_controller.la libtestresource_estimator.la
> test -z "liblogrotate_container_logger.la libfixed_resource_estimator.la 
> libload_qos_controller.la " || rm -f liblogrotate_container_logger.la 
> libfixed_resource_estimator.la libload_qos_controller.la 
>  rm -f mesos-fetcher mesos-executor mesos-containerizer 
> mesos-logrotate-logger mesos-health-check mesos-usage mesos-docker-executor
>  rm -f mesos-agent mesos-master mesos-slave
> rm -f ./so_locations
> rm -f *.o
> rm -f *.lo
> rm -f ../include/mesos/*.o
> rm -f ./so_locations
> rm -f *.tab.c
> test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f ./so_locations
> rm -f ../include/mesos/*.lo
> test . = "../../src" || test -z "" || rm -f 
> rm -f ../include/mesos/.deps/.dirstamp
> rm -f ../include/mesos/agent/*.o
> rm -f ../include/mesos/agent/*.lo
> rm -f ../include/mesos/.dirstamp
> rm -f ../include/mesos/allocator/*.o
> rm -f ../include/mesos/agent/.deps/.dirstamp
> rm -f ../include/mesos/allocator/*.lo
> rm -f ../include/mesos/agent/.dirstamp
> rm -f ../include/mesos/appc/*.o
> rm -f ../include/mesos/allocator/.deps/.dirstamp
> rm -f ../include/mesos/appc/*.lo
> rm -f ../include/mesos/allocator/.dirstamp
> rm -f ../include/mesos/authentication/*.o
> rm -f ../include/mesos/appc/.deps/.dirstamp
> rm -f ../include/mesos/authentication/*.lo
> rm -f ../include/mesos/appc/.dirstamp
> rm -f ../include/mesos/authorizer/*.o
> rm -f ../include/mesos/authentication/.deps/.dirstamp
> rm -f ../include/mesos/authorizer/*.lo
> rm -f ../include/mesos/authentication/.dirstamp
> rm -f ../include/mesos/containerizer/*.o
> rm -f ../include/mesos/authorizer/.deps/.dirstamp
> rm -f ../include/mesos/containerizer/*.lo
> rm -f ../include/mesos/authorizer/.dirstamp
> rm -f ../include/mesos/docker/*.o
> rm -f ../include/mesos/containerizer/.deps/.dirstamp
> rm -f ../include/mesos/docker/*.lo
> rm: cannot remove 'python/cli/build': Is a directory
> rm: cannot remove 'python/executor/build': Is a directory
> rm: cannot remove 'python/interface/build': Is a directory
> rm: cannot remove 'python/native/build': Is a directory
> rm: cannot remove 'python/scheduler/build': Is a directory
> rm -f ../include/mesos/containerizer/.dirstamp
> make[2]: [clean-generic] Error 1 (ignored)
> rm -f ../include/mesos/executor/*.o
> rm -f ../include/mesos/docker/.deps/.dirstamp
> rm -f ../include/mesos/executor/*.lo
> rm -f ../include/mesos/docker/.dirstamp
> rm -f ../include/mesos/fetcher/*.o
> rm -f ../include/mesos/executor/.deps/.dirstamp
> rm -f ../include/mesos/fetcher/*.lo
> rm -f ../include/mesos/executor/.dirstamp
> rm -f ../include/mesos/maintenance/*.o
> rm -f ../include/mesos/fetcher/.deps/.dirstamp
> rm -f ../include/mesos/maintenance/*.lo
> rm -f ../include/mesos/fetcher/.dirstamp
> rm -f ../include/mesos/master/*.o
> rm -f ../include/mesos/maintenance/.deps/.dirstamp
> rm -f ../include/mesos/master/*.lo
> rm -f ../include/mesos/module/*.o
> rm -f ../include/mesos/maintenance/.dirstamp
> rm -f ../include/mesos/module/*.lo
> rm -f ../include/mesos/master/.deps/.dirstamp
> rm -f ../include/mesos/master/.dirstamp
> rm -f ../include/mesos/quota/*.o
> rm -f ../include/mesos/module/.deps/.dirstamp
> rm -f ../include/mesos/quota/*.lo
> rm -f ../include/mesos/module/.dirstamp
> rm -f ../include/mesos/scheduler/*.o
> rm -f ../include/mesos/quota/.deps/.dirstamp
> rm -f 

[jira] [Commented] (MESOS-5958) Reviewbot failing due to python files not being cleaned up after distclean

[Vinod Kone (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404546#comment-15404546
 ] 

Vinod Kone commented on MESOS-5958:
---

I suspect this is the commit that broke it. [~lloesche] can you take a look?

{code}
commit b6e313a0c4335e30d60cb76d11384f4906ec141a
Author: Lukas Loesche 
Date:   Mon Feb 23 11:37:30 2015 +0100

Replaced unsafe `find | xargs` with `find -exec`.

`find | xargs rm -rf` is unsafe if there are files with spaces in the
name:

  $ touch "file with spaces.txt"
  $ find . -name "*.txt" | xargs echo rm -rf
  rm -rf ./file with spaces.txt

The above deletes three files/folders instead of the one file.

This closes #36

diff --git a/src/Makefile.am b/src/Makefile.am
index 3d33ee7..a531a50 100644
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -1825,7 +1825,7 @@ endif # HAS_PYTHON
 
 clean-python:
find python -name "build" -o -name "dist" -o -name "*.pyc"  \
- -o -name "*.egg-info" | xargs rm -rf
+ -o -name "*.egg-info" -exec rm -rf '{}' \+
 
 PHONY_TARGETS += clean-python
 
diff --git a/src/tests/balloon_framework_test.sh 
b/src/tests/balloon_framework_test.sh
index 78d534f..5d013fc 100755
--- a/src/tests/balloon_framework_test.sh
+++ b/src/tests/balloon_framework_test.sh
@@ -46,7 +46,7 @@ function cleanup() {
   fi
 
   # Make sure we cleanup any cgroups we created on exiting.
-  find ${TEST_CGROUP_HIERARCHY}/*/${TEST_CGROUP_ROOT} -mindepth 1 -depth -type 
d | xargs -r rmdir
+  find ${TEST_CGROUP_HIERARCHY}/*/${TEST_CGROUP_ROOT} -mindepth 1 -depth -type 
d -exec rmdir '{}' \+
 
   # Make sure we cleanup the hierarchy, if we created it.
   # NOTE: We do a sleep here, to ensure the hierarchy is not busy.
{code}

> Reviewbot failing due to python files not being cleaned up after distclean
> --
>
> Key: MESOS-5958
> URL: https://issues.apache.org/jira/browse/MESOS-5958
> Project: Mesos
>  Issue Type: Bug
> Environment: ASF CI
>Reporter: Vinod Kone
>
> This is on ASF CI. 
> https://builds.apache.org/job/mesos-reviewbot/14573/consoleFull
> {code}
> find python -name "build" -o -name "dist" -o -name "*.pyc"\
> -o -name "*.egg-info" -exec rm -rf '{}' \+
> test -z "libmesos_no_3rdparty.la libbuild.la liblog.la libstate.la libjava.la 
> libexamplemodule.la libtestallocator.la libtestanonymous.la 
> libtestauthentication.la libtestauthorizer.la libtestcontainer_logger.la 
> libtesthook.la libtesthttpauthenticator.la libtestisolator.la 
> libtestmastercontender.la libtestmasterdetector.la libtestqos_controller.la 
> libtestresource_estimator.la" || rm -f libmesos_no_3rdparty.la libbuild.la 
> liblog.la libstate.la libjava.la libexamplemodule.la libtestallocator.la 
> libtestanonymous.la libtestauthentication.la libtestauthorizer.la 
> libtestcontainer_logger.la libtesthook.la libtesthttpauthenticator.la 
> libtestisolator.la libtestmastercontender.la libtestmasterdetector.la 
> libtestqos_controller.la libtestresource_estimator.la
> test -z "liblogrotate_container_logger.la libfixed_resource_estimator.la 
> libload_qos_controller.la " || rm -f liblogrotate_container_logger.la 
> libfixed_resource_estimator.la libload_qos_controller.la 
>  rm -f mesos-fetcher mesos-executor mesos-containerizer 
> mesos-logrotate-logger mesos-health-check mesos-usage mesos-docker-executor
>  rm -f mesos-agent mesos-master mesos-slave
> rm -f ./so_locations
> rm -f *.o
> rm -f *.lo
> rm -f ../include/mesos/*.o
> rm -f ./so_locations
> rm -f *.tab.c
> test -z "" || rm -f 
> rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> rm -f ./so_locations
> rm -f ../include/mesos/*.lo
> test . = "../../src" || test -z "" || rm -f 
> rm -f ../include/mesos/.deps/.dirstamp
> rm -f ../include/mesos/agent/*.o
> rm -f ../include/mesos/agent/*.lo
> rm -f ../include/mesos/.dirstamp
> rm -f ../include/mesos/allocator/*.o
> rm -f ../include/mesos/agent/.deps/.dirstamp
> rm -f ../include/mesos/allocator/*.lo
> rm -f ../include/mesos/agent/.dirstamp
> rm -f ../include/mesos/appc/*.o
> rm -f ../include/mesos/allocator/.deps/.dirstamp
> rm -f ../include/mesos/appc/*.lo
> rm -f ../include/mesos/allocator/.dirstamp
> rm -f ../include/mesos/authentication/*.o
> rm -f ../include/mesos/appc/.deps/.dirstamp
> rm -f ../include/mesos/authentication/*.lo
> rm -f ../include/mesos/appc/.dirstamp
> rm -f ../include/mesos/authorizer/*.o
> rm -f ../include/mesos/authentication/.deps/.dirstamp
> rm -f ../include/mesos/authorizer/*.lo
> rm -f ../include/mesos/authentication/.dirstamp
> rm -f ../include/mesos/containerizer/*.o
> rm -f ../include/mesos/authorizer/.deps/.dirstamp
> rm -f ../include/mesos/containerizer/*.lo
> rm -f ../include/mesos/authorizer/.dirstamp
> rm -f ../include/mesos/docker/*.o
> rm -f 

[jira] [Commented] (MESOS-5968) Ensure that task IDs are quoted consistently

[Neil Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404487#comment-15404487
 ] 

Neil Conway commented on MESOS-5968:


One approach would be to fixup every place where task IDs are included in log 
messages. A different approach would be to change {{ostream& 
operator<<(ostream& stream, const TaskID& taskId)}} in {{type_utils.cpp}} and 
{{v1/mesos.cpp}} to use single quotes.

> Ensure that task IDs are quoted consistently
> 
>
> Key: MESOS-5968
> URL: https://issues.apache.org/jira/browse/MESOS-5968
> Project: Mesos
>  Issue Type: Bug
>  Components: general
>Reporter: Neil Conway
>Priority: Minor
>  Labels: mesosphere, newbie
>
> Task IDs are framework-generated, which means they might contain whitespace. 
> That means that when task IDs are included in log messages, they should be 
> quoted. We sometimes use quotes when logging task IDs, but this is not done 
> consistently right now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5968) Ensure that task IDs are quoted consistently

[Neil Conway (JIRA)]

Neil Conway created MESOS-5968:
--

 Summary: Ensure that task IDs are quoted consistently
 Key: MESOS-5968
 URL: https://issues.apache.org/jira/browse/MESOS-5968
 Project: Mesos
  Issue Type: Bug
  Components: general
Reporter: Neil Conway
Priority: Minor


Task IDs are framework-generated, which means they might contain whitespace. 
That means that when task IDs are included in log messages, they should be 
quoted. We sometimes use quotes when logging task IDs, but this is not done 
consistently right now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5853) http v1 API should document behavior regarding generated content-type header in the presence of errors

[Abhishek Dasgupta (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404451#comment-15404451
 ] 

Abhishek Dasgupta commented on MESOS-5853:
--

RR: https://reviews.apache.org/r/50713/

> http v1 API should document behavior regarding generated content-type header 
> in the presence of errors
> --
>
> Key: MESOS-5853
> URL: https://issues.apache.org/jira/browse/MESOS-5853
> Project: Mesos
>  Issue Type: Improvement
>  Components: documentation
>Reporter: James DeFelice
>Assignee: Abhishek Dasgupta
>  Labels: mesosphere
>
> Changes made as part of https://issues.apache.org/jira/browse/MESOS-3739 set 
> a default Content-Type header. This should be documented in the Mesos v1 HTTP 
> API literature so that devs implementing against the spec know what to expect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-4791) Operator API v1

[Vinod Kone (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404402#comment-15404402
 ] 

Vinod Kone commented on MESOS-4791:
---

I think the MVP for operator API is done now. I'll move the unresolved tickets 
to a new epic "Operator API v1 Improvements" like we did with scheduler and 
executor epics.

> Operator API v1
> ---
>
> Key: MESOS-4791
> URL: https://issues.apache.org/jira/browse/MESOS-4791
> Project: Mesos
>  Issue Type: Epic
>Reporter: Vinod Kone
>
> This epic captures the work needed to update the current master HTTP 
> endpoints for operators (e.g., /state, /metrics/snapshot).
> Some problems with the current operator endpoints
> --> No versioning
> --> Access patterns are not consistent (DELETE on /quota vs /destroy-volume)
> --> No published/standard schemas for requests or responses
> Note that we are doing similar work for Framework API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5041) Add cgroups unified isolator

[Jie Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jie Yu updated MESOS-5041:
--
Labels: mesosphere  (was: )

> Add cgroups unified isolator
> 
>
> Key: MESOS-5041
> URL: https://issues.apache.org/jira/browse/MESOS-5041
> Project: Mesos
>  Issue Type: Task
>  Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
>  Labels: mesosphere
> Fix For: 1.1.0
>
>
> Implement the cgroups unified isolator for Mesos containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5041) Add cgroups unified isolator

[Jie Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404362#comment-15404362
 ] 

Jie Yu commented on MESOS-5041:
---

commit 2eeb98e73495d6b015e7861a2ed0f4b131e8a85b
Author: haosdent huang 
Date:   Tue Aug 2 09:47:20 2016 -0700

Implemented `CgroupsIsolatorProcess::finalize`.

Review: https://reviews.apache.org/r/50643/

commit cc16d1dcdd242d380bcc8d63202d4cb647870475
Author: haosdent huang 
Date:   Tue Aug 2 09:47:17 2016 -0700

Implemented `CgroupsIsolatorProcess::initialize`.

Review: https://reviews.apache.org/r/50642/

> Add cgroups unified isolator
> 
>
> Key: MESOS-5041
> URL: https://issues.apache.org/jira/browse/MESOS-5041
> Project: Mesos
>  Issue Type: Task
>  Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
> Fix For: 1.1.0
>
>
> Implement the cgroups unified isolator for Mesos containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-5041) Add cgroups unified isolator

[Jie Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404334#comment-15404334
 ] 

Jie Yu commented on MESOS-5041:
---

commit 58a1bd1396f7f124537dd21812bcb65ee6802452
Author: haosdent huang 
Date:   Tue Aug 2 09:18:30 2016 -0700

Used `await` instead of `collect` on `Subsystem` operations.

In order to get the error message for each subsystem, this patch changes
to use `await` on `Subsystem` operations and combines every unready
`Future` error message.

Review: https://reviews.apache.org/r/50627/

> Add cgroups unified isolator
> 
>
> Key: MESOS-5041
> URL: https://issues.apache.org/jira/browse/MESOS-5041
> Project: Mesos
>  Issue Type: Task
>  Components: cgroups, isolation
>Reporter: haosdent
>Assignee: haosdent
> Fix For: 1.1.0
>
>
> Implement the cgroups unified isolator for Mesos containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5967) Add support for 'docker image inspect' in our docker abstraction

[Kevin Klues (JIRA)]

Kevin Klues created MESOS-5967:
--

 Summary: Add support for 'docker image inspect' in our docker 
abstraction
 Key: MESOS-5967
 URL: https://issues.apache.org/jira/browse/MESOS-5967
 Project: Mesos
  Issue Type: Improvement
Reporter: Kevin Klues
Assignee: Kevin Klues
 Fix For: 1.1.0


Our current {{docker inspect}} support in our docker abstraction only supports 
inspecting containers (not images).  We should expand this support to images.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-5966) Add libprocess HTTP tests with SSL support

[Greg Mann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann reassigned MESOS-5966:


Assignee: Greg Mann

> Add libprocess HTTP tests with SSL support
> --
>
> Key: MESOS-5966
> URL: https://issues.apache.org/jira/browse/MESOS-5966
> Project: Mesos
>  Issue Type: Task
>Reporter: Greg Mann
>Assignee: Greg Mann
>  Labels: mesosphere
>
> Libprocess contains SSL unit tests which test our SSL support using raw 
> sockets. We should add tests which also make use of libprocess's various HTTP 
> classes and helpers in a variety of SSL configurations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5966) Add libprocess HTTP tests with SSL support

[Greg Mann (JIRA)]

Greg Mann created MESOS-5966:


 Summary: Add libprocess HTTP tests with SSL support
 Key: MESOS-5966
 URL: https://issues.apache.org/jira/browse/MESOS-5966
 Project: Mesos
  Issue Type: Task
Reporter: Greg Mann


Libprocess contains SSL unit tests which test our SSL support using raw 
sockets. We should add tests which also make use of libprocess's various HTTP 
classes and helpers in a variety of SSL configurations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5966) Add libprocess HTTP tests with SSL support

[Greg Mann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann updated MESOS-5966:
-
Description: Libprocess contains SSL unit tests which test our SSL support 
using simple sockets. We should add tests which also make use of libprocess's 
various HTTP classes and helpers in a variety of SSL configurations.  (was: 
Libprocess contains SSL unit tests which test our SSL support using raw 
sockets. We should add tests which also make use of libprocess's various HTTP 
classes and helpers in a variety of SSL configurations.)

> Add libprocess HTTP tests with SSL support
> --
>
> Key: MESOS-5966
> URL: https://issues.apache.org/jira/browse/MESOS-5966
> Project: Mesos
>  Issue Type: Task
>Reporter: Greg Mann
>Assignee: Greg Mann
>  Labels: mesosphere
>
> Libprocess contains SSL unit tests which test our SSL support using simple 
> sockets. We should add tests which also make use of libprocess's various HTTP 
> classes and helpers in a variety of SSL configurations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5966) Add libprocess HTTP tests with SSL support

[Greg Mann (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann updated MESOS-5966:
-
Shepherd: Vinod Kone

> Add libprocess HTTP tests with SSL support
> --
>
> Key: MESOS-5966
> URL: https://issues.apache.org/jira/browse/MESOS-5966
> Project: Mesos
>  Issue Type: Task
>Reporter: Greg Mann
>Assignee: Greg Mann
>  Labels: mesosphere
>
> Libprocess contains SSL unit tests which test our SSL support using raw 
> sockets. We should add tests which also make use of libprocess's various HTTP 
> classes and helpers in a variety of SSL configurations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-5964) Support health policies in health checks.

[haosdent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

haosdent reassigned MESOS-5964:
---

Assignee: haosdent

> Support health policies in health checks.
> -
>
> Key: MESOS-5964
> URL: https://issues.apache.org/jira/browse/MESOS-5964
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Alexander Rukletsov
>Assignee: haosdent
>  Labels: health-check, mesosphere
>
> Currently, Mesos supports a single "restart policy" ("restart policy" is a 
> poor name, alternatives are "unhealthy policy", "health policy"): kill a task 
> when it becomes unhealthy. This can be described as "local health policy", 
> because the decision is made locally.
> In contrast, a framework may want to apply "global health policy", which 
> means health status is reported to the scheduler and no action is taken on 
> the agent; the scheduler decides how to act and instructs executor 
> explicitly. A third policy can be "mixed": executor does kill tasks without 
> consulting the scheduler, but it nevertheless propagates task health updates 
> to the scheduler.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-5963) HealthChecker should not decide when to kill tasks and when to stop performing health checks.

[haosdent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

haosdent reassigned MESOS-5963:
---

Assignee: haosdent

> HealthChecker should not decide when to kill tasks and when to stop 
> performing health checks.
> -
>
> Key: MESOS-5963
> URL: https://issues.apache.org/jira/browse/MESOS-5963
> Project: Mesos
>  Issue Type: Bug
>Reporter: Alexander Rukletsov
>Assignee: haosdent
>  Labels: health-check, mesosphere
>
> Currently, {{HealthChecker}} library decides when a task should be killed 
> based on its health status. Moreover, it stops checking it health after that. 
> This seems unfortunate, because it's up to the executor and / or framework to 
> decide both when to kill tasks and when to health check them. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5965) Implement garbage collection for unreachable, gone agent lists in registry

[Neil Conway (JIRA)]

Neil Conway created MESOS-5965:
--

 Summary: Implement garbage collection for unreachable, gone agent 
lists in registry
 Key: MESOS-5965
 URL: https://issues.apache.org/jira/browse/MESOS-5965
 Project: Mesos
  Issue Type: Improvement
  Components: master
Reporter: Neil Conway
Assignee: Neil Conway


The list of unreachable agents (and eventually, the list of gone agents) can 
grow without bound. We should implement a GC scheme to avoid these lists 
getting too large and hampering the performance of the master.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-4049) Allow user to control behavior of partitioned agents/tasks

[Neil Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-4049:
---
Shepherd: Vinod Kone

> Allow user to control behavior of partitioned agents/tasks
> --
>
> Key: MESOS-4049
> URL: https://issues.apache.org/jira/browse/MESOS-4049
> Project: Mesos
>  Issue Type: Improvement
>  Components: master, slave
>Reporter: Neil Conway
>Assignee: Neil Conway
>  Labels: mesosphere
>
> At present, if an agent is partitioned away from the master, the master waits 
> for a period of time (see MESOS-4048) before deciding that the agent is dead. 
> Then it marks the agent as lost, sends {{TASK_LOST}} messages for all the 
> tasks running on the agent, and instructs the agent to shutdown.
> Although this behavior is desirable for some/many users, it is not ideal for 
> everyone. For example:
> * Some users might want to aggressively start a new replacement task (e.g., 
> after one or two ping timeouts are missed); then when the old copy of the 
> task comes back, they might want to make an intelligent decision about how to 
> reconcile this situation (e.g., kill old, kill new, allow both to continue 
> running).
> * Some frameworks might want different behavior from other frameworks, or to 
> treat some tasks differently from other tasks. For example, if a task has a 
> huge amount of state that would need to be regenerated to spin up another 
> instance, the user might want to wait longer before starting a new task to 
> increase the chance that the old task will reappear.
> To do this, we'd need to change task state so that a task can go from 
> {{RUNNING}} to a new state (say {{UNKNOWN}} or {{WANDERING}}), and then from 
> that state back to {{RUNNING}} (or perhaps we could keep the current 
> "mark-lost-after-timeout" behavior as an option, in which case {{UNKNOWN}} 
> could also transition to {{LOST}}). The agent would also keep its old 
> {{slaveId}} when it reconnects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5964) Support health policies in health checks.

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-5964:
---
Description: 
Currently, Mesos supports a single "restart policy" ("restart policy" is a poor 
name, alternatives are "unhealthy policy", "health policy"): kill a task when 
it becomes unhealthy. This can be described as "local health policy", because 
the decision is made locally.

In contrast, a framework may want to apply "global health policy", which means 
health status is reported to the scheduler and no action is taken on the agent; 
the scheduler decides how to act and instructs executor explicitly. A third 
policy can be "mixed": executor does kill tasks without consulting the 
scheduler, but it nevertheless propagates task health updates to the scheduler.

  was:Currently, Mesos supports a single "restart policy" ("restart policy" is 
a poor name, alternatives are "unhealthy policy", "health policy"): kill a task 
when it becomes unhealthy. This can be described as 


> Support health policies in health checks.
> -
>
> Key: MESOS-5964
> URL: https://issues.apache.org/jira/browse/MESOS-5964
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Alexander Rukletsov
>  Labels: health-check, mesosphere
>
> Currently, Mesos supports a single "restart policy" ("restart policy" is a 
> poor name, alternatives are "unhealthy policy", "health policy"): kill a task 
> when it becomes unhealthy. This can be described as "local health policy", 
> because the decision is made locally.
> In contrast, a framework may want to apply "global health policy", which 
> means health status is reported to the scheduler and no action is taken on 
> the agent; the scheduler decides how to act and instructs executor 
> explicitly. A third policy can be "mixed": executor does kill tasks without 
> consulting the scheduler, but it nevertheless propagates task health updates 
> to the scheduler.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5964) Support health policies in health checks.

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-5964:
---
Summary: Support health policies in health checks.  (was: Support restart 
policies in health checks.)

> Support health policies in health checks.
> -
>
> Key: MESOS-5964
> URL: https://issues.apache.org/jira/browse/MESOS-5964
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Alexander Rukletsov
>  Labels: health-check, mesosphere
>
> Currently, Mesos supports a single "restart policy" ("restart policy" is a 
> poor name, alternatives are "unhealthy policy", "health policy"): kill a task 
> when it becomes unhealthy. This can be described as 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5964) Support restart policies in health checks.

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-5964:
---
Description: Currently, Mesos supports a single "restart policy" ("restart 
policy" is a poor name, alternatives are "unhealthy policy", "health policy"): 
kill a task when it becomes unhealthy. This can be described as 

> Support restart policies in health checks.
> --
>
> Key: MESOS-5964
> URL: https://issues.apache.org/jira/browse/MESOS-5964
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Alexander Rukletsov
>  Labels: health-check, mesosphere
>
> Currently, Mesos supports a single "restart policy" ("restart policy" is a 
> poor name, alternatives are "unhealthy policy", "health policy"): kill a task 
> when it becomes unhealthy. This can be described as 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5964) Support restart policies in health checks.

[Alexander Rukletsov (JIRA)]

Alexander Rukletsov created MESOS-5964:
--

 Summary: Support restart policies in health checks.
 Key: MESOS-5964
 URL: https://issues.apache.org/jira/browse/MESOS-5964
 Project: Mesos
  Issue Type: Improvement
Reporter: Alexander Rukletsov






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5961) HTTP and TCP health checks should support docker executor and bridged mode.

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-5961:
---
Labels: health-check mesosphere  (was: mesosphere)

> HTTP and TCP health checks should support docker executor and bridged mode.
> ---
>
> Key: MESOS-5961
> URL: https://issues.apache.org/jira/browse/MESOS-5961
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Alexander Rukletsov
>Assignee: haosdent
>  Labels: health-check, mesosphere
>
> If an executor and a task, e.g. the docker executor and docker container in 
> bridged mode, exist is different network namespaces, HTTP and TCP health 
> checks using {{localhost}} may not work properly. One solution would be to 
> enter the container's network in the health check binary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5963) HealthChecker should not decide when to kill tasks and when to stop performing health checks.

[Alexander Rukletsov (JIRA)]

Alexander Rukletsov created MESOS-5963:
--

 Summary: HealthChecker should not decide when to kill tasks and 
when to stop performing health checks.
 Key: MESOS-5963
 URL: https://issues.apache.org/jira/browse/MESOS-5963
 Project: Mesos
  Issue Type: Bug
Reporter: Alexander Rukletsov


Currently, {{HealthChecker}} library decides when a task should be killed based 
on its health status. Moreover, it stops checking it health after that. This 
seems unfortunate, because it's up to the executor and / or framework to decide 
both when to kill tasks and when to health check them. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5916) Improve health checking.

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-5916:
---
Labels: health-check mesosphere  (was: mesosphere)

> Improve health checking.
> 
>
> Key: MESOS-5916
> URL: https://issues.apache.org/jira/browse/MESOS-5916
> Project: Mesos
>  Issue Type: Epic
>Reporter: Alexander Rukletsov
>  Labels: health-check, mesosphere
>
> This epic aims to provide comprehensive health check support in Mesos 
> (command, HTTP, TCP) and a unified API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (MESOS-5961) HTTP and TCP health checks should support docker executor and bridged mode.

[haosdent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

haosdent reassigned MESOS-5961:
---

Assignee: haosdent

> HTTP and TCP health checks should support docker executor and bridged mode.
> ---
>
> Key: MESOS-5961
> URL: https://issues.apache.org/jira/browse/MESOS-5961
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Alexander Rukletsov
>Assignee: haosdent
>  Labels: mesosphere
>
> If an executor and a task, e.g. the docker executor and docker container in 
> bridged mode, exist is different network namespaces, HTTP and TCP health 
> checks using {{localhost}} may not work properly. One solution would be to 
> enter the container's network in the health check binary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5961) HTTP and TCP health checks should support docker executor and bridged mode.

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-5961:
---
Summary: HTTP and TCP health checks should support docker executor and 
bridged mode.  (was: HTTP and TCP health checks should support docker executor 
and bridged mode)

> HTTP and TCP health checks should support docker executor and bridged mode.
> ---
>
> Key: MESOS-5961
> URL: https://issues.apache.org/jira/browse/MESOS-5961
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Alexander Rukletsov
>  Labels: mesosphere
>
> If an executor and a task, e.g. the docker executor and docker container in 
> bridged mode, exist is different network namespaces, HTTP and TCP health 
> checks using {{localhost}} may not work properly. One solution would be to 
> enter the container's network in the health check binary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-3567) Support TCP checks in Mesos health check program

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-3567:
---
Sprint: Mesosphere Sprint 41

> Support TCP checks in Mesos health check program
> 
>
> Key: MESOS-3567
> URL: https://issues.apache.org/jira/browse/MESOS-3567
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Matthias Veit
>Assignee: haosdent
>  Labels: health-check, mesosphere
>
> In Marathon we have the ability to specify Health Checks for:
> - Command (Mesos supports this)
> - HTTP (see progress in MESOS-2533)
> - TCP missing
> See here for reference: 
> https://mesosphere.github.io/marathon/docs/health-checks.html
> Since we made good experiences with those 3 options in Marathon, I see a lot 
> of value, if Mesos would also support them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2533) Support HTTP checks in Mesos health check program

[Alexander Rukletsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-2533:
---
Sprint: Mesosphere Sprint 41

> Support HTTP checks in Mesos health check program
> -
>
> Key: MESOS-2533
> URL: https://issues.apache.org/jira/browse/MESOS-2533
> Project: Mesos
>  Issue Type: Improvement
>Reporter: Niklas Quarfot Nielsen
>Assignee: haosdent
>  Labels: health-check, mesosphere
>
> Currently, only commands are supported but our health check protobuf enables 
> users to encode HTTP checks as well. We should wire up this in the health 
> check program or remove the http field from the protobuf.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5961) HTTP and TCP health checks should support docker executor and bridged mode

[Alexander Rukletsov (JIRA)]

Alexander Rukletsov created MESOS-5961:
--

 Summary: HTTP and TCP health checks should support docker executor 
and bridged mode
 Key: MESOS-5961
 URL: https://issues.apache.org/jira/browse/MESOS-5961
 Project: Mesos
  Issue Type: Improvement
Reporter: Alexander Rukletsov


If an executor and a task, e.g. the docker executor and docker container in 
bridged mode, exist is different network namespaces, HTTP and TCP health checks 
using {{localhost}} may not work properly. One solution would be to enter the 
container's network in the health check binary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MESOS-2043) Framework auth fail with timeout error and never get authenticated

[Adam B (JIRA)]

[ 
https://issues.apache.org/jira/browse/MESOS-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15403603#comment-15403603
 ] 

Adam B commented on MESOS-2043:
---

Backported to 0.28.x (for 0.28.3) and 0.27.x (for 0.27.4).

> Framework auth fail with timeout error and never get authenticated
> --
>
> Key: MESOS-2043
> URL: https://issues.apache.org/jira/browse/MESOS-2043
> Project: Mesos
>  Issue Type: Bug
>  Components: master, scheduler driver, security, slave
>Affects Versions: 0.21.0
>Reporter: Bhuvan Arumugam
>Assignee: Benjamin Bannier
>Priority: Critical
>  Labels: mesosphere, security
> Fix For: 0.28.3, 1.0.0, 0.27.4
>
> Attachments: aurora-scheduler.20141104-1606-1706.log, master.log, 
> mesos-master.20141104-1606-1706.log, slave.log
>
>
> I'm facing this issue in master as of 
> https://github.com/apache/mesos/commit/74ea59e144d131814c66972fb0cc14784d3503d4
> As [~adam-mesos] mentioned in IRC, this sounds similar to MESOS-1866. I'm 
> running 1 master and 1 scheduler (aurora). The framework authentication fail 
> due to time out:
> error on mesos master:
> {code}
> I1104 19:37:17.741449  8329 master.cpp:3874] Authenticating 
> scheduler-d2d4437b-d375-4467-a583-362152fe065a@SCHEDULER_IP:8083
> I1104 19:37:17.741585  8329 master.cpp:3885] Using default CRAM-MD5 
> authenticator
> I1104 19:37:17.742106  8336 authenticator.hpp:169] Creating new server SASL 
> connection
> W1104 19:37:22.742959  8329 master.cpp:3953] Authentication timed out
> W1104 19:37:22.743548  8329 master.cpp:3930] Failed to authenticate 
> scheduler-d2d4437b-d375-4467-a583-362152fe065a@SCHEDULER_IP:8083: 
> Authentication discarded
> {code}
> scheduler error:
> {code}
> I1104 19:38:57.885486 49012 sched.cpp:283] Authenticating with master 
> master@MASTER_IP:PORT
> I1104 19:38:57.885928 49002 authenticatee.hpp:133] Creating new client SASL 
> connection
> I1104 19:38:57.890581 49007 authenticatee.hpp:224] Received SASL 
> authentication mechanisms: CRAM-MD5
> I1104 19:38:57.890656 49007 authenticatee.hpp:250] Attempting to authenticate 
> with mechanism 'CRAM-MD5'
> W1104 19:39:02.891196 49005 sched.cpp:378] Authentication timed out
> I1104 19:39:02.891850 49018 sched.cpp:338] Failed to authenticate with master 
> master@MASTER_IP:PORT: Authentication discarded
> {code}
> Looks like 2 instances {{scheduler-20f88a53-5945-4977-b5af-28f6c52d3c94}} & 
> {{scheduler-d2d4437b-d375-4467-a583-362152fe065a}} of same framework is 
> trying to authenticate and fail.
> {code}
> W1104 19:36:30.769420  8319 master.cpp:3930] Failed to authenticate 
> scheduler-20f88a53-5945-4977-b5af-28f6c52d3c94@SCHEDULER_IP:8083: Failed to 
> communicate with authenticatee
> I1104 19:36:42.701441  8328 master.cpp:3860] Queuing up authentication 
> request from scheduler-d2d4437b-d375-4467-a583-362152fe065a@SCHEDULER_IP:8083 
> because authentication is still in progress
> {code}
> Restarting master and scheduler didn't fix it. 
> This particular issue happen with 1 master and 1 scheduler after MESOS-1866 
> is fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-2043) Framework auth fail with timeout error and never get authenticated

[Adam B (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-2043:
--
Fix Version/s: 0.27.4

> Framework auth fail with timeout error and never get authenticated
> --
>
> Key: MESOS-2043
> URL: https://issues.apache.org/jira/browse/MESOS-2043
> Project: Mesos
>  Issue Type: Bug
>  Components: master, scheduler driver, security, slave
>Affects Versions: 0.21.0
>Reporter: Bhuvan Arumugam
>Assignee: Benjamin Bannier
>Priority: Critical
>  Labels: mesosphere, security
> Fix For: 0.28.3, 1.0.0, 0.27.4
>
> Attachments: aurora-scheduler.20141104-1606-1706.log, master.log, 
> mesos-master.20141104-1606-1706.log, slave.log
>
>
> I'm facing this issue in master as of 
> https://github.com/apache/mesos/commit/74ea59e144d131814c66972fb0cc14784d3503d4
> As [~adam-mesos] mentioned in IRC, this sounds similar to MESOS-1866. I'm 
> running 1 master and 1 scheduler (aurora). The framework authentication fail 
> due to time out:
> error on mesos master:
> {code}
> I1104 19:37:17.741449  8329 master.cpp:3874] Authenticating 
> scheduler-d2d4437b-d375-4467-a583-362152fe065a@SCHEDULER_IP:8083
> I1104 19:37:17.741585  8329 master.cpp:3885] Using default CRAM-MD5 
> authenticator
> I1104 19:37:17.742106  8336 authenticator.hpp:169] Creating new server SASL 
> connection
> W1104 19:37:22.742959  8329 master.cpp:3953] Authentication timed out
> W1104 19:37:22.743548  8329 master.cpp:3930] Failed to authenticate 
> scheduler-d2d4437b-d375-4467-a583-362152fe065a@SCHEDULER_IP:8083: 
> Authentication discarded
> {code}
> scheduler error:
> {code}
> I1104 19:38:57.885486 49012 sched.cpp:283] Authenticating with master 
> master@MASTER_IP:PORT
> I1104 19:38:57.885928 49002 authenticatee.hpp:133] Creating new client SASL 
> connection
> I1104 19:38:57.890581 49007 authenticatee.hpp:224] Received SASL 
> authentication mechanisms: CRAM-MD5
> I1104 19:38:57.890656 49007 authenticatee.hpp:250] Attempting to authenticate 
> with mechanism 'CRAM-MD5'
> W1104 19:39:02.891196 49005 sched.cpp:378] Authentication timed out
> I1104 19:39:02.891850 49018 sched.cpp:338] Failed to authenticate with master 
> master@MASTER_IP:PORT: Authentication discarded
> {code}
> Looks like 2 instances {{scheduler-20f88a53-5945-4977-b5af-28f6c52d3c94}} & 
> {{scheduler-d2d4437b-d375-4467-a583-362152fe065a}} of same framework is 
> trying to authenticate and fail.
> {code}
> W1104 19:36:30.769420  8319 master.cpp:3930] Failed to authenticate 
> scheduler-20f88a53-5945-4977-b5af-28f6c52d3c94@SCHEDULER_IP:8083: Failed to 
> communicate with authenticatee
> I1104 19:36:42.701441  8328 master.cpp:3860] Queuing up authentication 
> request from scheduler-d2d4437b-d375-4467-a583-362152fe065a@SCHEDULER_IP:8083 
> because authentication is still in progress
> {code}
> Restarting master and scheduler didn't fix it. 
> This particular issue happen with 1 master and 1 scheduler after MESOS-1866 
> is fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MESOS-5960) Design doc for supporting seccomp in Mesos container

[Jay Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MESOS-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jay Guo updated MESOS-5960:
---
   Assignee: Jay Guo
Component/s: containerization
 Issue Type: Task  (was: Bug)

> Design doc for supporting seccomp in Mesos container
> 
>
> Key: MESOS-5960
> URL: https://issues.apache.org/jira/browse/MESOS-5960
> Project: Mesos
>  Issue Type: Task
>  Components: containerization
>Reporter: Jay Guo
>Assignee: Jay Guo
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MESOS-5960) Design doc for supporting seccomp in Mesos container

[Jay Guo (JIRA)]

Jay Guo created MESOS-5960:
--

 Summary: Design doc for supporting seccomp in Mesos container
 Key: MESOS-5960
 URL: https://issues.apache.org/jira/browse/MESOS-5960
 Project: Mesos
  Issue Type: Bug
Reporter: Jay Guo






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)