Author: wfarner
Date: Mon Dec 21 22:14:24 2015
New Revision: 1721273
URL: http://svn.apache.org/viewvc?rev=1721273&view=rev
Log:
Sync with docs in git to fix anchor links.
Added:
aurora/site/publish/documentation/0.10.0/installing/
aurora/site/publish/documentation/0.10.0/installing/index.html
aurora/site/source/documentation/0.10.0/installing.md
Modified:
aurora/site/Rakefile
aurora/site/publish/documentation/latest/installing/index.html
aurora/site/publish/sitemap.xml
aurora/site/source/documentation/latest/installing.md
Modified: aurora/site/Rakefile
URL:
http://svn.apache.org/viewvc/aurora/site/Rakefile?rev=1721273&r1=1721272&r2=1721273&view=diff
==============================================================================
--- aurora/site/Rakefile (original)
+++ aurora/site/Rakefile Mon Dec 21 22:14:24 2015
@@ -119,9 +119,6 @@ task :generate_docs, [:title, :git_tag]
})
}
}
-
- puts '!!!!!'
- puts 'Note: If you are adding docs for a new release, you should generate
with the title "latest" as well.'
end
desc 'Run the site in development mode. Preview available at
http://localhost:4567/'
Added: aurora/site/publish/documentation/0.10.0/installing/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.10.0/installing/index.html?rev=1721273&view=auto
==============================================================================
--- aurora/site/publish/documentation/0.10.0/installing/index.html (added)
+++ aurora/site/publish/documentation/0.10.0/installing/index.html Mon Dec 21
22:14:24 2015
@@ -0,0 +1,412 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <title>Apache Aurora</title>
+ <link rel="stylesheet"
href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
+ <link href="/assets/css/main.css" rel="stylesheet">
+ <!-- Analytics -->
+ <script type="text/javascript">
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-45879646-1']);
+ _gaq.push(['_setDomainName', 'apache.org']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type =
'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ?
'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
+ })();
+ </script>
+ </head>
+ <body>
+ <div class="container-fluid section-header">
+ <div class="container">
+ <div class="nav nav-bar">
+ <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300"
alt="Transparent Apache Aurora logo with dark background"/></a>
+ <ul class="nav navbar-nav navbar-right">
+ <li><a href="/documentation/latest/">Documentation</a></li>
+ <li><a href="/community/">Community</a></li>
+ <li><a href="/downloads/">Downloads</a></li>
+ <li><a href="/blog/">Blog</a></li>
+ </ul>
+ </div>
+ </div>
+</div>
+
+ <div class="container-fluid">
+ <div class="container content">
+ <div class="col-md-12 documentation">
+<h5 class="page-header text-uppercase">Documentation
+<select onChange="window.location.href='/documentation/' + this.value +
'/installing/'"
+ value="0.10.0">
+ <option value="0.10.0"
+ selected="selected">
+ 0.10.0
+ (latest)
+ </option>
+ <option value="0.9.0"
+ >
+ 0.9.0
+ </option>
+ <option value="0.8.0"
+ >
+ 0.8.0
+ </option>
+ <option value="0.7.0-incubating"
+ >
+ 0.7.0-incubating
+ </option>
+ <option value="0.6.0-incubating"
+ >
+ 0.6.0-incubating
+ </option>
+ <option value="0.5.0-incubating"
+ >
+ 0.5.0-incubating
+ </option>
+</select>
+</h5>
+<h1 id="installing-aurora">Installing Aurora</h1>
+
+<ul>
+<li><a href="#components">Components</a>
+
+<ul>
+<li><a href="#machine-profiles">Machine profiles</a>
+
+<ul>
+<li><a href="#coordinator">Coordinator</a></li>
+<li><a href="#worker">Worker</a></li>
+<li><a href="#client">Client</a></li>
+</ul></li>
+</ul></li>
+<li><a href="#getting-aurora">Getting Aurora</a>
+
+<ul>
+<li><a href="#building-your-own-binary-packages">Building your own binary
packages</a></li>
+<li><a href="#rpms">RPMs</a></li>
+</ul></li>
+<li><a href="#installing-the-scheduler">Installing the scheduler</a>
+
+<ul>
+<li><a href="#ubuntu-1404">Ubuntu 14.04</a></li>
+<li><a href="#centos-7">CentOS 7</a></li>
+<li><a href="#finalizing">Finalizing</a></li>
+<li><a href="#configuration">Configuration</a></li>
+</ul></li>
+<li><a href="#installing-worker-components">Installing worker components</a>
+
+<ul>
+<li><a href="#ubuntu-1404-1">Ubuntu 14.04</a></li>
+<li><a href="#centos-7-1">CentOS 7</a></li>
+<li><a href="#configuration-1">Configuration</a></li>
+</ul></li>
+<li><a href="#installing-the-client">Installing the client</a>
+
+<ul>
+<li><a href="#ubuntu-1404-2">Ubuntu 14.04</a></li>
+<li><a href="#centos-7-2">CentOS 7</a></li>
+<li><a href="#configuration-2">Configuration</a></li>
+</ul></li>
+<li><a href="#see-also">See also</a></li>
+<li><a href="#installing-mesos">Installing Mesos</a>
+
+<ul>
+<li><a href="#mesos-on-ubuntu-14-04">Mesos on Ubuntu 14.04</a></li>
+<li><a href="#mesos-on-centos-7">Mesos on CentOS 7</a></li>
+</ul></li>
+</ul>
+
+<h2 id="components">Components</h2>
+
+<p>Before installing Aurora, it’s important to have an understanding of
the components that make up
+a functioning Aurora cluster.</p>
+
+<ul>
+<li><p><strong>Aurora scheduler</strong><br>
+The scheduler will be your primary interface to the work you run in your
cluster. You will
+instruct it to run jobs, and it will manage them in Mesos for you. You will
also frequently use
+the scheduler’s web interface as a heads-up display for what’s
running in your cluster.</p></li>
+<li><p><strong>Aurora client</strong><br>
+The client (<code>aurora</code> command) is a command line tool that exposes
primitives that you can use to
+interact with the scheduler.</p></li>
+</ul>
+
+<p>Aurora also provides an admin client (<code>aurora_admin</code> command)
that contains commands built for
+ cluster administrators. You can use this tool to do things like manage user
quotas and manage
+ graceful maintenance on machines in cluster.</p>
+
+<ul>
+<li><p><strong>Aurora executor</strong><br>
+The executor (a.k.a. Thermos executor) is responsible for carrying out the
workloads described in
+the Aurora DSL (<code>.aurora</code> files). The executor is what actually
executes user processes. It will
+also perform health checking of tasks and register tasks in ZooKeeper for the
purposes of dynamic
+service discovery. You can find lots more detail on the executor and Thermos
in the
+<a href="/documentation/0.10.0/user-guide/">user guide</a>.</p></li>
+<li><p><strong>Aurora observer</strong><br>
+The observer provides browser-based access to the status of individual tasks
executing on worker
+machines. It gives insight into the processes executing, and facilitates
browsing of task sandbox
+directories.</p></li>
+<li><p><strong>ZooKeeper</strong><br>
+<a href="http://zookeeper.apache.org">ZooKeeper</a> is a distributed consensus
system. In an Aurora cluster
+it is used for reliable election of the leading Aurora scheduler and Mesos
master.</p></li>
+<li><p><strong>Mesos master</strong><br>
+The master is responsible for tracking worker machines and performing
accounting of their
+resources. The scheduler interfaces with the master to control the
cluster.</p></li>
+<li><p><strong>Mesos agent</strong><br>
+The agent receives work assigned by the scheduler and executes them. It
interfaces with Linux
+isolation systems like cgroups, namespaces and Docker to manage the resource
consumption of tasks.
+When a user task is launched, the agent will launch the executor (in the
context of a Linux cgroup
+or Docker container depending upon the environment), which will in turn fork
user processes.</p></li>
+</ul>
+
+<h2 id="machine-profiles">Machine profiles</h2>
+
+<p>Given that many of these components communicate over the network, there are
numerous ways you could
+assemble them to create an Aurora cluster. The simplest way is to think in
terms of three machine
+profiles:</p>
+
+<h3 id="coordinator">Coordinator</h3>
+
+<p><strong>Components</strong>: ZooKeeper, Aurora scheduler, Mesos master</p>
+
+<p>A small number of machines (typically 3 or 5) responsible for cluster
orchestration. In most cases
+it is fine to co-locate these components in anything but very large clusters
(> 1000 machines).
+Beyond that point, operators will likely want to manage these services on
separate machines.</p>
+
+<p>In practice, 5 coordinators have been shown to reliably manage clusters
with tens of thousands of
+machines.</p>
+
+<h3 id="worker">Worker</h3>
+
+<p><strong>Components</strong>: Aurora executor, Aurora observer, Mesos
agent</p>
+
+<p>The bulk of the cluster, where services will actually run.</p>
+
+<h3 id="client">Client</h3>
+
+<p><strong>Components</strong>: Aurora client, Aurora admin client</p>
+
+<p>Any machines that users submit jobs from.</p>
+
+<h2 id="getting-aurora">Getting Aurora</h2>
+
+<p>Source and binary distributions can be found on our
+<a href="https://aurora.apache.org/downloads/">downloads</a> page. Installing
from binary packages is
+recommended for most.</p>
+
+<h3 id="building-your-own-binary-packages">Building your own binary
packages</h3>
+
+<p>Our package build toolchain makes it easy to build your own packages if you
would like. See the
+<a href="https://github.com/apache/aurora-packaging">instructions</a> to learn
how.</p>
+
+<h3 id="rpms">RPMs</h3>
+
+<p>We currently have work in progress to provide official RPMs. As of this
writing, the suggested way
+to get RPMs is to <a href="#building-your-own-binary-packages">build
them</a>.</p>
+
+<p>We do have unofficial experimental RPMs available for testing purposes.</p>
+
+<p><strong>Use these RPMs at your own risk, they are not officially released
under the ASF guidelines.</strong></p>
+<pre class="highlight plaintext"><code>echo '[apache-aurora-wfarner]
+name=Apache Aurora distribution maintained by wfarner
+baseurl=http://people.apache.org/~wfarner/aurora/distributions/0.9.0/rpm/centos-7/x86_64/
+gpgcheck = 0' | sudo tee /etc/yum.repos.d/apache-aurora-wfarner.repo >
/dev/null
+</code></pre>
+
+<h2 id="installing-the-scheduler">Installing the scheduler</h2>
+
+<h3 id="ubuntu-14-04">Ubuntu 14.04</h3>
+
+<ol>
+<li><p>Install Mesos<br>
+Skip down to <a href="#mesos-on-ubuntu-14-04">install mesos</a>, then run:</p>
+<pre class="highlight plaintext"><code>sudo start mesos-master
+</code></pre></li>
+<li><p>Install ZooKeeper</p>
+<pre class="highlight plaintext"><code>sudo apt-get install -y zookeeperd
+</code></pre></li>
+<li><p>Install the Aurora scheduler</p>
+<pre class="highlight plaintext"><code>wget -c
https://apache.bintray.com/aurora/aurora-scheduler_0.10.0-1_amd64.deb
+sudo dpkg -i aurora-scheduler_0.10.0-1_amd64.deb
+</code></pre></li>
+</ol>
+
+<h3 id="centos-7">CentOS 7</h3>
+
+<ol>
+<li><p>Install Mesos<br>
+Skip down to <a href="#mesos-on-centos-7">install mesos</a>, then run:</p>
+<pre class="highlight plaintext"><code>sudo systemctl start mesos-master
+</code></pre></li>
+<li><p>Install ZooKeeper</p>
+<pre class="highlight plaintext"><code>sudo rpm -Uvh
https://archive.cloudera.com/cdh4/one-click-install/redhat/6/x86_64/cloudera-cdh-4-0.x86_64.rpm
+sudo yum install -y java-1.8.0-openjdk-headless zookeeper-server
+
+sudo service zookeeper-server init
+sudo systemctl start zookeeper-server
+</code></pre></li>
+<li><p>Install the Aurora scheduler<br>
+If you haven’t already, read the section on <a href="#rpms">how to get
Aurora RPMs</a>.</p>
+<pre class="highlight plaintext"><code># Note: for older Aurora RPM versions,
this may be called 'aurora'.
+sudo yum install -y aurora-scheduler
+</code></pre></li>
+</ol>
+
+<p>Note: if you are using the unreleased 0.9.0 RPM, you will need to edit
<code>/etc/sysconfig/aurora</code>:<br>
+Change<br>
+<code>-mesos_master_address='zk://127.0.0.1:2181/mesos/master'</code><br>
+To<br>
+<code>-mesos_master_address='zk://127.0.0.1:2181/mesos'</code><br>
+And<br>
+<code>-native_log_file_path='/var/lib/aurora/db'</code><br>
+To<br>
+<code>-native_log_file_path='/var/lib/aurora/scheduler/db'</code></p>
+
+<h3 id="finalizing">Finalizing</h3>
+
+<p>By default, the scheduler will start in an uninitialized mode. This is
because external
+coordination is necessary to be certain operator error does not result in a
quorum of schedulers
+starting up and believing their databases are empty when in fact they should
be re-joining a
+cluster.</p>
+
+<p>Because of this, a fresh install of the scheduler will need intervention to
start up. First,
+stop the scheduler service.<br>
+Ubuntu: <code>sudo stop aurora-scheduler</code><br>
+CentOS: <code>sudo systemctl stop aurora</code></p>
+
+<p>Now initialize the database:</p>
+<pre class="highlight plaintext"><code>sudo -u aurora mkdir -p
/var/lib/aurora/scheduler/db
+sudo -u aurora mesos-log initialize --path=/var/lib/aurora/scheduler/db
+</code></pre>
+
+<p>Now you can start the scheduler back up.<br>
+Ubuntu: <code>sudo start aurora-scheduler</code><br>
+CentOS: <code>sudo systemctl start aurora</code></p>
+
+<h3 id="configuration">Configuration</h3>
+
+<p>For more detail on this topic, see the dedicated page on
+<a href="/documentation/0.10.0/deploying-aurora-scheduler/">deploying the
scheduler</a></p>
+
+<h2 id="installing-worker-components">Installing worker components</h2>
+
+<h3 id="ubuntu-14-04">Ubuntu 14.04</h3>
+
+<ol>
+<li><p>Install Mesos<br>
+Skip down to <a href="#mesos-on-ubuntu-14-04">install mesos</a>, then run:</p>
+<pre class="highlight plaintext"><code>sudo start mesos-slave
+</code></pre></li>
+<li><p>Install Aurora executor and observer</p>
+<pre class="highlight plaintext"><code>wget -c
https://apache.bintray.com/aurora/aurora-executor_0.10.0-1_amd64.deb
+sudo dpkg -i aurora-executor_0.10.0-1_amd64.deb
+</code></pre></li>
+</ol>
+
+<h3 id="centos-7">CentOS 7</h3>
+
+<ol>
+<li><p>Install Mesos<br>
+Skip down to <a href="#mesos-on-centos-7">install mesos</a>, then run:</p>
+<pre class="highlight plaintext"><code>sudo systemctl start mesos-slave
+</code></pre></li>
+<li><p>Install Aurora executor and observer<br>
+If you haven’t already, read the section on <a href="#rpms">how to get
Aurora RPMs</a>.</p>
+<pre class="highlight plaintext"><code># Note: for older Aurora RPM versions,
this may be called 'aurora-thermos'.
+sudo yum install -y aurora-executor
+</code></pre></li>
+</ol>
+
+<h3 id="configuration">Configuration</h3>
+
+<p>The executor and observer typically do not require much configuration.
Command line arguments can
+be passed to the executor using a command line argument on the scheduler.</p>
+
+<h2 id="installing-the-client">Installing the client</h2>
+
+<h3 id="ubuntu-14-04">Ubuntu 14.04</h3>
+<pre class="highlight plaintext"><code>sudo apt-get install -y python2.7 wget
+
+wget https://apache.bintray.com/aurora/aurora-tools_0.10.0-1_amd64.deb
+sudo dpkg -i aurora-tools_0.10.0-1_amd64.deb
+</code></pre>
+
+<h3 id="centos-7">CentOS 7</h3>
+
+<p>If you haven’t already, read the section on <a href="#rpms">how to
get Aurora RPMs</a>.</p>
+<pre class="highlight plaintext"><code># Note: for older Aurora RPM versions,
this may be called 'aurora-client'.
+sudo yum install -y aurora-tools
+</code></pre>
+
+<h3 id="configuration">Configuration</h3>
+
+<p>Client configuration lives in a json file that describes the clusters
available and how to reach
+them. By default this file is at <code>/etc/aurora/clusters.json</code>.</p>
+
+<p>Jobs may be submitted to the scheduler using the client, and are described
with
+<a href="/documentation/0.10.0/configuration-reference/">job
configurations</a> expressed in <code>.aurora</code> files. Typically you will
+maintain a single job configuration file to describe one or more deployment
environments (e.g.
+dev, test, prod) for a production job.</p>
+
+<h2 id="see-also">See also</h2>
+
+<p>We have other docs that you will find useful once you have your cluster up
and running:
+* <a href="/documentation/0.10.0/monitoring/">Monitor</a> your cluster
+* Enable scheduler <a href="/documentation/0.10.0/security/">security</a>
+* View job SLA <a href="/documentation/0.10.0/sla/">statistics</a>
+* Understand the internals of the scheduler’s <a
href="/documentation/0.10.0/storage/">storage</a></p>
+
+<h2 id="installing-mesos">Installing Mesos</h2>
+
+<p>Mesos uses a single package for the Mesos master and slave. As a result,
the package dependencies
+are identical for both.</p>
+
+<h3 id="mesos-on-ubuntu-14-04">Mesos on Ubuntu 14.04</h3>
+<pre class="highlight plaintext"><code>sudo add-apt-repository
ppa:openjdk-r/ppa -y
+sudo apt-get update
+
+sudo apt-get install -y software-properties-common wget libsvn1 libcurl3
openjdk-8-jre-headless
+
+wget -c
http://downloads.mesosphere.io/master/ubuntu/14.04/mesos_0.23.0-1.0.ubuntu1404_amd64.deb
+sudo dpkg -i mesos_0.23.0-1.0.ubuntu1404_amd64.deb
+</code></pre>
+
+<h3 id="mesos-on-centos-7">Mesos on CentOS 7</h3>
+<pre class="highlight plaintext"><code>sudo rpm -Uvh
http://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm
+sudo yum install -y mesos-0.22.0
+</code></pre>
+
+</div>
+
+ </div>
+ </div>
+ <div class="container-fluid section-footer buffer">
+ <div class="container">
+ <div class="row">
+ <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
+ <ul>
+ <li><a href="/downloads/">Downloads</a></li>
+ <li><a href="/community/">Mailing Lists</a></li>
+ <li><a
href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
+ <li><a href="/documentation/latest/contributing/">How
To Contribute</a></li>
+ </ul>
+ </div>
+ <div class="col-md-2"><h3>The ASF</h3>
+ <ul>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a
href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a
href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+ <li><a href="http://www.apache.org/security/">Security</a></li>
+ </ul>
+ </div>
+ <div class="col-md-6">
+ <p class="disclaimer">Copyright 2014 <a
href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under
the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a
href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX
photo</a> displayed on the homepage is available under a <a
href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons
BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo
are trademarks of The Apache Software Foundation.</p>
+ </div>
+ </div>
+ </div>
+
+ </body>
+</html>
Modified: aurora/site/publish/documentation/latest/installing/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/installing/index.html?rev=1721273&r1=1721272&r2=1721273&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/installing/index.html (original)
+++ aurora/site/publish/documentation/latest/installing/index.html Mon Dec 21
22:14:24 2015
@@ -114,7 +114,7 @@
<li><a href="#installing-mesos">Installing Mesos</a>
<ul>
-<li><a href="#mesos-on-ubuntu-1404">Mesos on Ubuntu 14.04</a></li>
+<li><a href="#mesos-on-ubuntu-14-04">Mesos on Ubuntu 14.04</a></li>
<li><a href="#mesos-on-centos-7">Mesos on CentOS 7</a></li>
</ul></li>
</ul>
@@ -222,7 +222,7 @@ gpgcheck = 0' | sudo tee /etc/yum.repos.
<ol>
<li><p>Install Mesos<br>
-Skip down to <a href="#mesos-on-ubuntu-1404">install mesos</a>, then run:</p>
+Skip down to <a href="#mesos-on-ubuntu-14-04">install mesos</a>, then run:</p>
<pre class="highlight plaintext"><code>sudo start mesos-master
</code></pre></li>
<li><p>Install ZooKeeper</p>
@@ -297,7 +297,7 @@ CentOS: <code>sudo systemctl start auror
<ol>
<li><p>Install Mesos<br>
-Skip down to <a href="#mesos-on-ubuntu-1404">install mesos</a>, then run:</p>
+Skip down to <a href="#mesos-on-ubuntu-14-04">install mesos</a>, then run:</p>
<pre class="highlight plaintext"><code>sudo start mesos-slave
</code></pre></li>
<li><p>Install Aurora executor and observer</p>
Modified: aurora/site/publish/sitemap.xml
URL:
http://svn.apache.org/viewvc/aurora/site/publish/sitemap.xml?rev=1721273&r1=1721272&r2=1721273&view=diff
==============================================================================
--- aurora/site/publish/sitemap.xml (original)
+++ aurora/site/publish/sitemap.xml Mon Dec 21 22:14:24 2015
@@ -93,6 +93,10 @@
<lastmod>2015-12-21T00:00:00+00:00</lastmod>
</url>
<url>
+ <loc>http://aurora.apache.org/documentation/0.10.0/installing/</loc>
+ <lastmod>2015-12-21T00:00:00+00:00</lastmod>
+ </url>
+ <url>
<loc>http://aurora.apache.org/documentation/0.10.0/monitoring/</loc>
<lastmod>2015-12-21T00:00:00+00:00</lastmod>
</url>
Added: aurora/site/source/documentation/0.10.0/installing.md
URL:
http://svn.apache.org/viewvc/aurora/site/source/documentation/0.10.0/installing.md?rev=1721273&view=auto
==============================================================================
--- aurora/site/source/documentation/0.10.0/installing.md (added)
+++ aurora/site/source/documentation/0.10.0/installing.md Mon Dec 21 22:14:24
2015
@@ -0,0 +1,271 @@
+# Installing Aurora
+
+- [Components](#components)
+ - [Machine profiles](#machine-profiles)
+ - [Coordinator](#coordinator)
+ - [Worker](#worker)
+ - [Client](#client)
+- [Getting Aurora](#getting-aurora)
+ - [Building your own binary packages](#building-your-own-binary-packages)
+ - [RPMs](#rpms)
+- [Installing the scheduler](#installing-the-scheduler)
+ - [Ubuntu 14.04](#ubuntu-1404)
+ - [CentOS 7](#centos-7)
+ - [Finalizing](#finalizing)
+ - [Configuration](#configuration)
+- [Installing worker components](#installing-worker-components)
+ - [Ubuntu 14.04](#ubuntu-1404-1)
+ - [CentOS 7](#centos-7-1)
+ - [Configuration](#configuration-1)
+- [Installing the client](#installing-the-client)
+ - [Ubuntu 14.04](#ubuntu-1404-2)
+ - [CentOS 7](#centos-7-2)
+ - [Configuration](#configuration-2)
+- [See also](#see-also)
+- [Installing Mesos](#installing-mesos)
+ - [Mesos on Ubuntu 14.04](#mesos-on-ubuntu-14-04)
+ - [Mesos on CentOS 7](#mesos-on-centos-7)
+
+## Components
+Before installing Aurora, it's important to have an understanding of the
components that make up
+a functioning Aurora cluster.
+
+* **Aurora scheduler**
+ The scheduler will be your primary interface to the work you run in your
cluster. You will
+ instruct it to run jobs, and it will manage them in Mesos for you. You will
also frequently use
+ the scheduler's web interface as a heads-up display for what's running in
your cluster.
+
+* **Aurora client**
+ The client (`aurora` command) is a command line tool that exposes primitives
that you can use to
+ interact with the scheduler.
+
+ Aurora also provides an admin client (`aurora_admin` command) that contains
commands built for
+ cluster administrators. You can use this tool to do things like manage user
quotas and manage
+ graceful maintenance on machines in cluster.
+
+* **Aurora executor**
+ The executor (a.k.a. Thermos executor) is responsible for carrying out the
workloads described in
+ the Aurora DSL (`.aurora` files). The executor is what actually executes
user processes. It will
+ also perform health checking of tasks and register tasks in ZooKeeper for
the purposes of dynamic
+ service discovery. You can find lots more detail on the executor and
Thermos in the
+ [user guide](/documentation/0.10.0/user-guide/).
+
+* **Aurora observer**
+ The observer provides browser-based access to the status of individual tasks
executing on worker
+ machines. It gives insight into the processes executing, and facilitates
browsing of task sandbox
+ directories.
+
+* **ZooKeeper**
+ [ZooKeeper](http://zookeeper.apache.org) is a distributed consensus system.
In an Aurora cluster
+ it is used for reliable election of the leading Aurora scheduler and Mesos
master.
+
+* **Mesos master**
+ The master is responsible for tracking worker machines and performing
accounting of their
+ resources. The scheduler interfaces with the master to control the cluster.
+
+* **Mesos agent**
+ The agent receives work assigned by the scheduler and executes them. It
interfaces with Linux
+ isolation systems like cgroups, namespaces and Docker to manage the resource
consumption of tasks.
+ When a user task is launched, the agent will launch the executor (in the
context of a Linux cgroup
+ or Docker container depending upon the environment), which will in turn fork
user processes.
+
+## Machine profiles
+Given that many of these components communicate over the network, there are
numerous ways you could
+assemble them to create an Aurora cluster. The simplest way is to think in
terms of three machine
+profiles:
+
+### Coordinator
+**Components**: ZooKeeper, Aurora scheduler, Mesos master
+
+A small number of machines (typically 3 or 5) responsible for cluster
orchestration. In most cases
+it is fine to co-locate these components in anything but very large clusters
(> 1000 machines).
+Beyond that point, operators will likely want to manage these services on
separate machines.
+
+In practice, 5 coordinators have been shown to reliably manage clusters with
tens of thousands of
+machines.
+
+
+### Worker
+**Components**: Aurora executor, Aurora observer, Mesos agent
+
+The bulk of the cluster, where services will actually run.
+
+### Client
+**Components**: Aurora client, Aurora admin client
+
+Any machines that users submit jobs from.
+
+## Getting Aurora
+Source and binary distributions can be found on our
+[downloads](https://aurora.apache.org/downloads/) page. Installing from
binary packages is
+recommended for most.
+
+### Building your own binary packages
+Our package build toolchain makes it easy to build your own packages if you
would like. See the
+[instructions](https://github.com/apache/aurora-packaging) to learn how.
+
+### RPMs
+We currently have work in progress to provide official RPMs. As of this
writing, the suggested way
+to get RPMs is to [build them](#building-your-own-binary-packages).
+
+We do have unofficial experimental RPMs available for testing purposes.
+
+**Use these RPMs at your own risk, they are not officially released under the
ASF guidelines.**
+
+ echo '[apache-aurora-wfarner]
+ name=Apache Aurora distribution maintained by wfarner
+
baseurl=http://people.apache.org/~wfarner/aurora/distributions/0.9.0/rpm/centos-7/x86_64/
+ gpgcheck = 0' | sudo tee /etc/yum.repos.d/apache-aurora-wfarner.repo >
/dev/null
+
+
+## Installing the scheduler
+### Ubuntu 14.04
+
+1. Install Mesos
+ Skip down to [install mesos](#mesos-on-ubuntu-14-04), then run:
+
+ sudo start mesos-master
+
+2. Install ZooKeeper
+
+ sudo apt-get install -y zookeeperd
+
+3. Install the Aurora scheduler
+
+ wget -c
https://apache.bintray.com/aurora/aurora-scheduler_0.10.0-1_amd64.deb
+ sudo dpkg -i aurora-scheduler_0.10.0-1_amd64.deb
+
+### CentOS 7
+
+1. Install Mesos
+ Skip down to [install mesos](#mesos-on-centos-7), then run:
+
+ sudo systemctl start mesos-master
+
+2. Install ZooKeeper
+
+ sudo rpm -Uvh
https://archive.cloudera.com/cdh4/one-click-install/redhat/6/x86_64/cloudera-cdh-4-0.x86_64.rpm
+ sudo yum install -y java-1.8.0-openjdk-headless zookeeper-server
+
+ sudo service zookeeper-server init
+ sudo systemctl start zookeeper-server
+
+3. Install the Aurora scheduler
+ If you haven't already, read the section on [how to get Aurora RPMs](#rpms).
+
+ # Note: for older Aurora RPM versions, this may be called 'aurora'.
+ sudo yum install -y aurora-scheduler
+
+Note: if you are using the unreleased 0.9.0 RPM, you will need to edit
`/etc/sysconfig/aurora`:
+Change
+`-mesos_master_address='zk://127.0.0.1:2181/mesos/master'`
+To
+`-mesos_master_address='zk://127.0.0.1:2181/mesos'`
+And
+`-native_log_file_path='/var/lib/aurora/db'`
+To
+`-native_log_file_path='/var/lib/aurora/scheduler/db'`
+
+### Finalizing
+By default, the scheduler will start in an uninitialized mode. This is
because external
+coordination is necessary to be certain operator error does not result in a
quorum of schedulers
+starting up and believing their databases are empty when in fact they should
be re-joining a
+cluster.
+
+Because of this, a fresh install of the scheduler will need intervention to
start up. First,
+stop the scheduler service.
+Ubuntu: `sudo stop aurora-scheduler`
+CentOS: `sudo systemctl stop aurora`
+
+Now initialize the database:
+
+ sudo -u aurora mkdir -p /var/lib/aurora/scheduler/db
+ sudo -u aurora mesos-log initialize --path=/var/lib/aurora/scheduler/db
+
+Now you can start the scheduler back up.
+Ubuntu: `sudo start aurora-scheduler`
+CentOS: `sudo systemctl start aurora`
+
+### Configuration
+For more detail on this topic, see the dedicated page on
+[deploying the scheduler](/documentation/0.10.0/deploying-aurora-scheduler/)
+
+
+## Installing worker components
+### Ubuntu 14.04
+
+1. Install Mesos
+ Skip down to [install mesos](#mesos-on-ubuntu-14-04), then run:
+
+ sudo start mesos-slave
+
+2. Install Aurora executor and observer
+
+ wget -c
https://apache.bintray.com/aurora/aurora-executor_0.10.0-1_amd64.deb
+ sudo dpkg -i aurora-executor_0.10.0-1_amd64.deb
+
+### CentOS 7
+
+1. Install Mesos
+ Skip down to [install mesos](#mesos-on-centos-7), then run:
+
+ sudo systemctl start mesos-slave
+
+2. Install Aurora executor and observer
+ If you haven't already, read the section on [how to get Aurora RPMs](#rpms).
+
+ # Note: for older Aurora RPM versions, this may be called
'aurora-thermos'.
+ sudo yum install -y aurora-executor
+
+### Configuration
+The executor and observer typically do not require much configuration.
Command line arguments can
+be passed to the executor using a command line argument on the scheduler.
+
+## Installing the client
+### Ubuntu 14.04
+
+ sudo apt-get install -y python2.7 wget
+
+ wget https://apache.bintray.com/aurora/aurora-tools_0.10.0-1_amd64.deb
+ sudo dpkg -i aurora-tools_0.10.0-1_amd64.deb
+
+### CentOS 7
+If you haven't already, read the section on [how to get Aurora RPMs](#rpms).
+
+ # Note: for older Aurora RPM versions, this may be called 'aurora-client'.
+ sudo yum install -y aurora-tools
+
+### Configuration
+Client configuration lives in a json file that describes the clusters
available and how to reach
+them. By default this file is at `/etc/aurora/clusters.json`.
+
+Jobs may be submitted to the scheduler using the client, and are described with
+[job configurations](/documentation/0.10.0/configuration-reference/) expressed
in `.aurora` files. Typically you will
+maintain a single job configuration file to describe one or more deployment
environments (e.g.
+dev, test, prod) for a production job.
+
+## See also
+We have other docs that you will find useful once you have your cluster up and
running:
+* [Monitor](/documentation/0.10.0/monitoring/) your cluster
+* Enable scheduler [security](/documentation/0.10.0/security/)
+* View job SLA [statistics](/documentation/0.10.0/sla/)
+* Understand the internals of the scheduler's
[storage](/documentation/0.10.0/storage/)
+
+## Installing Mesos
+Mesos uses a single package for the Mesos master and slave. As a result, the
package dependencies
+are identical for both.
+
+### Mesos on Ubuntu 14.04
+
+ sudo add-apt-repository ppa:openjdk-r/ppa -y
+ sudo apt-get update
+
+ sudo apt-get install -y software-properties-common wget libsvn1 libcurl3
openjdk-8-jre-headless
+
+ wget -c
http://downloads.mesosphere.io/master/ubuntu/14.04/mesos_0.23.0-1.0.ubuntu1404_amd64.deb
+ sudo dpkg -i mesos_0.23.0-1.0.ubuntu1404_amd64.deb
+
+### Mesos on CentOS 7
+
+ sudo rpm -Uvh
http://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm
+ sudo yum install -y mesos-0.22.0
Modified: aurora/site/source/documentation/latest/installing.md
URL:
http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/installing.md?rev=1721273&r1=1721272&r2=1721273&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/installing.md (original)
+++ aurora/site/source/documentation/latest/installing.md Mon Dec 21 22:14:24
2015
@@ -23,7 +23,7 @@
- [Configuration](#configuration-2)
- [See also](#see-also)
- [Installing Mesos](#installing-mesos)
- - [Mesos on Ubuntu 14.04](#mesos-on-ubuntu-1404)
+ - [Mesos on Ubuntu 14.04](#mesos-on-ubuntu-14-04)
- [Mesos on CentOS 7](#mesos-on-centos-7)
## Components
@@ -122,7 +122,7 @@ We do have unofficial experimental RPMs
### Ubuntu 14.04
1. Install Mesos
- Skip down to [install mesos](#mesos-on-ubuntu-1404), then run:
+ Skip down to [install mesos](#mesos-on-ubuntu-14-04), then run:
sudo start mesos-master
@@ -195,7 +195,7 @@ For more detail on this topic, see the d
### Ubuntu 14.04
1. Install Mesos
- Skip down to [install mesos](#mesos-on-ubuntu-1404), then run:
+ Skip down to [install mesos](#mesos-on-ubuntu-14-04), then run:
sudo start mesos-slave