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 2018/03/26 17:12:32 UTC
mesos-site git commit: Updated the website built from mesos SHA:
008e068.
Repository: mesos-site
Updated Branches:
refs/heads/asf-site 93e59ddeb -> abc999c14
Updated the website built from mesos SHA: 008e068.
Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/abc999c1
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/abc999c1
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/abc999c1
Branch: refs/heads/asf-site
Commit: abc999c14c2398d3c494f60ca1e1908356b654c3
Parents: 93e59dd
Author: jenkins <bu...@apache.org>
Authored: Mon Mar 26 17:12:28 2018 +0000
Committer: jenkins <bu...@apache.org>
Committed: Mon Mar 26 17:12:28 2018 +0000
----------------------------------------------------------------------
content/blog/feed.xml | 2 +-
.../index.html | 2 +-
content/documentation/cni/index.html | 18 +++++++++---------
content/documentation/latest/cni/index.html | 18 +++++++++---------
4 files changed, 20 insertions(+), 20 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/abc999c1/content/blog/feed.xml
----------------------------------------------------------------------
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 2392953..6bc9378 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -292,7 +292,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;&#x61;&#105;&#x6c;&#116;&#111;&#58;&#100;&#101;&#118;&#64;&#97;&#112;&#97;&#x63;&#104;&#x65;&#x2e;&#x6d;&#101;&#x73;&#x6f;&#x73;&#x2e;&#x6f;&#114;&#x67;">&#100;&#x65;&#118;&#x40;&#x61;&#x70;&#x61;&#99;&#104;&#101;&#46;&#109;&#101;&#x73;&#111;&#115;&#x2e;&#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;&#x6c;&#116;&#111;&#58;&#100;&#101;&#x76;&#64;&#x61;&#x70;&#97;&#x63;&#x68;&#x65;&#x2e;&#x6d;&#101;&#x73;&#111;&#x73;&#46;&#x6f;&#114;&#x67;">&#x64;&#x65;&#x76;&#64;&#97;&#112;&#x61;&#99;&#104;&#x65;&#46;&#x6d;&#x65;&#x73;&#x6f;&#115;&#46;&#x6f;&#x72;&#x67;</a>.</p>
</content>
</entry>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/abc999c1/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 49f3f05..83e7375 100644
--- a/content/blog/performance-working-group-progress-report/index.html
+++ b/content/blog/performance-working-group-progress-report/index.html
@@ -238,7 +238,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/abc999c1/content/documentation/cni/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/cni/index.html b/content/documentation/cni/index.html
index 4dbd5aa..2d06264 100644
--- a/content/documentation/cni/index.html
+++ b/content/documentation/cni/index.html
@@ -224,8 +224,8 @@ isolator) will not affect container orchestration.</p>
<h4><a name="adding-modifying-deleting"></a>Adding/Deleting/Modifying CNI networks</h4>
<p>The <code>network/cni</code> isolator learns about all the CNI networks by
-reading the CNI configuration specified in <code>--network_cni_config_dir</code>
-. Hence, if the operator wants to add a CNI network, the corresponding
+reading the CNI configuration specified in <code>--network_cni_config_dir</code>.
+Hence, if the operator wants to add a CNI network, the corresponding
configuration needs to be added to <code>--network_cni_config_dir</code>.</p>
<p>While the <code>network/cni</code> isolator learns the CNI networks by reading
@@ -245,13 +245,13 @@ destroyed, even if the CNI configuration is deleted.</p>
<p>The fact that the <code>network/cni</code> isolator always reads the CNI
configurations from the disk allows the operator to dynamically add,
modify and delete CNI configurations without the need to restart the
-agent. Whenever the operator adds a new CNI configuration, or modifies
-an existing CNI configuration, the agent will pick up this new CNI
-configuration when the next container is launched on that specific CNI
-network. Similarly when the operator deletes a CNI network the
-<code>network/cni</code> isolator will “unlearn” the CNI network (since it will
-have a reference to this CNI network when it started) in case a
-framework tries to launch a container on the deleted CNI network.</p>
+agent. Whenever the operator modifies an existing CNI configuration,
+the agent will pick up this new CNI configuration when the next
+container is launched on that specific CNI network. Similarly when the
+operator deletes a CNI network the <code>network/cni</code> isolator will
+“unlearn” the CNI network (since it will have a reference to this CNI
+network when it started) in case a framework tries to launch a
+container on the deleted CNI network.</p>
<h4><a name="attaching-containers-to-cni-networks"></a>Attaching containers to CNI networks</h4>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/abc999c1/content/documentation/latest/cni/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/cni/index.html b/content/documentation/latest/cni/index.html
index 74d45c7..0b5a5d1 100644
--- a/content/documentation/latest/cni/index.html
+++ b/content/documentation/latest/cni/index.html
@@ -224,8 +224,8 @@ isolator) will not affect container orchestration.</p>
<h4><a name="adding-modifying-deleting"></a>Adding/Deleting/Modifying CNI networks</h4>
<p>The <code>network/cni</code> isolator learns about all the CNI networks by
-reading the CNI configuration specified in <code>--network_cni_config_dir</code>
-. Hence, if the operator wants to add a CNI network, the corresponding
+reading the CNI configuration specified in <code>--network_cni_config_dir</code>.
+Hence, if the operator wants to add a CNI network, the corresponding
configuration needs to be added to <code>--network_cni_config_dir</code>.</p>
<p>While the <code>network/cni</code> isolator learns the CNI networks by reading
@@ -245,13 +245,13 @@ destroyed, even if the CNI configuration is deleted.</p>
<p>The fact that the <code>network/cni</code> isolator always reads the CNI
configurations from the disk allows the operator to dynamically add,
modify and delete CNI configurations without the need to restart the
-agent. Whenever the operator adds a new CNI configuration, or modifies
-an existing CNI configuration, the agent will pick up this new CNI
-configuration when the next container is launched on that specific CNI
-network. Similarly when the operator deletes a CNI network the
-<code>network/cni</code> isolator will “unlearn” the CNI network (since it will
-have a reference to this CNI network when it started) in case a
-framework tries to launch a container on the deleted CNI network.</p>
+agent. Whenever the operator modifies an existing CNI configuration,
+the agent will pick up this new CNI configuration when the next
+container is launched on that specific CNI network. Similarly when the
+operator deletes a CNI network the <code>network/cni</code> isolator will
+“unlearn” the CNI network (since it will have a reference to this CNI
+network when it started) in case a framework tries to launch a
+container on the deleted CNI network.</p>
<h4><a name="attaching-containers-to-cni-networks"></a>Attaching containers to CNI networks</h4>