You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by vi...@apache.org on 2013/04/03 03:43:39 UTC
svn commit: r1463805 - in /incubator/mesos/trunk/docs: Home.md
Mesos-Architecture.md
Author: vinodkone
Date: Wed Apr 3 01:43:38 2013
New Revision: 1463805
URL: http://svn.apache.org/r1463805
Log:
Typo fixes for documentation.
From: Andrew Ash <an...@andrewash.com>
Review: https://reviews.apache.org/r/10002
Modified:
incubator/mesos/trunk/docs/Home.md
incubator/mesos/trunk/docs/Mesos-Architecture.md
Modified: incubator/mesos/trunk/docs/Home.md
URL: http://svn.apache.org/viewvc/incubator/mesos/trunk/docs/Home.md?rev=1463805&r1=1463804&r2=1463805&view=diff
==============================================================================
--- incubator/mesos/trunk/docs/Home.md (original)
+++ incubator/mesos/trunk/docs/Home.md Wed Apr 3 01:43:38 2013
@@ -45,7 +45,7 @@ To get running with Mesos version 0.9.0-
1. [Download Mesos 0.9.0-incubating](http://www.apache.org/dyn/closer.cgi/incubator/mesos/mesos-0.9.0-incubating/)
1. Run configure (there are a few different helper scripts that wrap the `configure` script called configure.<type-of-os>)
1. In OS X: run `./configure.macosx`. If you're running Mountain Lion, you may need to follow the instructions [here](https://issues.apache.org/jira/browse/MESOS-261?focusedCommentId=13447058&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13447058) and [here](https://issues.apache.org/jira/browse/MESOS-285).
- 1. In Linux, you can probably just run `./configure --with-webui --with-included-zookeeper`. These flags are what we recommend; advanced users may want to exclude these flags or use others, see [Mesos Command-Line Flags](Configuration.textile).
+ 1. In Linux, you can probably just run `./configure`, which includes the web UI and included Zookeeper. Advanced users may want to exclude these options or include other options, see [Mesos Command-Line Flags](Configuration.textile).
1. run `make`
### NOTES:
@@ -96,7 +96,7 @@ To run Mesos on more than one machine, y
* [EC2 scripts](EC2-Scripts.textile) for launching a Mesos cluster on Amazon EC2.
* [Logging and Debugging](Logging-and-Debugging.textile) -- viewing Mesos and framework logs.
* [Using ZooKeeper](Using-ZooKeeper.textile) for master fault-tolerance.
- * [Using Linux Containers](Using-Linux-Containers.textile) for resouce isolation on slaves.
+ * [Using Linux Containers](Using-Linux-Containers.textile) for resource isolation on slaves.
* Guide to running existing frameworks:
* [Running Spark on Mesos](https://github.com/mesos/spark/wiki)
* [Using the Mesos Submit tool](Using-the-mesos-submit-tool.md)
Modified: incubator/mesos/trunk/docs/Mesos-Architecture.md
URL: http://svn.apache.org/viewvc/incubator/mesos/trunk/docs/Mesos-Architecture.md?rev=1463805&r1=1463804&r2=1463805&view=diff
==============================================================================
--- incubator/mesos/trunk/docs/Mesos-Architecture.md (original)
+++ incubator/mesos/trunk/docs/Mesos-Architecture.md Wed Apr 3 01:43:38 2013
@@ -1,6 +1,6 @@
<p align="center"><img src="/images/architecture3.jpg" height="300px"></p>
-The above figure shows the main components of Mesos. Mesos consists of a <i>master</i> daemons that manages <i>slave</i> daemons running on each cluster node, and <i>mesos applications</i> (also called <i>frameworks</i>) that run <i>tasks</i> on these slaves.
+The above figure shows the main components of Mesos. Mesos consists of a <i>master</i> daemon that manages <i>slave</i> daemons running on each cluster node, and <i>mesos applications</i> (also called <i>frameworks</i>) that run <i>tasks</i> on these slaves.
The master enables fine-grained sharing of resources (cpu, ram, ...) across applications by making them <i>resource offers</i>. Each resource offer contains a list of <slave ID, resource1: amount1, resource2, amount2, ...>. The master decides <i>how many</i> resources to offer to each framework according to a given organizational policy, such as fair sharing, or strict priority. To support a diverse set of policies, the master employs a modular architecture that makes it easy to add new allocation modules via a plugin mechanism.