You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by me...@apache.org on 2015/09/25 09:42:16 UTC
svn commit: r1705246 [3/3] - in /mesos/site: publish/ publish/documentation/
publish/documentation/configuration/ publish/documentation/latest/
publish/documentation/latest/configuration/
publish/documentation/latest/maintenance/ publish/documentation/...
Added: mesos/site/source/blog/2015-09-24-mesos-0-24-1-and-more-released.md
URL: http://svn.apache.org/viewvc/mesos/site/source/blog/2015-09-24-mesos-0-24-1-and-more-released.md?rev=1705246&view=auto
==============================================================================
--- mesos/site/source/blog/2015-09-24-mesos-0-24-1-and-more-released.md (added)
+++ mesos/site/source/blog/2015-09-24-mesos-0-24-1-and-more-released.md Fri Sep 25 07:42:15 2015
@@ -0,0 +1,21 @@
+---
+layout: post
+title: Apache Mesos 0.24.1 and More Released
+permalink: /blog/mesos-0-24-1-and-more-released/
+published: true
+post_author:
+ display_name: Adam B
+tags: Release
+---
+
+The latest Mesos 0.24.1 is now available for [download](/downloads). This release includes a fix for version parsing for Docker 1.8 and 1.7.0.fc22, as well as a fix for Docker command health checks. These same fixes were backported onto 0.23.0 to produce a new Mesos 0.23.1 release. MESOS-2986 was also backported to 0.21 and 0.22 to produce Mesos 0.21.2 and 0.22.2 (still VOTING). All of these releases are (or will be) available on the [downloads](/downloads) page.
+
+* [MESOS-2986](https://issues.apache.org/jira/browse/MESOS-2986) - Docker version output is not compatible with Mesos
+* [MESOS-3136](https://issues.apache.org/jira/browse/MESOS-3136) - COMMAND health checks with Marathon 0.10.0 are broken
+
+Full release notes are available in the release [CHANGELOG](https://github.com/apache/mesos/blob/master/CHANGELOG).
+
+Upgrading to 0.24.1 can be done seamlessly on a 0.24.0 cluster. In fact, only the slaves need to be upgraded. If upgrading from an earlier version, please refer to the [upgrades](http://mesos.apache.org/documentation/latest/upgrades/) documentation.
+
+## Contributors
+Special thanks to the lone code contributor for 0.24.1, 0.23.1, 0.22.2, and 0.21.2: haosdent huang. Our hero.
Modified: mesos/site/source/documentation/latest.html.md
URL: http://svn.apache.org/viewvc/mesos/site/source/documentation/latest.html.md?rev=1705246&r1=1705245&r2=1705246&view=diff
==============================================================================
--- mesos/site/source/documentation/latest.html.md (original)
+++ mesos/site/source/documentation/latest.html.md Fri Sep 25 07:42:15 2015
@@ -23,6 +23,7 @@ layout: documentation
* [Monitoring](/documentation/latest/monitoring/)
* [Network Monitoring and Isolation](/documentation/latest/network-monitoring/)
* [Slave Recovery](/documentation/latest/slave-recovery/) for doing seamless upgrades.
+* [Maintenance](/documentation/latest/maintenance/) for performing maintenance on a Mesos cluster.
* [Tools](/documentation/latest/tools/) for setting up and running a Mesos cluster.
* [SSL](/documentation/latest/mesos-ssl/) for enabling and enforcing SSL communication.
Modified: mesos/site/source/documentation/latest/configuration.md
URL: http://svn.apache.org/viewvc/mesos/site/source/documentation/latest/configuration.md?rev=1705246&r1=1705245&r2=1705246&view=diff
==============================================================================
--- mesos/site/source/documentation/latest/configuration.md (original)
+++ mesos/site/source/documentation/latest/configuration.md Fri Sep 25 07:42:15 2015
@@ -407,9 +407,22 @@ file:///path/to/file (where file contain
--hostname=VALUE
</td>
<td>
- The hostname the master should advertise in ZooKeeper.
+ The hostname the master should advertise in ZooKeeper.<br>
If left unset, the hostname is resolved from the IP address
- that the master binds to.
+ that the slave binds to; unless the user explicitly prevents
+ that, using --no-hostname_lookup, in which case the IP itself
+ is used.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ --[no-]hostname_lookup
+ </td>
+ <td>
+ Whether we should execute a lookup to find out the server's hostname,
+ if not explicitly set (via, e.g., `--hostname`).
+ True by default; if set to 'false' it will cause Mesos
+ to use the IP address, unless the hostname is explicitly set.
</td>
</tr>
<tr>
@@ -853,6 +866,15 @@ file:///path/to/file (where file contain
</tr>
<tr>
<td>
+ --systemd_runtime_directory=VALUE
+ </td>
+ <td>
+ The path to the systemd system run time directory
+ (default: /run/systemd/system)
+ </td>
+ </tr>
+ <tr>
+ <td>
--container_disk_watch_interval=VALUE
</td>
<td>
@@ -1141,10 +1163,22 @@ file:///path/to/file (where file contain
--hostname=VALUE
</td>
<td>
- The hostname the slave should report.
- <p/>
+ The hostname the agent node should report.<br>
If left unset, the hostname is resolved from the IP address
- that the slave binds to.
+ that the slave binds to; unless the user explicitly prevents
+ that, using --no-hostname_lookup, in which case the IP itself
+ is used.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ --[no-]hostname_lookup
+ </td>
+ <td>
+ Whether we should execute a lookup to find out the server's hostname,
+ if not explicitly set (via, e.g., `--hostname`).
+ True by default; if set to 'false' it will cause Mesos
+ to use the IP address, unless the hostname is explicitly set.
</td>
</tr>
<tr>
@@ -1161,6 +1195,18 @@ file:///path/to/file (where file contain
</tr>
<tr>
<td>
+ --launcher=VALUE
+ </td>
+ <td>
+ The launcher to be used for Mesos containerizer. It could either be
+ 'linux' or 'posix'. The Linux launcher is required for cgroups
+ isolation and for any isolators that require Linux namespaces such as
+ network, pid, etc. If unspecified, the slave will choose the Linux
+ launcher if it's running as root on Linux.
+ </td>
+ </tr>
+ <tr>
+ <td>
--launcher_dir=VALUE
</td>
<td>
@@ -1168,6 +1214,14 @@ file:///path/to/file (where file contain
</td>
</tr>
<tr>
+ <td>
+ --image_providers=VALUE
+ </td>
+ <td>
+ Comma separated list of supported image providers, e.g., 'APPC,DOCKER'.
+ </td>
+ </tr>
+ <tr>
<td>
--modules=VALUE
</td>
Modified: mesos/site/source/documentation/latest/maintenance.md
URL: http://svn.apache.org/viewvc/mesos/site/source/documentation/latest/maintenance.md?rev=1705246&r1=1705245&r2=1705246&view=diff
==============================================================================
--- mesos/site/source/documentation/latest/maintenance.md (original)
+++ mesos/site/source/documentation/latest/maintenance.md Fri Sep 25 07:42:15 2015
@@ -8,6 +8,7 @@ Operators regularly need to perform main
a Mesos cluster. Most Mesos upgrades can be done without affecting running
tasks, but there are situations where maintenance may affect running tasks.
For example:
+
* Hardware repair
* Kernel upgrades
* Agent upgrades (e.g. adjusting agent attributes or resources)
@@ -27,6 +28,7 @@ which manages the Mesos cluster.
Maintenance primitives add several new concepts to the Mesos cluster.
Those concepts are:
+
* **Maintenance** - An operation that makes resources on a machine unavailable,
either temporarily or permanently.
* **Maintenance window** - A set of machines and an associated interval during
@@ -82,7 +84,8 @@ For example, in a cluster of three machi
machines for one hour of maintenance, followed by another hour for the last
machine. The timestamps for unavailability are in nanoseconds since the epoch.
The schedule might look like:
-```json
+
+```
{
"windows" : [
{
@@ -108,7 +111,8 @@ The schedule might look like:
```
The operator then posts the schedule to the master's maintenance endpoints.
-```bash
+
+```
curl http://localhost:5050/master/maintenance/schedule
-H "Content-type: application/json"
-X POST
@@ -150,6 +154,7 @@ To cancel a maintenance schedule, the op
### Draining mode
As soon as a schedule is posted to the Mesos master, the following things occur:
+
* The schedule is stored in the replicated log. This means
the schedule is persisted in case of master failover.
* All machines in the schedule are immediately transitioned into Draining
@@ -165,6 +170,7 @@ With this additional information, framew
maintenance-aware fashion. Inverse offers communicate the frameworks' ability
to conform to the maintenance schedule.
For example:
+
* A framework with long-running tasks may choose agents with no unavailability
or with unavailability further in the future.
* A datastore may choose to start a new replica if one of its agents is
@@ -203,13 +209,15 @@ maintenance endpoint.
See the definition of a [MachineID](https://github.com/apache/mesos/blob/016b02d7ed5a65bcad9261a133c8237c2df66e6e/include/mesos/v1/mesos.proto#L157-L167).
For example, to start maintenance on two machines:
-```json
+
+```
[
{ "hostname" : "machine1", "ip" : "10.0.0.1" },
{ "hostname" : "machine2", "ip" : "10.0.0.2" }
]
```
-```bash
+
+```
curl http://localhost:5050/master/machine/down
-H "Content-type: application/json"
-X POST
@@ -217,6 +225,7 @@ curl http://localhost:5050/master/machin
```
The master checks that a list of machines has the following properties:
+
* The list of machines must not be empty.
* Each machine must only appear once.
* Each machine must have at least a hostname or IP included.
@@ -250,13 +259,15 @@ When maintenance is complete, or if main
the operator can stop maintenance. The process is very similar
to starting maintenance (same validation criterion as the previous section).
The operator posts a list of machines to the master's endpoints:
-```json
+
+```
[
{ "hostname" : "machine1", "ip" : "10.0.0.1" },
{ "hostname" : "machine2", "ip" : "10.0.0.2" }
]
```
-```bash
+
+```
curl http://localhost:5050/master/machine/up
-H "Content-type: application/json"
-X POST
Modified: mesos/site/source/documentation/latest/reservation.md
URL: http://svn.apache.org/viewvc/mesos/site/source/documentation/latest/reservation.md?rev=1705246&r1=1705245&r2=1705246&view=diff
==============================================================================
--- mesos/site/source/documentation/latest/reservation.md (original)
+++ mesos/site/source/documentation/latest/reservation.md Fri Sep 25 07:42:15 2015
@@ -217,7 +217,8 @@ which we specify with the resources to b
The unreserved resources may now be offered to other frameworks.
-### `/reserve` (_Coming Soon_)
+### `/reserve` (since 0.25.0)
+
Suppose we want to reserve 8 CPUs and 4096 MB of RAM for the `ads` role on
a slave with id=`<slave_id>`. We send an HTTP POST request to the `/reserve`
@@ -256,7 +257,8 @@ The user receives one of the following H
* `409 Conflict`: Insufficient resources to satisfy the reserve operation.
-### `/unreserve` (_Coming Soon_)
+### `/unreserve` (since 0.25.0)
+
Suppose we want to unreserve the resources that we dynamically reserved above.
We can send an HTTP POST request to the `/unreserve` HTTP endpoint like so:
Modified: mesos/site/source/downloads.html.md
URL: http://svn.apache.org/viewvc/mesos/site/source/downloads.html.md?rev=1705246&r1=1705245&r2=1705246&view=diff
==============================================================================
--- mesos/site/source/downloads.html.md (original)
+++ mesos/site/source/downloads.html.md Fri Sep 25 07:42:15 2015
@@ -8,12 +8,20 @@ breadcrumb: Downloads
<h4>Previous Releases</h4>
<ul>
+ <li><a href="http://archive.apache.org/dist/mesos/0.24.0/">0.24.0</a>
+ (<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12329851">Release Notes</a>)</li>
+ <li><a href="http://archive.apache.org/dist/mesos/0.23.1/">0.23.1</a>
+ (<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12333553">Release Notes</a>)</li>
<li><a href="http://archive.apache.org/dist/mesos/0.23.0/">0.23.0</a>
(<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12328728">Release Notes</a>)</li>
+ <li><a href="http://archive.apache.org/dist/mesos/0.22.2/">0.22.2</a>
+ (<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12333645">Release Notes</a>)</li>
<li><a href="http://archive.apache.org/dist/mesos/0.22.1/">0.22.1</a>
(<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12329855">Release Notes</a>)</li>
<li><a href="http://archive.apache.org/dist/mesos/0.22.0/">0.22.0</a>
(<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12328650">Release Notes</a>)</li>
+ <li><a href="http://archive.apache.org/dist/mesos/0.21.2/">0.21.2</a>
+ (<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12333646">Release Notes</a>)</li>
<li><a href="http://archive.apache.org/dist/mesos/0.21.1/">0.21.1</a>
(<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12329076">Release Notes</a>)</li>
<li><a href="http://archive.apache.org/dist/mesos/0.21.0/">0.21.0</a>
@@ -60,8 +68,8 @@ breadcrumb: Downloads
<div class="col-md-8">
<h1>Download Mesos</h1>
<p>Download the most recent stable release:
- <a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/mesos/0.24.0/">0.24.0</a>
- (<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12329851">Release Notes</a>)
+ <a href="http://www.apache.org/dyn/mirrors/mirrors.cgi/mesos/0.24.1/">0.24.1</a>
+ (<a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&version=12333552">Release Notes</a>)
</p>
<h4>Getting the code via source control</h4>
Modified: mesos/site/source/index.html.md
URL: http://svn.apache.org/viewvc/mesos/site/source/index.html.md?rev=1705246&r1=1705245&r2=1705246&view=diff
==============================================================================
--- mesos/site/source/index.html.md (original)
+++ mesos/site/source/index.html.md Fri Sep 25 07:42:15 2015
@@ -4,11 +4,11 @@ title: Apache Mesos
<div class="container-fluid homepage jumbotron">
<div class="row">
- <div class="col-md-7 nopadding">
+ <div class="col-md-7">
<h1>Program against your datacenter like itâs a single pool of resources</h1>
<p class="lead">Apache Mesos abstracts CPU, memory, storage, and other compute resources away from machines (physical or virtual), enabling fault-tolerant and elastic distributed systems to easily be built and run effectively.</p>
- <p> <a href="downloads/"><span class="glyphicon glyphicon-download"></span> Download Mesos 0.24.0</a> or learn how to <a href="gettingstarted/">get started</a></p>
+ <p> <a href="downloads/"><span class="glyphicon glyphicon-download"></span> Download Mesos 0.24.1</a> or learn how to <a href="gettingstarted/">get started</a></p>
</div>
<div class="col-md-5 text-center download">
<div class="homepage-featured">
@@ -22,20 +22,18 @@ title: Apache Mesos
</div>
</div>
-<hr>
-
<!-- lowersection -->
<div class="row">
<div class="col-md-7">
<h3>What is Mesos?</h3>
- <h4>A distributed systems kernel</h4>
- <p>Mesos is built using the same principles as the Linux kernel, only at a different level of abstraction. The Mesos kernel runs on every machine and provides applications (e.g., Hadoop, Spark, Kafka, Elastic Search) with APIâs for resource management and scheduling across entire datacenter and cloud environments.</p>
+ <h4>A distributed systems kernel</h4>
+ <p>Mesos is built using the same principles as the Linux kernel, only at a different level of abstraction. The Mesos kernel runs on every machine and provides applications (e.g., Hadoop, Spark, Kafka, Elastic Search) with APIâs for resource management and scheduling across entire datacenter and cloud environments.</p>
<h3>Project Features</h3>
<ul>
<li>Scalability to 10,000s of nodes</li>
<li>Fault-tolerant replicated master and slaves using ZooKeeper</li>
- <li>Support for Docker containers</li>
+ <li>Support for Docker containers</li>
<li>Native isolation between tasks with Linux Containers</li>
<li>Multi-resource scheduling (memory, CPU, disk, and ports)</li>
<li>Java, Python and C++ APIs for developing new parallel applications</li>
@@ -45,22 +43,20 @@ title: Apache Mesos
<div class="col-md-5">
<h3>News</h3>
<ul>
- <li><em>September 21, 2015</em> - Mesos 0.24.0 is released! See the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.24.0">CHANGELOG</a> and <a href="/blog/mesos-0-24-0-released/">blog post</a> for more details.</li>
+ <li><em>September 24, 2015</em> - Mesos 0.24.1 is released! See the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.24.1">CHANGELOG</a> and <a href="/blog/mesos-0-24-1-and-more-released/">blog post</a> for details.</li>
+ <li><em>September 21, 2015</em> - Mesos 0.24.0 is released! See the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.24.0">CHANGELOG</a> and <a href="/blog/mesos-0-24-0-released/">blog post</a> for details.</li>
<li><em>September 17, 2015</em> - <a href="/blog/mesoscon-europe-2015-schedule-announced/">MesosCon Europe Schedule and Diversity Scholarship</a></li>
<li><em>August 5, 2015</em> - <a href="/blog/mesoscon-goes-europe/">MesosCon goes Europe</a></li>
- <li><em>July 28, 2015</em> - <a href="/blog/register-for-mesoscon-seattle-save/">Register for #MesosCon by 7/31 and Save $100</a></li>
<li><em>July 22, 2015</em> - Mesos 0.23.0 is released! See the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.23.0">CHANGELOG</a> and <a href="/blog/mesos-0-23-0-released/">blog post</a> for more details.</li>
- <li><em>July 13, 2015</em> - MesosCon pre-conference and social activities announced! See the <a href="/blog/mesoscon-seattle-preconference-and-social-activities/">blog post</a> for more details.</li>
- <li><em>July 1, 2015</em> - MesosCon Seattle 2015 keynote speakers announced! See the <a href="/blog/mesoscon-seattle-keynote-speakers-announced/">blog post</a> for more details.</li>
- </ul>
+ </ul>
- <h3>Follow Us</h3>
- <span class="social">
- <a href="https://twitter.com/ApacheMesos" class="twitter-follow-button" data-show-count="false" data-size="large">Follow @ApacheMesos</a>
- <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script>
- <a href="https://twitter.com/intent/tweet?button_hashtag=mesos" class="twitter-hashtag-button" data-size="large" data-related="ApacheMesos">Tweet #mesos</a>
- <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script>
- </span>
+ <h3>Follow Us</h3>
+ <span class="social">
+ <a href="https://twitter.com/ApacheMesos" class="twitter-follow-button" data-show-count="false" data-size="large">Follow @ApacheMesos</a>
+ <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script>
+ <a href="https://twitter.com/intent/tweet?button_hashtag=mesos" class="twitter-hashtag-button" data-size="large" data-related="ApacheMesos">Tweet #mesos</a>
+ <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script>
+ </span>
</div>
</div>
<!-- /lowersection -->