mesos git commit: Fixed reference to Mesos paper in the documentation.

[vi...@apache.org]

Repository: mesos
Updated Branches:
  refs/heads/master e35e6808b -> a9a49f834


Fixed reference to Mesos paper in the documentation.

The paper is also available at
https://people.eecs.berkeley.edu/~alig/papers/mesos.pdf but I noticed
it was already included in the site's assets so I just linked that
instead.

This closes #247


Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/a9a49f83
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/a9a49f83
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/a9a49f83

Branch: refs/heads/master
Commit: a9a49f834d78168e1445f089934e89d02b8ac549
Parents: e35e680
Author: Murilo Pereira <mu...@murilopereira.com>
Authored: Mon Jan 8 10:57:00 2018 -0800
Committer: Vinod Kone <vi...@gmail.com>
Committed: Mon Jan 8 10:57:00 2018 -0800

----------------------------------------------------------------------
 docs/architecture.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos/blob/a9a49f83/docs/architecture.md
----------------------------------------------------------------------
diff --git a/docs/architecture.md b/docs/architecture.md
index ede5917..51f7ecc 100644
--- a/docs/architecture.md
+++ b/docs/architecture.md
@@ -34,4 +34,4 @@ In addition, this resource offer process repeats when tasks finish and new resou
 
 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 **reject** 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.
 
-You can also read much more about the Mesos architecture in this [technical paper](http://mesos.berkeley.edu/mesos_tech_report.pdf).
+You can also read much more about the Mesos architecture in this [technical paper](https://www.usenix.org/conference/nsdi11/mesos-platform-fine-grained-resource-sharing-data-center).