You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by me...@apache.org on 2015/10/09 10:55:29 UTC
[1/2] mesos git commit: Renamed libprocess tests to libprocess-tests.
Repository: mesos
Updated Branches:
refs/heads/master ee9280f35 -> e8e9768c7
Renamed libprocess tests to libprocess-tests.
Review: https://reviews.apache.org/r/39138
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/68743dc9
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/68743dc9
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/68743dc9
Branch: refs/heads/master
Commit: 68743dc92fc57dd9cb827c9e23c515da46eedf9c
Parents: ee9280f
Author: Kapil Arya <ka...@mesosphere.io>
Authored: Fri Oct 9 01:24:21 2015 -0700
Committer: Adam B <ad...@mesosphere.io>
Committed: Fri Oct 9 01:25:40 2015 -0700
----------------------------------------------------------------------
3rdparty/libprocess/Makefile.am | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/68743dc9/3rdparty/libprocess/Makefile.am
----------------------------------------------------------------------
diff --git a/3rdparty/libprocess/Makefile.am b/3rdparty/libprocess/Makefile.am
index c764717..eb73939 100644
--- a/3rdparty/libprocess/Makefile.am
+++ b/3rdparty/libprocess/Makefile.am
@@ -136,9 +136,9 @@ libprocess_la_LIBADD += $(GPERFTOOLS)/libprofiler.la
endif
# Tests.
-check_PROGRAMS = tests benchmarks
+check_PROGRAMS = libprocess-tests benchmarks
-tests_SOURCES = \
+libprocess_tests_SOURCES = \
src/tests/collect_tests.cpp \
src/tests/decoder_tests.cpp \
src/tests/encoder_tests.cpp \
@@ -161,13 +161,13 @@ tests_SOURCES = \
src/tests/timeseries_tests.cpp \
src/tests/time_tests.cpp
-tests_CPPFLAGS = \
+libprocess_tests_CPPFLAGS = \
-I$(top_srcdir)/src \
-I$(GTEST)/include \
-I$(GMOCK)/include \
$(libprocess_la_CPPFLAGS)
-tests_LDADD = \
+libprocess_tests_LDADD = \
3rdparty/libgmock.la \
libprocess.la \
$(LIBGLOG) \
@@ -177,10 +177,10 @@ tests_LDADD = \
if ENABLE_SSL
check_PROGRAMS += ssl-client
ssl_client_SOURCES = src/tests/ssl_client.cpp
-ssl_client_CPPFLAGS = $(tests_CPPFLAGS)
-ssl_client_LDADD = $(tests_LDADD)
+ssl_client_CPPFLAGS = $(libprocess_tests_CPPFLAGS)
+ssl_client_LDADD = $(libprocess_tests_LDADD)
-tests_SOURCES += \
+libprocess_tests_SOURCES += \
src/tests/ssl_tests.cpp
endif
@@ -204,8 +204,8 @@ benchmarks_LDADD = \
# runner that ships with newer versions of autotools.
# See the following discussion for the workaround:
# http://lists.gnu.org/archive/html/automake/2013-01/msg00051.html
-check-local: tests benchmarks
- ./tests
+check-local: libprocess-tests benchmarks
+ ./libprocess-tests
# TODO(benh): Fix shared builds (tests need libglog, libev, etc).
[2/2] mesos git commit: Fixed misleading information in the Mesos
framework writing guide.
Posted by me...@apache.org.
Fixed misleading information in the Mesos framework writing guide.
The framework author's guide contained some misleading and incomplete
information.
Added description of the Mesos command executor.
Fixed outdated information about how to use ExecutorInfo.
Added a link to the Mesos fetcher user documentation.
Review: https://reviews.apache.org/r/38943
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/e8e9768c
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/e8e9768c
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/e8e9768c
Branch: refs/heads/master
Commit: e8e9768c7e82a49d88bee9b68feff7f9b852c9f9
Parents: 68743dc
Author: Connor Doyle <co...@mesosphere.io>
Authored: Fri Oct 9 01:52:02 2015 -0700
Committer: Adam B <ad...@mesosphere.io>
Committed: Fri Oct 9 01:55:00 2015 -0700
----------------------------------------------------------------------
docs/app-framework-development-guide.md | 32 ++++++++++++++++++++++++----
1 file changed, 28 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/e8e9768c/docs/app-framework-development-guide.md
----------------------------------------------------------------------
diff --git a/docs/app-framework-development-guide.md b/docs/app-framework-development-guide.md
index c7aa08d..4a43a93 100644
--- a/docs/app-framework-development-guide.md
+++ b/docs/app-framework-development-guide.md
@@ -128,11 +128,31 @@ virtual void executorLost(SchedulerDriver* driver,
virtual void error(SchedulerDriver* driver, const std::string& message) = 0;
~~~
-## Create your Framework Executor
+## Working with Executors
+
+### Using the Mesos Command Executor
+
+Mesos provides a simple executor that can execute shell commands and Docker containers on behalf of the framework scheduler; enough functionality for a wide variety of framework requirements.
+
+Any scheduler can make use of the Mesos command executor by filling in the optional `CommandInfo` member of the `TaskInfo` protobuf message.
+
+~~~{.proto}
+message TaskInfo {
+ ...
+ optional CommandInfo command = 7;
+ ...
+}
+~~~
+
+The Mesos slave will fill in the rest of the ExecutorInfo for you when tasks are specified this way.
+
+### Creating a custom Framework Executor
+
+If your framework has special requirements, you might want to provide your own Executor implementation. For example, you may not want a 1:1 relationship between tasks and processes.
Your framework executor must inherit from the Executor class. It must override the launchTask() method. You can use the $MESOS_HOME environment variable inside of your executor to determine where Mesos is running from.
-### Executor API
+#### Executor API
Declared in `MESOS_HOME/include/mesos/executor.hpp`
@@ -204,9 +224,13 @@ virtual void shutdown(ExecutorDriver* driver) = 0;
virtual void error(ExecutorDriver* driver, const std::string& message) = 0;
~~~
-## Install your Framework
+#### Install your custom Framework Executor
+
+After creating your custom executor, you need to make it available to all slaves in the cluster.
+
+One way to distribute your framework executor is to let the [Mesos fetcher](/documentation/latest/fetcher/) download it on-demand when your scheduler launches tasks on that slave. `ExecutorInfo` is a Protocol Buffer Message class (defined in `include/mesos/mesos.proto`), and it contains a field of type `CommandInfo`. `CommandInfo` allows schedulers to specify, among other things, a number of resources as URIs. These resources are fetched to a sandbox directory on the slave before attempting to execute the `ExecutorInfo` command. Several URI schemes are supported, including HTTP, FTP, HDFS, and S3 (e.g. see src/examples/java/TestFramework.java for an example of this).
-You need to put your framework somewhere that all slaves on the cluster can get it from. If you are running HDFS, you can put your executor into HDFS. Then, you tell Mesos where it is via the `ExecutorInfo` parameter of `MesosSchedulerDriver`'s constructor (e.g. see src/examples/java/TestFramework.java for an example of this). ExecutorInfo is a Protocol Buffer Message class (defined in `include/mesos/mesos.proto`), and you set its URI field to something like "HDFS://path/to/executor/". Also, you can pass the `frameworks_home` configuration option (defaults to: `MESOS_HOME/frameworks`) to your `mesos-slave` daemons when you launch them to specify where all of your framework executors are stored (e.g. on an NFS mount that is available to all slaves), then set `ExecutorInfo` to be a relative path, and the slave will prepend the value of frameworks_home to the relative path provided.
+Alternatively, you can pass the `frameworks_home` configuration option (defaults to: `MESOS_HOME/frameworks`) to your `mesos-slave` daemons when you launch them to specify where your framework executors are stored (e.g. on an NFS mount that is available to all slaves), then use a relative path in `CommandInfo.uris`, and the slave will prepend the value of `frameworks_home` to the relative path provided.
Once you are sure that your executors are available to the mesos-slaves, you should be able to run your scheduler, which will register with the Mesos master, and start receiving resource offers!