[jira] [Comment Edited] (MESOS-5813) Port stout-tests suites to Windows
[
https://issues.apache.org/jira/browse/MESOS-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482924#comment-16482924
]
Andrew Schwartzmeyer edited comment on MESOS-5813 at 8/27/18 10:30 PM:
---
We're now at 300 tests enabled vs 324 on Linux, or 92.6%.
More importantly, there are no more stout unit tests disabled with
{{TEMP_DISABLED_ON_WINDOWS}}, meaning the remaining difference are mostly
incompatible code.
Missing tests that won'd be ported:
* FlagsFileTest.JSONFile: This tests deprecated code that pre-dates Windows
support for Mesos.
* OsSignalsTest.Suppress: Tests unused and deleted-on-Windows code.
* OsTest.KilltreeNoRoot: "No root" is not supported
* OsTest.SYMLINK_Chown: chown not supported
* OsTest.Libraries: {LD_LIBRARY_PATH}} has no equivalent
* OsTest.Mknod: "mknod" not supported
* FsTest.Xattr: "xattr" not supported
* ProcTest.Pids: All of {{/proc}} is a Linux thing
* ProcTest.Cpus
* ProcTest.SystemStatus
* ProcTest.ProcessStatus
* ProcTest.SingleThread
* ProcTest.MultipleThreads
* RmdirTest.RemoveDirectoryWithDeviceFile: Not supported
* StrerrorTest.ValidHerrno: Explicitly tests POSIX function
* SystemsTest.Uname: Tests unused and deleted-on-Windows code.
* SystemsTest.Sysname: Tests unused and deleted-on-Windows code.
* SystemsTest.Release: Tests unused and deleted-on-Windows code.
Missing tests that need to be investigated:
* OsTest.Environment
* OsTest.Children
* OsTest.Killtree
* OsTest.ProcessExists
* OsTest.User
* EnvTest.EraseEnv
* RmdirContinueOnErrorTest.RemoveWithContinueOnError
* OsSendfileTest.Sendfile
Missing tests that need 3rdparty support:
* SVNTest.DiffPatch
* SVNTtest.EmptyDiffPatch
was (Author: andschwa):
We're now at 300 tests enabled vs 324 on Linux, or 92.6%.
More importantly, there are no more stout unit tests disabled with
{{TEMP_DISABLED_ON_WINDOWS}}, meaning the remaining difference are mostly
incompatible code.
Missing tests that won'd be ported:
* FlagsFileTest.JSONFile: This tests deprecated code that pre-dates Windows
support for Mesos.
* OsSignalsTest.Suppress: Tests unused and deleted-on-Windows code.
* SystemsTest.Uname: Tests unused and deleted-on-Windows code.
* SystemsTest.Sysname: Tests unused and deleted-on-Windows code.
* SystemsTest.Release: Tests unused and deleted-on-Windows code.
Missing tests that need to be investigated:
* OsTest.Environment
* OsTest.Children
* OsTest.Killtree
* OsTest.KilltreeNoRoot
* OsTest.ProcessExists
* OsTest.User
* OsTest.SYMLINK_Chown
* OsTest.Libraries
* OsTest.Mknod
* ProcTest.Pids
* ProcTest.Cpus
* ProcTest.SystemStatus
* ProcTest.ProcessStatus
* ProcTest.SingleThread
* ProcTest.MultipleThreads
* EnvTest.EraseEnv
* FsTest.Xattr
* RmdirTest.RemoveDirectoryWithDeviceFile
* RmdirContinueOnErrorTest.RemoveWithContinueOnError
* StrerrorTest.ValidHerrno
* OsSendfileTest.Sendfile
Missing tests that need 3rdparty support:
* SVNTest.DiffPatch
* SVNTtest.EmptyDiffPatch
> Port stout-tests suites to Windows
> --
>
> Key: MESOS-5813
> URL: https://issues.apache.org/jira/browse/MESOS-5813
> Project: Mesos
> Issue Type: Epic
>Reporter: Andrew Schwartzmeyer
>Assignee: Andrew Schwartzmeyer
>Priority: Major
> Labels: microsoft, stout, windows
>
> This does not require enabling every test, as inevitably there will be
> disabled tests. However, all test files should be ported to Windows, and for
> each disabled test, an associated issue should exist. The exception is if the
> test does not make sense whatsoever for Windows, in which case it should be
> compiled out instead of temporarily disabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MESOS-5813) Port stout-tests suites to Windows
[ https://issues.apache.org/jira/browse/MESOS-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schwartzmeyer reassigned MESOS-5813: --- Assignee: Andrew Schwartzmeyer > Port stout-tests suites to Windows > -- > > Key: MESOS-5813 > URL: https://issues.apache.org/jira/browse/MESOS-5813 > Project: Mesos > Issue Type: Epic >Reporter: Andrew Schwartzmeyer >Assignee: Andrew Schwartzmeyer >Priority: Major > Labels: microsoft, stout, windows > > This does not require enabling every test, as inevitably there will be > disabled tests. However, all test files should be ported to Windows, and for > each disabled test, an associated issue should exist. The exception is if the > test does not make sense whatsoever for Windows, in which case it should be > compiled out instead of temporarily disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-7386) Executor not cleaning up existing running docker containers if external logrotate/logger processes die/killed
[
https://issues.apache.org/jira/browse/MESOS-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594059#comment-16594059
]
Joseph Wu commented on MESOS-7386:
--
I believe the problem still exists. When the {{mesos-docker-executor}} exits
prematurely for any reason (like someone manually killing the executor), it
will not have the chance to stop the associated docker container.
> Executor not cleaning up existing running docker containers if external
> logrotate/logger processes die/killed
> -
>
> Key: MESOS-7386
> URL: https://issues.apache.org/jira/browse/MESOS-7386
> Project: Mesos
> Issue Type: Bug
> Components: agent, docker, executor
>Affects Versions: 0.28.2, 1.2.0
> Environment: Mesos 0.28.2/1.2.0, docker 1.12.0/17.04.0-ce, marathon
> v1.1.2/v1.4.2 , ubuntu trusty 14.04,
> org_apache_mesos_LogrotateContainerLogger,
> org_apache_mesos_ExternalContainerLogger
>Reporter: Pranay Kanwar
>Priority: Critical
>
> if mesos-logrorate/external logger processes die/killed executor exits / task
> fails and task is relaunched , but is unable to cleanup existing running
> container.
> Logs
> {noformat}
> slave-one_1 | I0413 12:45:17.707762 8989 status_update_manager.cpp:395]
> Received status update acknowledgement (UUID:
> 7262c443-e201-45f4-8de0-825d3d92c26b) for task
> msg.dfb155bc-2046-11e7-8019-02427fa1c4d5 of framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-
> slave-one_1 | I0413 12:45:17.707813 8989 status_update_manager.cpp:832]
> Checkpointing ACK for status update TASK_FAILED (UUID:
> 7262c443-e201-45f4-8de0-825d3d92c26b) for task
> msg.dfb155bc-2046-11e7-8019-02427fa1c4d5 of framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-
> slave-one_1 | I0413 12:45:18.615839 8991 slave.cpp:4388] Got exited event
> for executor(1)@172.17.0.1:36471
> slave-one_1 | I0413 12:45:18.696413 8987 docker.cpp:2358] Executor for
> container 665e86c8-ef36-4be3-b56e-3ba7edc81182 has exited
> slave-one_1 | I0413 12:45:18.696446 8987 docker.cpp:2052] Destroying
> container 665e86c8-ef36-4be3-b56e-3ba7edc81182
> slave-one_1 | I0413 12:45:18.696482 8987 docker.cpp:2179] Running docker
> stop on container 665e86c8-ef36-4be3-b56e-3ba7edc81182
> slave-one_1 | I0413 12:45:18.697042 8994 slave.cpp:4769] Executor
> 'msg.dfb155bc-2046-11e7-8019-02427fa1c4d5' of framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9- exited with status 0
> slave-one_1 | I0413 12:45:18.697077 8994 slave.cpp:4869] Cleaning up
> executor 'msg.dfb155bc-2046-11e7-8019-02427fa1c4d5' of framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9- at executor(1)@172.17.0.1:36471
> slave-one_1 | I0413 12:45:18.697424 8994 slave.cpp:4957] Cleaning up
> framework d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-
> slave-one_1 | I0413 12:45:18.697530 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-/executors/msg.dfb155bc-2046-11e7-8019-02427fa1c4d5/runs/665e86c8-ef36-4be3-b56e-3ba7edc81182'
> for gc 6.9192952593days in the future
> slave-one_1 | I0413 12:45:18.697572 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-/executors/msg.dfb155bc-2046-11e7-8019-02427fa1c4d5'
> for gc 6.9192882963days in the future
> slave-one_1 | I0413 12:45:18.697607 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/meta/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-/executors/msg.dfb155bc-2046-11e7-8019-02427fa1c4d5/runs/665e86c8-ef36-4be3-b56e-3ba7edc81182'
> for gc 6.9192843852days in the future
> slave-one_1 | I0413 12:45:18.697628 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/meta/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-/executors/msg.dfb155bc-2046-11e7-8019-02427fa1c4d5'
> for gc 6.9192808889days in the future
> slave-one_1 | I0413 12:45:18.697649 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-'
> for gc 6.9192731556days in the future
> slave-one_1 | I0413 12:45:18.697670 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/meta/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-'
> for gc 6.9192698963days in the future
> slave-one_1 | I0413 12:45:18.697698 8994 status_update_manager.cpp:285]
> Closing status update streams for framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-
> {noformat}
> Container 665e86c8-ef36-4be3-b56e-3ba7edc81182 is still running
> {noformat}
> root@orobas:/#
[jira] [Commented] (MESOS-7386) Executor not cleaning up existing running docker containers if external logrotate/logger processes die/killed
[
https://issues.apache.org/jira/browse/MESOS-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594047#comment-16594047
]
Greg Mann commented on MESOS-7386:
--
[~r4um] [~kaysoky] do you guys know if this is still an issue? Came across the
open PR while reviewing Github today.
> Executor not cleaning up existing running docker containers if external
> logrotate/logger processes die/killed
> -
>
> Key: MESOS-7386
> URL: https://issues.apache.org/jira/browse/MESOS-7386
> Project: Mesos
> Issue Type: Bug
> Components: agent, docker, executor
>Affects Versions: 0.28.2, 1.2.0
> Environment: Mesos 0.28.2/1.2.0, docker 1.12.0/17.04.0-ce, marathon
> v1.1.2/v1.4.2 , ubuntu trusty 14.04,
> org_apache_mesos_LogrotateContainerLogger,
> org_apache_mesos_ExternalContainerLogger
>Reporter: Pranay Kanwar
>Priority: Critical
>
> if mesos-logrorate/external logger processes die/killed executor exits / task
> fails and task is relaunched , but is unable to cleanup existing running
> container.
> Logs
> {noformat}
> slave-one_1 | I0413 12:45:17.707762 8989 status_update_manager.cpp:395]
> Received status update acknowledgement (UUID:
> 7262c443-e201-45f4-8de0-825d3d92c26b) for task
> msg.dfb155bc-2046-11e7-8019-02427fa1c4d5 of framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-
> slave-one_1 | I0413 12:45:17.707813 8989 status_update_manager.cpp:832]
> Checkpointing ACK for status update TASK_FAILED (UUID:
> 7262c443-e201-45f4-8de0-825d3d92c26b) for task
> msg.dfb155bc-2046-11e7-8019-02427fa1c4d5 of framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-
> slave-one_1 | I0413 12:45:18.615839 8991 slave.cpp:4388] Got exited event
> for executor(1)@172.17.0.1:36471
> slave-one_1 | I0413 12:45:18.696413 8987 docker.cpp:2358] Executor for
> container 665e86c8-ef36-4be3-b56e-3ba7edc81182 has exited
> slave-one_1 | I0413 12:45:18.696446 8987 docker.cpp:2052] Destroying
> container 665e86c8-ef36-4be3-b56e-3ba7edc81182
> slave-one_1 | I0413 12:45:18.696482 8987 docker.cpp:2179] Running docker
> stop on container 665e86c8-ef36-4be3-b56e-3ba7edc81182
> slave-one_1 | I0413 12:45:18.697042 8994 slave.cpp:4769] Executor
> 'msg.dfb155bc-2046-11e7-8019-02427fa1c4d5' of framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9- exited with status 0
> slave-one_1 | I0413 12:45:18.697077 8994 slave.cpp:4869] Cleaning up
> executor 'msg.dfb155bc-2046-11e7-8019-02427fa1c4d5' of framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9- at executor(1)@172.17.0.1:36471
> slave-one_1 | I0413 12:45:18.697424 8994 slave.cpp:4957] Cleaning up
> framework d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-
> slave-one_1 | I0413 12:45:18.697530 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-/executors/msg.dfb155bc-2046-11e7-8019-02427fa1c4d5/runs/665e86c8-ef36-4be3-b56e-3ba7edc81182'
> for gc 6.9192952593days in the future
> slave-one_1 | I0413 12:45:18.697572 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-/executors/msg.dfb155bc-2046-11e7-8019-02427fa1c4d5'
> for gc 6.9192882963days in the future
> slave-one_1 | I0413 12:45:18.697607 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/meta/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-/executors/msg.dfb155bc-2046-11e7-8019-02427fa1c4d5/runs/665e86c8-ef36-4be3-b56e-3ba7edc81182'
> for gc 6.9192843852days in the future
> slave-one_1 | I0413 12:45:18.697628 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/meta/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-/executors/msg.dfb155bc-2046-11e7-8019-02427fa1c4d5'
> for gc 6.9192808889days in the future
> slave-one_1 | I0413 12:45:18.697649 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-'
> for gc 6.9192731556days in the future
> slave-one_1 | I0413 12:45:18.697670 8994 gc.cpp:55] Scheduling
> '/tmp/mesos/agent/meta/slaves/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-S0/frameworks/d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-'
> for gc 6.9192698963days in the future
> slave-one_1 | I0413 12:45:18.697698 8994 status_update_manager.cpp:285]
> Closing status update streams for framework
> d1d616b4-1ed1-4fed-92e5-0ee3d8619be9-
> {noformat}
> Container 665e86c8-ef36-4be3-b56e-3ba7edc81182 is still running
> {noformat}
> root@orobas:/# docker ps | grep 665e86c8-ef36-4be3-b56e-3ba7edc81182
> 8b4dd2ab340dr4um/msg
[jira] [Commented] (MESOS-3932) Silence Boost compiler warnings with CMake
[
https://issues.apache.org/jira/browse/MESOS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594023#comment-16594023
]
ASF GitHub Bot commented on MESOS-3932:
---
andschwa closed pull request #104: MESOS-3932 Suppressed boost auto_ptr compile
warnings.
URL: https://github.com/apache/mesos/pull/104
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index e0c538d9e6..cfb05475e6 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -388,7 +388,7 @@ add_definitions(-DUSE_STATIC_LIB -DBUILD_DATE=0
-DBUILD_TIME=0 -DBUILD_USER="fra
# INCLUDE DIRECTIVES FOR MESOS LIBRARY (generates, e.g., -I/path/to/thing
# on Linux).
#
-include_directories(${AGENT_INCLUDE_DIRS})
+include_directories(SYSTEM ${AGENT_INCLUDE_DIRS})
# LINKING LIBRARIES BY DIRECTORY (might generate, e.g., -L/path/to/thing on
# Linux).
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Silence Boost compiler warnings with CMake
> --
>
> Key: MESOS-3932
> URL: https://issues.apache.org/jira/browse/MESOS-3932
> Project: Mesos
> Issue Type: Bug
>Reporter: Neil Conway
>Assignee: Alex Clemmer
>Priority: Minor
> Labels: cmake, mesosphere, microsoft
> Fix For: 1.2.0
>
>
> Per MESOS-3799, we should silence at least two kinds of compiler warning
> fixes when including the Boost headers:
> * Add -Wno-unused-local-typedefs to CXXFLAGS
> * Use -isystem when including Boost to avoid deprecation warnings for use of
> auto_ptr
> I believe we technically need both, IIRC because some other depedencies pull
> in Boost using their own -I flag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-3932) Silence Boost compiler warnings with CMake
[ https://issues.apache.org/jira/browse/MESOS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594022#comment-16594022 ] ASF GitHub Bot commented on MESOS-3932: --- andschwa commented on issue #104: MESOS-3932 Suppressed boost auto_ptr compile warnings. URL: https://github.com/apache/mesos/pull/104#issuecomment-416309788 Thanks @frankscholten! I am closing this as the whole CMake build has been pretty much rewritten since this was opened. Sorry we didn't get to it in time! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Silence Boost compiler warnings with CMake > -- > > Key: MESOS-3932 > URL: https://issues.apache.org/jira/browse/MESOS-3932 > Project: Mesos > Issue Type: Bug >Reporter: Neil Conway >Assignee: Alex Clemmer >Priority: Minor > Labels: cmake, mesosphere, microsoft > Fix For: 1.2.0 > > > Per MESOS-3799, we should silence at least two kinds of compiler warning > fixes when including the Boost headers: > * Add -Wno-unused-local-typedefs to CXXFLAGS > * Use -isystem when including Boost to avoid deprecation warnings for use of > auto_ptr > I believe we technically need both, IIRC because some other depedencies pull > in Boost using their own -I flag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-3139) Incorporate CMake into standard documentation
[ https://issues.apache.org/jira/browse/MESOS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594019#comment-16594019 ] ASF GitHub Bot commented on MESOS-3139: --- greggomann closed pull request #105: MESOS-3139 Added first draft CMake build docs. URL: https://github.com/apache/mesos/pull/105 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/docs/cmake.md b/docs/cmake.md new file mode 100644 index 00..eac94da76a --- /dev/null +++ b/docs/cmake.md @@ -0,0 +1,59 @@ +--- +title: Apache Mesos - CMake +layout: documentation +--- + +# CMake + +## Downloading Mesos + +There are different ways you can get Mesos: + +1\. Download the latest stable release from [Apache](http://mesos.apache.org/downloads/) (***Recommended***) + +$ wget http://www.apache.org/dist/mesos/0.28.1/mesos-0.28.1.tar.gz +$ tar -zxf mesos-0.28.1.tar.gz + +2\. Clone the Mesos git [repository](https://git-wip-us.apache.org/repos/asf/mesos.git) (***Advanced Users Only***) + +$ git clone https://git-wip-us.apache.org/repos/asf/mesos.git + +*NOTE: If you have problems running the above commands, you may need to first run through the ***System Requirements*** section below to install the `wget`, `tar`, and `git` utilities for your system.* + +## System Requirements + +Mesos runs on Linux (64 Bit) and Mac OS X (64 Bit). To build Mesos from source, GCC 4.8.1+ or Clang 3.5+ and CMake 3.5.1 is required. + +For full support of process isolation under Linux a recent kernel >=3.10 is required. + +Make sure your hostname is resolvable via DNS or via `/etc/hosts` to allow full support of Docker's host-networking capabilities, needed for some of the Mesos tests. When in doubt, please validate that `/etc/hosts` contains your hostname. + +### Ubuntu 16.04 + +Following are the instructions for stock Ubuntu 16.04. If you are using a different OS, please install the packages accordingly. + +# Update the packages. +$ sudo apt-get update + +# Install a few utility tools. +$ sudo apt-get install -y tar wget git + +# Install the latest OpenJDK. +$ sudo apt-get install -y openjdk-7-jdk + +# Install autotools (Only necessary if building from git repository). +$ sudo apt-get install -y autoconf libtool + +# Install other Mesos dependencies. +$ sudo apt-get -y install build-essential python-dev libcurl4-nss-dev libsasl2-dev libsasl2-modules maven libapr1-dev libsvn-dev + +## Building Mesos with CMake + +# Change working directory. +$ cd mesos + +# Configure and build. +$ mkdir build +$ cd build +$ cmake .. +$ make diff --git a/docs/home.md b/docs/home.md index 16a77da437..75d659a1e8 100644 --- a/docs/home.md +++ b/docs/home.md @@ -13,6 +13,7 @@ layout: documentation ## Running Mesos * [Getting Started](getting-started.md) for basic instructions on compiling and installing Mesos. +* [CMake](cmake.md) for building Mesos with CMake. * [Upgrades](upgrades.md) for upgrading a Mesos cluster. * [Configuration](configuration.md) for command-line arguments. * [HTTP Endpoints](endpoints/) for available HTTP endpoints. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Incorporate CMake into standard documentation > - > > Key: MESOS-3139 > URL: https://issues.apache.org/jira/browse/MESOS-3139 > Project: Mesos > Issue Type: Task > Components: cmake >Reporter: Alex Clemmer >Assignee: Alex Clemmer >Priority: Major > Labels: cmake, mesosphere, microsoft, windows-mvp > Fix For: 1.3.0 > > > Right now it's anyone's guess how to build with CMake. If we want people to > use it, we should put up documentation. The central challenge is that the > CMake instructions will be slightly different for different platforms. > For example, on Linux, the gist of the build is basically the same as > autotools; you pull down the system dependencies (like APR, _etc_.), and then: > ``` > ./bootstrap > mkdir build-cmake && cd build-cmake > cmake .. > make > ``` > But, on Windows, it will be somewhat more complicated. There is no bootstrap > step, for example, because Windows doesn't have bash natively. And even when > we put that in, you'll still have to build the glog stuff out-of-band because > CMake has no way of booting up Visual Studio and calling
[jira] [Commented] (MESOS-3139) Incorporate CMake into standard documentation
[ https://issues.apache.org/jira/browse/MESOS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594018#comment-16594018 ] ASF GitHub Bot commented on MESOS-3139: --- greggomann commented on issue #105: MESOS-3139 Added first draft CMake build docs. URL: https://github.com/apache/mesos/pull/105#issuecomment-416308848 Closing this PR since we have added CMake documentation in the meantime. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Incorporate CMake into standard documentation > - > > Key: MESOS-3139 > URL: https://issues.apache.org/jira/browse/MESOS-3139 > Project: Mesos > Issue Type: Task > Components: cmake >Reporter: Alex Clemmer >Assignee: Alex Clemmer >Priority: Major > Labels: cmake, mesosphere, microsoft, windows-mvp > Fix For: 1.3.0 > > > Right now it's anyone's guess how to build with CMake. If we want people to > use it, we should put up documentation. The central challenge is that the > CMake instructions will be slightly different for different platforms. > For example, on Linux, the gist of the build is basically the same as > autotools; you pull down the system dependencies (like APR, _etc_.), and then: > ``` > ./bootstrap > mkdir build-cmake && cd build-cmake > cmake .. > make > ``` > But, on Windows, it will be somewhat more complicated. There is no bootstrap > step, for example, because Windows doesn't have bash natively. And even when > we put that in, you'll still have to build the glog stuff out-of-band because > CMake has no way of booting up Visual Studio and calling "build." > So practically, we need to figure out: > * What our build story is for different platforms > * Write specific instructions for our "core" target platforms. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9186) Failed to build Mesos with Python 3.7
Robin Gögge created MESOS-9186:
--
Summary: Failed to build Mesos with Python 3.7
Key: MESOS-9186
URL: https://issues.apache.org/jira/browse/MESOS-9186
Project: Mesos
Issue Type: Bug
Components: cli
Reporter: Robin Gögge
I've tried to build Mesos with the flag 'enable-new-cli' and Python 3.7 and it
failed with this error message:
{code:java}
Traceback (most recent call last):
File "/Users/mesosphere/code/mesos/src/python/cli_new/bin/../tests/main.py",
line 26, in
from cli.tests import CLITestCase
File "/Users/mesosphere/code/mesos/src/python/cli_new/lib/cli/__init__.py",
line 24, in
from . import util
File "/Users/mesosphere/code/mesos/src/python/cli_new/lib/cli/util.py", line
29, in
from kazoo.client import KazooClient
File
"/Users/mesosphere/code/mesos/build/src/.virtualenv/lib/python3.7/site-packages/kazoo/client.py",
line 67, in
from kazoo.recipe.partitioner import SetPartitioner
File
"/Users/mesosphere/code/mesos/build/src/.virtualenv/lib/python3.7/site-packages/kazoo/recipe/partitioner.py",
line 194
self._child_watching(self._allocate_transition, async=True)
^
SyntaxError: invalid syntax
make[3]: *** [check-local] Error 1
make[2]: *** [check-am] Error 2
make[1]: *** [check] Error 2
make: *** [check-recursive] Error 1
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MESOS-9185) An attempt to remove or destroy container in composing containerizer leads to segfault
Andrei Budnik created MESOS-9185: Summary: An attempt to remove or destroy container in composing containerizer leads to segfault Key: MESOS-9185 URL: https://issues.apache.org/jira/browse/MESOS-9185 Project: Mesos Issue Type: Bug Components: agent, containerization Reporter: Andrei Budnik Assignee: Andrei Budnik `LAUNCH_NESTED_CONTAINER` and `LAUNCH_NESTED_CONTAINER_SESSION` leads to segfault in the agent when the parent container is unknown to the composing containerizer. If the parent container cannot be found during an attempt to launch a nested container via `ComposingContainerizerProcess::launch()`, the composing container returns an error without cleaning up the container. On `launch()` failures, the agent calls `destroy()` which accesses uninitialized `containerizer` field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MESOS-9184) A new API for master information, like the state api but subtract the slaves and task
xiaowei created MESOS-9184:
--
Summary: A new API for master information, like the state api but
subtract the slaves and task
Key: MESOS-9184
URL: https://issues.apache.org/jira/browse/MESOS-9184
Project: Mesos
Issue Type: Improvement
Components: HTTP API
Reporter: xiaowei
Now, Mesos provides two HTTP Endpoints: `/state` & `/state-summary` for the
master status info. In the `/state-summary` API, it report the frameworks and
slaves statistics info. In the `/state` API, the response like this:
{code:java}
// https://github.com/apache/mesos/blob/master/src/master/http.cpp#L2742
// Omitted the flags detail
{
"version" : "0.28.0",
"git_sha" : "9d5889b5a265849886a533965f4aefefd1fbd103",
"git_branch" : "refs/heads/master",
"git_tag" : "0.28.0",
"build_date" : "2016-02-15 10:00:28",
"build_time" : 149228,
"build_user" : "mesos-user",
"start_time" : 1455643643.42422,
"elected_time" : 1455643643.43457,
"id" : "b5eac2c5-609b-4ca1-a352-61941702fc9e",
"pid" : "master@127.0.0.1:5050",
"hostname" : "localhost",
"activated_slaves" : 0,
"deactivated_slaves" : 0,
"cluster" : "test-cluster",
"leader" : "master@127.0.0.1:5050",
"log_dir" : "/var/log",
"external_log_file" : "mesos.log",
"flags" : {...},
"slaves" : [],
"frameworks" : [],
"completed_frameworks" : [],
"orphan_tasks" : [],
"unregistered_frameworks" : []",
}
{code}
These information contains the master program build info, current master
process info and the whole cluster running info like slaves、frameworks、tasks.
Hope :D there is a new api to report the master program build info and process
info, and only contains the master information. it will be much more simply and
fast.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
