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/01/08 19:44:42 UTC
mesos-site git commit: Updated the website built from mesos SHA:
a9a49f8.
Repository: mesos-site
Updated Branches:
refs/heads/asf-site e4abfd76e -> 955dff2ce
Updated the website built from mesos SHA: a9a49f8.
Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/955dff2c
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/955dff2c
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/955dff2c
Branch: refs/heads/asf-site
Commit: 955dff2ce6fd29d7fedc9437fd3301874613739e
Parents: e4abfd7
Author: jenkins <bu...@apache.org>
Authored: Mon Jan 8 19:44:39 2018 +0000
Committer: jenkins <bu...@apache.org>
Committed: Mon Jan 8 19:44:39 2018 +0000
----------------------------------------------------------------------
content/blog/feed.xml | 2 +-
content/blog/performance-working-group-progress-report/index.html | 2 +-
content/documentation/architecture/index.html | 2 +-
content/documentation/latest/architecture/index.html | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/955dff2c/content/blog/feed.xml
----------------------------------------------------------------------
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 1d790e1..a7af402 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;&#97;&#x69;&#x6c;&#x74;&#111;&#58;&#100;&#101;&#x76;&#64;&#x61;&#112;&#97;&#99;&#104;&#101;&#46;&#109;&#x65;&#x73;&#111;&#115;&#46;&#x6f;&#114;&#103;">&#100;&#101;&#x76;&#x40;&#97;&#112;&#x61;&#99;&#x68;&#x65;&#46;&#109;&#101;&#x73;&#111;&#x73;&#46;&#x6f;&#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="&#109;&#97;&#x69;&#x6c;&#x74;&#x6f;&#x3a;&#x64;&#x65;&#118;&#x40;&#97;&#112;&#x61;&#99;&#104;&#x65;&#x2e;&#109;&#x65;&#115;&#111;&#x73;&#46;&#111;&#114;&#x67;">&#100;&#101;&#x76;&#64;&#97;&#112;&#x61;&#99;&#x68;&#101;&#x2e;&#109;&#x65;&#x73;&#x6f;&#115;&#x2e;&#x6f;&#114;&#103;</a>.</p>
</content>
</entry>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/955dff2c/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 8307525..9e76d49 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/955dff2c/content/documentation/architecture/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/architecture/index.html b/content/documentation/architecture/index.html
index c615119..f9be2bb 100644
--- a/content/documentation/architecture/index.html
+++ b/content/documentation/architecture/index.html
@@ -147,7 +147,7 @@ still receive offers with slave ID, whereas frameworks using the v1 HTTP API rec
<p>While the thin interface provided by Mesos allows it to scale and allows the frameworks to evolve independently, one question remains: how can the constraints of a framework be satisfied without Mesos knowing about these constraints? For example, how can a framework achieve data locality without Mesos knowing which nodes store the data required by the framework? Mesos answers these questions by simply giving frameworks the ability to <strong>reject</strong> offers. A framework will reject the offers that do not satisfy its constraints and accept the ones that do. In particular, we have found that a simple policy called delay scheduling, in which frameworks wait for a limited time to acquire nodes storing the input data, yields nearly optimal data locality.</p>
-<p>You can also read much more about the Mesos architecture in this <a href="http://mesos.berkeley.edu/mesos_tech_report.pdf">technical paper</a>.</p>
+<p>You can also read much more about the Mesos architecture in this <a href="https://www.usenix.org/conference/nsdi11/mesos-platform-fine-grained-resource-sharing-data-center">technical paper</a>.</p>
</div>
</div>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/955dff2c/content/documentation/latest/architecture/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/architecture/index.html b/content/documentation/latest/architecture/index.html
index 947ffd8..87292a0 100644
--- a/content/documentation/latest/architecture/index.html
+++ b/content/documentation/latest/architecture/index.html
@@ -147,7 +147,7 @@ still receive offers with slave ID, whereas frameworks using the v1 HTTP API rec
<p>While the thin interface provided by Mesos allows it to scale and allows the frameworks to evolve independently, one question remains: how can the constraints of a framework be satisfied without Mesos knowing about these constraints? For example, how can a framework achieve data locality without Mesos knowing which nodes store the data required by the framework? Mesos answers these questions by simply giving frameworks the ability to <strong>reject</strong> offers. A framework will reject the offers that do not satisfy its constraints and accept the ones that do. In particular, we have found that a simple policy called delay scheduling, in which frameworks wait for a limited time to acquire nodes storing the input data, yields nearly optimal data locality.</p>
-<p>You can also read much more about the Mesos architecture in this <a href="http://mesos.berkeley.edu/mesos_tech_report.pdf">technical paper</a>.</p>
+<p>You can also read much more about the Mesos architecture in this <a href="https://www.usenix.org/conference/nsdi11/mesos-platform-fine-grained-resource-sharing-data-center">technical paper</a>.</p>
</div>
</div>