From commits-return-19825-archive-asf-public=cust-asf.ponee.io@mesos.apache.org Fri Jan 12 01:31:36 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 2E9C1180656 for ; Fri, 12 Jan 2018 01:31:36 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1EAF8160C42; Fri, 12 Jan 2018 00:31:36 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E0DC8160C13 for ; Fri, 12 Jan 2018 01:31:34 +0100 (CET) Received: (qmail 95032 invoked by uid 500); 12 Jan 2018 00:31:34 -0000 Mailing-List: contact commits-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list commits@mesos.apache.org Received: (qmail 95014 invoked by uid 99); 12 Jan 2018 00:31:33 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jan 2018 00:31:33 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id D9645E945F; Fri, 12 Jan 2018 00:31:33 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: git-site-role@apache.org To: commits@mesos.apache.org Date: Fri, 12 Jan 2018 00:31:34 -0000 Message-Id: <2f8a8c3afeae43a792ebabd7bb8a964f@git.apache.org> In-Reply-To: <3e622ff1fb2840e0b5b0bff1a797cf5c@git.apache.org> References: <3e622ff1fb2840e0b5b0bff1a797cf5c@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [2/2] mesos-site git commit: Updated the website built from mesos SHA: 31835a1. Updated the website built from mesos SHA: 31835a1. Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/a150ebc6 Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/a150ebc6 Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/a150ebc6 Branch: refs/heads/asf-site Commit: a150ebc6483d4127cbdbc0de0c70ede744dc4739 Parents: 57e8e9d Author: jenkins Authored: Fri Jan 12 00:31:31 2018 +0000 Committer: jenkins Committed: Fri Jan 12 00:31:31 2018 +0000 ---------------------------------------------------------------------- content/blog/feed.xml | 2 +- .../index.html | 2 +- .../documentation/container-volume/index.html | 5 +- .../latest/container-volume/index.html | 5 +- .../latest/isolators/filesystems/index.html | 233 + .../latest/mesos-containerizer/index.html | 4 +- .../mesos-containerizer/index.html | 4 +- content/sitemap.xml | 8988 +++++++++--------- 8 files changed, 4741 insertions(+), 4502 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a150ebc6/content/blog/feed.xml ---------------------------------------------------------------------- diff --git a/content/blog/feed.xml b/content/blog/feed.xml index cb4a8a8..9b7f0fb 100644 --- a/content/blog/feed.xml +++ b/content/blog/feed.xml @@ -168,7 +168,7 @@ To learn more about CSI work in Mesos, you can dig into the design document < </ul> -<p>If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing <a href="&#x6d;&#97;&#x69;&#108;&#x74;&#x6f;&#58;&#x64;&#x65;&#x76;&#64;&#97;&#x70;&#x61;&#x63;&#104;&#101;&#x2e;&#x6d;&#101;&#x73;&#111;&#115;&#46;&#111;&#114;&#103;">&#x64;&#x65;&#118;&#x40;&#97;&#x70;&#97;&#x63;&#104;&#101;&#x2e;&#109;&#x65;&#x73;&#111;&#115;&#46;&#111;&#x72;&#103;</a>.</p> +<p>If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing <a href="&#x6d;&#x61;&#105;&#108;&#116;&#x6f;&#58;&#100;&#x65;&#x76;&#x40;&#x61;&#x70;&#97;&#99;&#x68;&#101;&#46;&#109;&#x65;&#x73;&#x6f;&#x73;&#46;&#111;&#x72;&#x67;">&#x64;&#x65;&#118;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#x2e;&#x6d;&#x65;&#115;&#111;&#115;&#x2e;&#111;&#114;&#103;</a>.</p> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a150ebc6/content/blog/performance-working-group-progress-report/index.html ---------------------------------------------------------------------- diff --git a/content/blog/performance-working-group-progress-report/index.html b/content/blog/performance-working-group-progress-report/index.html index 4e4053e..cf2215b 100644 --- a/content/blog/performance-working-group-progress-report/index.html +++ b/content/blog/performance-working-group-progress-report/index.html @@ -248,7 +248,7 @@ -

If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing dev@apache.mesos.org.

+

If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing dev@apache.mesos.org.

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a150ebc6/content/documentation/container-volume/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/container-volume/index.html b/content/documentation/container-volume/index.html index c532d37..07cb283 100644 --- a/content/documentation/container-volume/index.html +++ b/content/documentation/container-volume/index.html @@ -166,8 +166,9 @@ host filesystem.

If you are using the Mesos Containerizer, HOST_PATH volumes are handled by the volume/host_path isolator. To enable this isolator, append volume/host_path to the --isolation -flag when starting the agent. This isolator depends on -filesystem/linux isolator.

+flag when starting the agent. This isolator depends on the +filesystem/linux +isolator.

Docker Containerizer supports HOST_PATH volume as well.

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a150ebc6/content/documentation/latest/container-volume/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/container-volume/index.html b/content/documentation/latest/container-volume/index.html index 8c3cef9..3f93a06 100644 --- a/content/documentation/latest/container-volume/index.html +++ b/content/documentation/latest/container-volume/index.html @@ -166,8 +166,9 @@ host filesystem.

If you are using the Mesos Containerizer, HOST_PATH volumes are handled by the volume/host_path isolator. To enable this isolator, append volume/host_path to the --isolation -flag when starting the agent. This isolator depends on -filesystem/linux isolator.

+flag when starting the agent. This isolator depends on the +filesystem/linux +isolator.

Docker Containerizer supports HOST_PATH volume as well.

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a150ebc6/content/documentation/latest/isolators/filesystems/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/isolators/filesystems/index.html b/content/documentation/latest/isolators/filesystems/index.html new file mode 100644 index 0000000..c1e1164 --- /dev/null +++ b/content/documentation/latest/isolators/filesystems/index.html @@ -0,0 +1,233 @@ + + + + + Apache Mesos - Filesystem Isolators in Mesos Containerizer + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+

If you're new to Mesos

+

See the getting started page for more + information about downloading, building, and deploying Mesos.

+ +

If you'd like to get involved or you're looking for support

+

See our community page for more details.

+
+
+

Filesystem Isolators in Mesos Containerizer

+ +

The Mesos Containerizer has several ‘filesystem’ +isolators that are used to provide isolation for a container’s filesystems. +Usually, each platform has a corresponding filesystem isolator associated with +it, because the level of isolation depends on the capabilities of that platform.

+ +

Currently, the Mesos Containerizer supports the +filesystem/posix and +filesystem/linux isolators. +filesystem/shared isolator has a subset of the +features provided by the filesystem/linux +isolator and is broken on hosts with systemd +(MESOS-6563), thus is not +recommended and will be deprecated.

+ +

If you are using the Mesos Containerizer, at least one of the filesystem +isolators needs to be specified through the --isolation flag. If a user does +not specify any filesystem isolator, Mesos Containerizer will default to using +the filesystem/posix isolator.

+ +

Filesystem isolation is a pre-requisite for all the container volume +isolators because it provides some basic +functionality that the volume isolators depends on. For example, the +filesystem/linux isolator will create a new mount +namespace for the container so that any volume mounts made by the volume +isolators will be hidden from the host mount namespace.

+ +

The filesystem isolator is also responsible for preparing persistent volumes +for containers.

+ +

filesystem/posix isolator

+ +

The filesystem/posix isolator works on all POSIX systems. It isolates +container sandboxes and persistent volumes using UNIX file permissions.

+ +

All containers share the same host filesystem. As a result, if you want to +specify a container image for the container, you cannot +use this isolator. Use the filesystem/linux +isolator instead.

+ +

The filesystem/posix isolator handles persistent volumes +by creating symlinks in the container’s sandbox that point to the actual +persistent volumes on the host filesystem.

+ +

filesystem/linux isolator

+ +

The filesystem/linux isolator works only on Linux. It isolates the filesystems +of containers using the following primitives:

+ +
    +
  • Each container gets its own mount namespace. The default mount propagation +in each container is set to ‘slave’.
  • +
  • Use UNIX file permissions to protect container sandboxes and persistent +volumes.
  • +
+ + +

Each container is allowed to define its own image. If a +container image is specified, by default, the container won’t be able to see +files and directories on the host filesystem.

+ +

The filesystem/linux isolator handles persistent volumes +by bind mounting persistent volumes into the container’s sandbox.

+ +
+
+ +
+
+ +
+ + + + + + + + + + + + + + + http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a150ebc6/content/documentation/latest/mesos-containerizer/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/mesos-containerizer/index.html b/content/documentation/latest/mesos-containerizer/index.html index a1f4b4d..9d2fb94 100644 --- a/content/documentation/latest/mesos-containerizer/index.html +++ b/content/documentation/latest/mesos-containerizer/index.html @@ -153,8 +153,8 @@ can write modules that implement custom isolators.

  • docker/runtime
  • docker/volume
  • environment_secret
  • -
  • filesystem/linux
  • -
  • filesystem/posix
  • +
  • filesystem/linux
  • +
  • filesystem/posix
  • filesystem/shared
  • filesystem/windows
  • gpu/nvidia
  • http://git-wip-us.apache.org/repos/asf/mesos-site/blob/a150ebc6/content/documentation/mesos-containerizer/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/mesos-containerizer/index.html b/content/documentation/mesos-containerizer/index.html index ff9b894..7926f9b 100644 --- a/content/documentation/mesos-containerizer/index.html +++ b/content/documentation/mesos-containerizer/index.html @@ -153,8 +153,8 @@ can write modules that implement custom isolators.

  • docker/runtime
  • docker/volume
  • environment_secret
  • -
  • filesystem/linux
  • -
  • filesystem/posix
  • +
  • filesystem/linux
  • +
  • filesystem/posix
  • filesystem/shared
  • filesystem/windows
  • gpu/nvidia