You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by gi...@apache.org on 2017/12/31 12:41:32 UTC
[2/2] mesos-site git commit: Updated the website built from mesos
SHA: 5e88bc0.
Updated the website built from mesos SHA: 5e88bc0.
Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/4492ea6b
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/4492ea6b
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/4492ea6b
Branch: refs/heads/asf-site
Commit: 4492ea6b3f27199eef764123853f818b2d13b43c
Parents: 241ee62
Author: jenkins <bu...@apache.org>
Authored: Sun Dec 31 12:41:28 2017 +0000
Committer: jenkins <bu...@apache.org>
Committed: Sun Dec 31 12:41:28 2017 +0000
----------------------------------------------------------------------
content/blog/feed.xml | 2 +-
.../index.html | 2 +-
.../documentation/container-image/index.html | 43 +
.../latest/container-image/index.html | 43 +
.../latest/operator-http-api/index.html | 29 +
.../documentation/operator-http-api/index.html | 29 +
content/sitemap.xml | 8978 +++++++++---------
7 files changed, 4635 insertions(+), 4491 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/4492ea6b/content/blog/feed.xml
----------------------------------------------------------------------
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 2ab4204..de452c3 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="&#109;&#x61;&#105;&#108;&#x74;&#111;&#58;&#x64;&#x65;&#118;&#x40;&#97;&#x70;&#97;&#x63;&#104;&#101;&#46;&#x6d;&#x65;&#x73;&#111;&#x73;&#x2e;&#x6f;&#x72;&#103;">&#x64;&#x65;&#118;&#x40;&#x61;&#112;&#x61;&#x63;&#x68;&#x65;&#x2e;&#109;&#101;&#115;&#x6f;&#x73;&#x2e;&#111;&#114;&#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;&#97;&#x69;&#108;&#x74;&#x6f;&#x3a;&#100;&#x65;&#118;&#x40;&#97;&#x70;&#97;&#x63;&#x68;&#x65;&#46;&#109;&#101;&#x73;&#x6f;&#x73;&#46;&#x6f;&#114;&#103;">&#100;&#x65;&#118;&#x40;&#x61;&#112;&#97;&#x63;&#104;&#x65;&#46;&#109;&#101;&#115;&#111;&#115;&#46;&#111;&#x72;&#x67;</a>.</p>
</content>
</entry>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/4492ea6b/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 fb2ed40..40a38c0 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 @@
</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="mailto:dev@apache.mesos.org">dev@apache.mesos.org</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="mailto:dev@apache.mesos.org">dev@apache.mesos.org</a>.</p>
</div>
</div>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/4492ea6b/content/documentation/container-image/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/container-image/index.html b/content/documentation/container-image/index.html
index 6c544c4..8aec96c 100644
--- a/content/documentation/container-image/index.html
+++ b/content/documentation/container-image/index.html
@@ -510,6 +510,49 @@ and mount it under the sandbox directory. The executor can perform
<code>pivot_root</code> or <code>chroot</code> itself to enter the container root
filesystem.</p>
+<h2>Garbage Collect Unused Container Images</h2>
+
+<p>Experimental support of garbage-collecting unused container images was added at
+Mesos 1.5. This can be either configured automatically via a new agent flag
+<code>--image_gc_config</code>, or manually invoked through agent’s
+<a href="/documentation/latest/./operator-http-api/#prune_images">v1 Operator HTTP API</a>. This can be used
+to avoid unbounded disk space usage of image stores.</p>
+
+<p>This is implemented with a simple mark-and-sweep logic. When image GC happens,
+we check all layers and images referenced by active running containers and avoid
+removing them from the image store. As a pre-requisite, if there are active
+containers launched before Mesos 1.5.0, we cannot determine what images can be
+safely garbage collected, so agent will refuse to invoke image GC. To garbage
+collect container images, users are expected to drain all containers launched
+before Mesos 1.5.0.</p>
+
+<p><strong>NOTE</strong>: currently, the image GC is only supported for docker store in Mesos
+Containerizer.</p>
+
+<h3>Automatic Image GC through Agent Flag</h3>
+
+<p>To enable automatic image GC, use the new agent flag <code>--image_gc_config</code>:</p>
+
+<pre><code>--image_gc_config=file:///home/vagrant/image-gc-config.json
+</code></pre>
+
+<p>or as a JSON object,</p>
+
+<pre><code>--image_gc_config="{ \
+ \"image_disk_headroom\": 0.1, \
+ \"image_disk_watch_interval\": { \
+ \"nano_seconds\": 3600 \
+ }, \
+ \"excluded_images\": \[ \] \
+}"
+</code></pre>
+
+<h3>Manual Image GC through HTTP API</h3>
+
+<p>See <code>PRUNE_IMAGES</code> section in
+<a href="/documentation/latest/./operator-http-api/#prune_images">v1 Operator HTTP API</a> for manual image GC
+through the agent HTTP API.</p>
+
<h2>References</h2>
<p>For more information on the Mesos containerizer filesystem, namespace,
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/4492ea6b/content/documentation/latest/container-image/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/container-image/index.html b/content/documentation/latest/container-image/index.html
index 99c37bd..01597a6 100644
--- a/content/documentation/latest/container-image/index.html
+++ b/content/documentation/latest/container-image/index.html
@@ -510,6 +510,49 @@ and mount it under the sandbox directory. The executor can perform
<code>pivot_root</code> or <code>chroot</code> itself to enter the container root
filesystem.</p>
+<h2>Garbage Collect Unused Container Images</h2>
+
+<p>Experimental support of garbage-collecting unused container images was added at
+Mesos 1.5. This can be either configured automatically via a new agent flag
+<code>--image_gc_config</code>, or manually invoked through agent’s
+<a href="/documentation/latest/./operator-http-api/#prune_images">v1 Operator HTTP API</a>. This can be used
+to avoid unbounded disk space usage of image stores.</p>
+
+<p>This is implemented with a simple mark-and-sweep logic. When image GC happens,
+we check all layers and images referenced by active running containers and avoid
+removing them from the image store. As a pre-requisite, if there are active
+containers launched before Mesos 1.5.0, we cannot determine what images can be
+safely garbage collected, so agent will refuse to invoke image GC. To garbage
+collect container images, users are expected to drain all containers launched
+before Mesos 1.5.0.</p>
+
+<p><strong>NOTE</strong>: currently, the image GC is only supported for docker store in Mesos
+Containerizer.</p>
+
+<h3>Automatic Image GC through Agent Flag</h3>
+
+<p>To enable automatic image GC, use the new agent flag <code>--image_gc_config</code>:</p>
+
+<pre><code>--image_gc_config=file:///home/vagrant/image-gc-config.json
+</code></pre>
+
+<p>or as a JSON object,</p>
+
+<pre><code>--image_gc_config="{ \
+ \"image_disk_headroom\": 0.1, \
+ \"image_disk_watch_interval\": { \
+ \"nano_seconds\": 3600 \
+ }, \
+ \"excluded_images\": \[ \] \
+}"
+</code></pre>
+
+<h3>Manual Image GC through HTTP API</h3>
+
+<p>See <code>PRUNE_IMAGES</code> section in
+<a href="/documentation/latest/./operator-http-api/#prune_images">v1 Operator HTTP API</a> for manual image GC
+through the agent HTTP API.</p>
+
<h2>References</h2>
<p>For more information on the Mesos containerizer filesystem, namespace,
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/4492ea6b/content/documentation/latest/operator-http-api/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/operator-http-api/index.html b/content/documentation/latest/operator-http-api/index.html
index 2e13e0c..a10d197 100644
--- a/content/documentation/latest/operator-http-api/index.html
+++ b/content/documentation/latest/operator-http-api/index.html
@@ -3866,6 +3866,35 @@ REMOVE_NESTED_CONTAINER HTTP Response (JSON):
HTTP/1.1 200 OK
</code></pre>
+<h3>PRUNE_IMAGES</h3>
+
+<p>This call triggers garbage collection for container images. This call can
+only be made when all running containers are launched with Mesos version 1.5
+or newer. An optional list of excluded images from GC can be speficied via
+<code>prune_images.excluded_images</code> field.</p>
+
+<pre><code>PRUNE_IMAGES HTTP Request (JSON):
+
+POST /api/v1 HTTP/1.1
+
+Host: agenthost:5051
+Content-Type: application/json
+Accept: application/json
+
+{
+ "type": "PRUNE_IMAGES",
+ "prune_images": {
+ "excluded_images": [
+ {"type":"DOCKER","docker":{"name":"mysql:latest"}}
+ ]
+ }
+}
+
+PRUNE_IMAGES HTTP Response (JSON):
+
+HTTP/1.1 200 OK
+</code></pre>
+
</div>
</div>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/4492ea6b/content/documentation/operator-http-api/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/operator-http-api/index.html b/content/documentation/operator-http-api/index.html
index fb8e5d0..69d0c61 100644
--- a/content/documentation/operator-http-api/index.html
+++ b/content/documentation/operator-http-api/index.html
@@ -3866,6 +3866,35 @@ REMOVE_NESTED_CONTAINER HTTP Response (JSON):
HTTP/1.1 200 OK
</code></pre>
+<h3>PRUNE_IMAGES</h3>
+
+<p>This call triggers garbage collection for container images. This call can
+only be made when all running containers are launched with Mesos version 1.5
+or newer. An optional list of excluded images from GC can be speficied via
+<code>prune_images.excluded_images</code> field.</p>
+
+<pre><code>PRUNE_IMAGES HTTP Request (JSON):
+
+POST /api/v1 HTTP/1.1
+
+Host: agenthost:5051
+Content-Type: application/json
+Accept: application/json
+
+{
+ "type": "PRUNE_IMAGES",
+ "prune_images": {
+ "excluded_images": [
+ {"type":"DOCKER","docker":{"name":"mysql:latest"}}
+ ]
+ }
+}
+
+PRUNE_IMAGES HTTP Response (JSON):
+
+HTTP/1.1 200 OK
+</code></pre>
+
</div>
</div>