| |
| <feed xmlns="http://www.w3.org/2005/Atom"> |
| <title>Apache Mesos Blog</title> |
| <id>http://mesos.apache.org/blog</id> |
| <link href="http://mesos.apache.org/blog" /> |
| <link href="http://mesos.apache.org/blog/feed.xml" rel="self"/> |
| <updated>2017-03-14T00:00:00Z</updated> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-1-1-1-released/</id> |
| <link href="/blog/mesos-1-1-1-released/" /> |
| <title> |
| Apache Mesos 1.1.1 Released |
| </title> |
| <updated>2017-03-14T00:00:00Z</updated> |
| <author> |
| <name>AlexR</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 1.1.1, is now available for |
| <a href="http://mesos.apache.org/downloads">download</a>. This release includes some |
| important bug fixes and improvements on top of 1.1.0. It is highly recommended |
| that users use this version if you are considering using Mesos 1.1. More |
| specifically, this release includes the following major fixes and improvements:</p> |
| |
| <ul> |
| <li>[MESOS-6002] - The whiteout file cannot be removed correctly using aufs backend.</li> |
| <li>[MESOS-6010] - Docker registry puller shows decode error &ldquo;No response decoded&rdquo;.</li> |
| <li>[MESOS-6142] - Frameworks may RESERVE for an arbitrary role.</li> |
| <li>[MESOS-6360] - The handling of whiteout files in provisioner is not correct.</li> |
| <li>[MESOS-6411] - Add documentation for CNI port-mapper plugin.</li> |
| <li>[MESOS-6526] - <code>mesos-containerizer launch --environment</code> exposes executor env vars in <code>ps</code>.</li> |
| <li>[MESOS-6571] - Add &ldquo;&ndash;task&rdquo; flag to mesos-execute</li> |
| <li>[MESOS-6597] - Include v1 Operator API protos in generated JAR and python packages.</li> |
| <li>[MESOS-6606] - Reject optimized builds with libcxx before 3.9</li> |
| <li>[MESOS-6621] - SSL downgrade path will CHECK-fail when using both temporary and persistent sockets</li> |
| <li>[MESOS-6624] - Master WebUI does not work on Firefox 45</li> |
| <li>[MESOS-6676] - Always re-link with scheduler during re-registration.</li> |
| <li>[MESOS-6848] - The default executor does not exit if a single task pod fails.</li> |
| <li>[MESOS-6852] - Nested container&rsquo;s launch command is not set correctly in docker/runtime isolator.</li> |
| <li>[MESOS-6917] - Segfault when the executor sets an invalid UUID when sending a status update.</li> |
| <li>[MESOS-7008] - Quota not recovered from registry in empty cluster.</li> |
| <li>[MESOS-7133] - mesos-fetcher fails with openssl-related output.</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release |
| <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.1.1">CHANGELOG</a></p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 1.1.0 cluster to Mesos 1.1.1 are straightforward. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> |
| for detailed information on upgrading to Mesos 1.1.1.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. If you |
| run into any issues, please let us know on the |
| <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 15 contributors who made 1.1.1 possible:</p> |
| |
| <p>Aaron Wood, Alexander Rukletsov, Anand Mazumdar, Avinash sridharan, Benjamin Bannier, Gastón Kleiman, Gilbert Song, Haosdent Huang, Jan Schlicht, Jiang Yan Xu, Jie Yu, Joseph Wu, Michael Park, Neil Conway, Qian Zhang, Till Toenshoff, Vijay Srinivasaraghavan, Vinod Kone, haosdent huang.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-1-2-0-released/</id> |
| <link href="/blog/mesos-1-2-0-released/" /> |
| <title> |
| Apache Mesos 1.2.0 Released |
| </title> |
| <updated>2017-03-08T00:00:00Z</updated> |
| <author> |
| <name>Adam</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 1.2.0, is now available for <a href="/downloads">download</a>. This release includes the following features and improvements:</p> |
| |
| <ul> |
| <li><p><a href="https://issues.apache.org/jira/browse/MESOS-5931">MESOS-5931</a> - |
| <strong>Experimental</strong> support for auto backend in Mesos Containerizer, |
| prefering overlayfs then aufs. Please note that the bind backend needs to be |
| specified explicitly through the agent flag <code>--image_provisioner_backend</code> |
| since it requires the sandbox already existed.</p></li> |
| <li><p><a href="https://issues.apache.org/jira/browse/MESOS-6402">MESOS-6402</a> - |
| <strong>Experimental</strong> support for rlimit in Mesos containerizer. |
| The isolator adds support for setting POSIX resource limits (rlimits) for |
| containers launched using the Mesos containerizer. POSIX rlimits can be used |
| to control the resources a process can consume. See |
| <a href="/documentation/latest/posix_rlimits">docs</a> for details.</p></li> |
| <li><p><a href="https://issues.apache.org/jira/browse/MESOS-6419">MESOS-6419</a> - |
| <strong>Experimental</strong>: Teardown unregistered frameworks. The master |
| now treats recovered frameworks very similarly to frameworks that are registered |
| but currently disconnected. For example, recovered frameworks will be reported |
| via the normal &ldquo;frameworks&rdquo; key when querying HTTP endpoints. This means there |
| is no longer a concept of &ldquo;orphan tasks&rdquo;: if the master knows about a task, the |
| task will be running under a framework. Similarly, &ldquo;teardown&rdquo; operations on |
| recovered frameworks will now work correctly.</p></li> |
| <li><p><a href="https://issues.apache.org/jira/browse/MESOS-6460">MESOS-6460</a> - |
| <strong>Experimental</strong>: Container Attach and Exec. This feature adds new |
| <a href="/documentation/latest/operator-http-api">Agent APIs</a> for attaching a remote |
| client to the stdin, stdout, and stderr of a running Mesos task, as well as |
| an API for launching new processes inside the same container as a running |
| Mesos task and attaching to its stdin, stdout, and stderr. At a high level, |
| these APIs mimic functionality similar to docker attach and docker exec. |
| The primary motivation for such functionality is to enable users to debug |
| their running Mesos tasks.</p></li> |
| <li><p><a href="https://issues.apache.org/jira/browse/MESOS-6758">MESOS-6758</a> - |
| <strong>Experimental</strong> support for &lsquo;Basic&rsquo; auth docker private registry |
| on Mesos Containerizer. Until now, the mesos containerizer always assumed |
| Bearer auth, but we now also support basic auth for private registries. Please |
| note that the AWS ECS uses Basic authorization but it does not work yet due to |
| the redirect issue <a href="https://issues.apache.org/jira/browse/MESOS-5172">MESOS-5172</a>.</p></li> |
| </ul> |
| |
| |
| <p>More than 200 other bug fixes and improvements made it into this release. For full release notes with all features and bug fixes, please refer to the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.2.0">CHANGELOG</a>.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 1.1.0 cluster to Mesos 1.2.0 are straightforward. There are just some minor, backwards compatible deprecations. |
| Please refer to the <a href="/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 1.2.0.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. |
| If you run into any issues, please let us know on the <a href="/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 56 contributors who made Mesos 1.2.0 possible:</p> |
| |
| <p>Aaron Wood, Abhishek Dasgupta, Adam B, Alexander Rojas, Alexander Rukletsov, Alex Clemmer, Anand Mazumdar, Andrew Schwartzmeyer, Anindya Sinha, Armand Grillet, Avinash Sridharan, Benjamin Bannier, Benjamin Hindman, Benjamin Mahler, Bruce Merry, Chengwei Yang, Daniel Pravat, David Forsythe, Dmitry Zhuk, Gastón Kleiman, Gilbert Song, Greg Mann, Guangya Liu, Haosdent Huang, Ilya Pronin, Jacob Janco, James Peach, Jan Schlicht, Jay Guo, Jeff Malnick, Jiang Yan Xu, Jie Yu, Joerg Schad Johannes Unterstein, Joris Van Remoortere, Joseph Wu, Kevin Klues, Lior Zeno, Manuwela Kanade, Megha Sharma, Michael Park, Miguel Bernadin, Neil Conway, Nicholas Sun, Qian Zhang, Ronald Petty, Santhosh Kumar Shanmugham, Sivaram Kannan, Srinivas Brahmaroutu, Thomas Maurice, Till Toenshoff, Tomasz Janiszewski, Vijay Srinivasaraghavan, Vinod Kone, Yubo Li, and Zhitao Li.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-28-3-released/</id> |
| <link href="/blog/mesos-0-28-3-released/" /> |
| <title> |
| Apache Mesos 0.28.3 Released |
| </title> |
| <updated>2016-12-20T00:00:00Z</updated> |
| <author> |
| <name>Anand Mazumdar</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.28.3, is now available for <a href="http://mesos.apache.org/downloads">download</a>. This release includes some important bug fixes and improvements on top of 0.28.2. It is highly recommended that users use this version if you are considering using Mesos 0.28. More specifically, this release includes the following major fixes and improvements:</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2043">MESOS-2043</a> - Framework auth fail with timeout error and never get authenticated</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5571">MESOS-5571</a> - Scheduler JNI throws exception when the major versions of JAR and libmesos don&rsquo;t match.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5691">MESOS-5691</a> - SSL downgrade support will leak sockets in CLOSE_WAIT status.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5698">MESOS-5698</a> - Quota sorter not updated for resource changes at agent.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5723">MESOS-5723</a> - SSL-enabled libprocess will leak incoming links to forks.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5763">MESOS-5763</a> - Task stuck in fetching is not cleaned up after &ndash;executor_registration_timeout.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5913">MESOS-5913</a> - Stale socket FD usage when using libevent + SSL.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5943">MESOS-5943</a> - Incremental http parsing of URLs leads to decoder error.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5986">MESOS-5986</a> - SSL Socket CHECK can fail after socket receives EOF.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-6104">MESOS-6104</a> - Potential FD double close in libevent&rsquo;s</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-6142">MESOS-6142</a> - Frameworks may RESERVE for an arbitrary role.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-6233">MESOS-6233</a> - Master CHECK fails during recovery while relinking to other masters.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-6299">MESOS-6299</a> - Master doesn&rsquo;t remove task from pending when it is invalid.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-6457">MESOS-6457</a> - Tasks shouldn&rsquo;t transition from TASK_KILLING to TASK_RUNNING.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-6502">MESOS-6502</a> - _version uses incorrect MESOS<em>{MAJOR,MINOR,PATCH}</em>VERSION in libmesos java binding.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-6527">MESOS-6527</a> - Memory leak in the libprocess request decoder.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-6621">MESOS-6621</a> - SSL downgrade path will CHECK-fail when using both temporary and persistent sockets.</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.3">CHANGELOG</a></p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.28.2 cluster to Mesos 0.28.3 are straightforward. Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.28.3.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 15 contributors who made 0.28.3 possible:</p> |
| |
| <p>Anand Mazumdar, Benjamin Bannier, Benjamin Mahler, David Robinson, Gastón Kleiman, Gilbert Song, Greg Mann, Joris Van Remoortere, Joseph Wu, Neil Conway, Silas Snider, Vinod Kone, Yan Xu, Zhitao Li, Zhou Xing</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-1-1-0-released/</id> |
| <link href="/blog/mesos-1-1-0-released/" /> |
| <title> |
| Apache Mesos 1.1.0 Released |
| </title> |
| <updated>2016-11-10T00:00:00Z</updated> |
| <author> |
| <name>Till Toenshoff</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 1.1.0, is now available for <a href="http://mesos.apache.org/downloads">download</a>.</p> |
| |
| <p>This release includes the following features and improvements:</p> |
| |
| <ul> |
| <li><p>[MESOS-2449] - <strong>Experimental</strong> support for launching a group of tasks |
| via a new <code>LAUNCH_GROUP</code> Offer operation. Mesos will guarantee that either |
| all tasks or none of the tasks in the group are delivered to the executor. |
| Executors receive the task group via a new <code>LAUNCH_GROUP</code> event.</p></li> |
| <li><p>[MESOS-2533] - <strong>Experimental</strong> support for HTTP and HTTPS health checks. |
| Executors may now use the updated <code>HealthCheck</code> protobuf to implement |
| HTTP(S) health checks. Both default executors (command and docker) leverage |
| <code>curl</code> binary for sending HTTP(S) requests and connect to <code>127.0.0.1</code>, |
| hence a task must listen on all interfaces. On Linux, for BRIDGE and USER |
| modes, docker executor enters the task&rsquo;s network namespace.</p></li> |
| <li><p>[MESOS-3421] - <strong>Experimental</strong> Support sharing of resources across |
| containers. Currently persistent volumes are the only resources allowed to |
| be shared.</p></li> |
| <li><p>[MESOS-3567] - <strong>Experimental</strong> support for TCP health checks. Executors |
| may now use the updated <code>HealthCheck</code> protobuf to implement TCP health |
| checks. Both default executors (command and docker) connect to <code>127.0.0.1</code>, |
| hence a task must listen on all interfaces. On Linux, for BRIDGE and USER |
| modes, docker executor enters the task&rsquo;s network namespace.</p></li> |
| <li><p>[MESOS-4324] - Allow tasks to access persistent volumes in either a |
| read-only or read-write manner. Using a volume in read-only mode can |
| simplify sharing that volume between multiple tasks on the same agent.</p></li> |
| <li><p>[MESOS-5275] - <strong>Experimental</strong> support for linux capabilities. Frameworks |
| or operators now have fine-grained control over the capabilities that a |
| container may have. This allows a container to run as root, but not have all |
| the privileges associated with the root user (e.g., CAP_SYS_ADMIN).</p></li> |
| <li><p>[MESOS-5344] - <strong>Experimental</strong> support for partition-aware Mesos |
| frameworks. In previous Mesos releases, when an agent is partitioned from |
| the master and then reregisters with the cluster, all tasks running on the |
| agent are terminated and the agent is shutdown. In Mesos 1.1, partitioned |
| agents will no longer be shutdown when they reregister with the master. By |
| default, tasks running on such agents will still be killed (for backward |
| compatibility); however, frameworks can opt-in to the new PARTITION_AWARE |
| capability. If they do this, their tasks will not be killed when a partition |
| is healed. This allows frameworks to define their own policies for how to |
| handle partitioned tasks. Enabling the PARTITION_AWARE capability also |
| introduces a new set of task states: TASK_UNREACHABLE, TASK_DROPPED, |
| TASK_GONE, TASK_GONE_BY_OPERATOR, and TASK_UNKNOWN. These new states are |
| intended to eventually replace the TASK_LOST state.</p></li> |
| <li><p>[MESOS-5788] - <strong>Experimental</strong> support for Java scheduler adapter. This |
| adapter allows framework developers to toggle between the old/new API |
| (driver/scheduler library) implementations, thereby allowing them to easily |
| transition their frameworks to the new v1 Scheduler API.</p></li> |
| <li><p>[MESOS-6014] - <strong>Experimental</strong> A new port-mapper CNI plugin, the |
| <code>mesos-cni-port-mapper</code> has been introduced. For Mesos containers, with the |
| CNI port-mapper plugin, users can now expose container ports through host |
| ports using DNAT. This is especially useful when Mesos containers are |
| attached to isolated CNI networks such as private bridge networks, and the |
| services running in the container needs to be exposed outside these |
| isolated networks.</p></li> |
| <li><p>[MESOS-6077] - <strong>Experimental</strong> A new default executor is introduced which |
| frameworks can use to launch task groups as nested containers. All the |
| nested containers share resources likes cpu, memory, network and volumes.</p></li> |
| </ul> |
| |
| |
| <h4>Deprecations</h4> |
| |
| <ul> |
| <li><p>The following metrics are deprecated and will be removed in Mesos 1.4: |
| master/slave_shutdowns_scheduled, |
| master/slave_shutdowns_canceled, |
| slave_shutdowns_completed. |
| As of Mesos 1.1.0, these metrics will always be zero. The following new |
| metrics have been introduced as replacements: |
| master/slave_unreachable_scheduled, |
| master/slave_unreachable_canceled, |
| master/slave_unreachable_completed.</p></li> |
| <li><p>[MESOS-5955] - Health check binary &ldquo;mesos-health-check&rdquo; is removed.</p></li> |
| <li><p>[MESOS-6371] - Remove the &lsquo;recover()&rsquo; interface in &lsquo;ContainerLogger&rsquo;.</p></li> |
| </ul> |
| |
| |
| <h4>Additional API Changes</h4> |
| |
| <ul> |
| <li><p>[MESOS-6204] - A new agent flag called <code>--runtime_dir</code>. Unlike |
| <code>--work_dir</code> which persists data across reboots, <code>--runtime_dir</code> is designed |
| to checkpoint state that should persist across agent restarts, but not |
| across reboots. By default this flag is set to <code>/var/run/mesos</code> when run as |
| root and <code>os::temp/mesos/runtime/</code> when run as non-root.</p></li> |
| <li><p>[MESOS-6220] - HTTP handler failures should result in 500 rather than |
| 503 responses. This means that when using the master or agent endpoints, |
| failures will now result in a <code>500 Internal Server Error</code> rather than a |
| <code>503 Service Unavailable</code>.</p></li> |
| <li><p>[MESOS-6241] - New API calls (LAUNCH_NESTED_CONTAINER, |
| KILL_NESTED_CONTAINER and WAIT_NESTED_CONTAINER) have been added to the |
| v1 Agent API to manage nested containers within an executor container.</p></li> |
| </ul> |
| |
| |
| <h4>Unresolved Critical Issues</h4> |
| |
| <ul> |
| <li><p>[MESOS-3794] - Master should not store arbitrarily sized data in ExecutorInfo.</p></li> |
| <li><p>[MESOS-4642] - Mesos Agent Json API can dump binary data from log files out as invalid JSON.</p></li> |
| <li><p>[MESOS-5396] - After failover, master does not remove agents with same UPID.</p></li> |
| <li><p>[MESOS-5856] - Logrotate ContainerLogger module does not rotate logs when run as root with <code>--switch_user</code>.</p></li> |
| <li><p>[MESOS-6142] - Frameworks may RESERVE for an arbitrary role.</p></li> |
| <li><p>[MESOS-6327] - Large docker images causes container launch failures: Too many levels of symbolic links.</p></li> |
| <li><p>[MESOS-6360] - The handling of whiteout files in provisioner is not correct.</p></li> |
| <li><p>[MESOS-6419] - The &lsquo;master/teardown&rsquo; endpoint should support tearing down &lsquo;unregistered_frameworks&rsquo;.</p></li> |
| <li><p>[MESOS-6432] - Roles with quota assigned can &ldquo;game&rdquo; the system to receive excessive resources.</p></li> |
| </ul> |
| |
| |
| <h4>All Experimental Features</h4> |
| |
| <ul> |
| <li><p>[MESOS-2449] - Support group of tasks (Pod) constructs and API in Mesos.</p></li> |
| <li><p>[MESOS-2533] - Support HTTP checks in Mesos.</p></li> |
| <li><p>[MESOS-3094] - Mesos on Windows.</p></li> |
| <li><p>[MESOS-3421] - Support sharing of resources across task instances.</p></li> |
| <li><p>[MESOS-3567] - Support TCP checks in Mesos.</p></li> |
| <li><p>[MESOS-4312] - Porting Mesos on Power (ppc64le).</p></li> |
| <li><p>[MESOS-4355] - Implement isolator for Docker volume.</p></li> |
| <li><p>[MESOS-4641] - Support Container Network Interface (CNI).</p></li> |
| <li><p>[MESOS-4791] - Operator API v1.</p></li> |
| <li><p>[MESOS-4828] - XFS disk quota isolator.</p></li> |
| <li><p>[MESOS-5275] - Add capabilities support for unified containerizer.</p></li> |
| <li><p>[MESOS-5344] - Partition-aware Mesos frameworks.</p></li> |
| <li><p>[MESOS-5788] - Added JAVA API adapter for seamless transition to new scheduler API.</p></li> |
| <li><p>[MESOS-6014] - Added port mapping CNI plugin.</p></li> |
| <li><p>[MESOS-6077] - Added a default (task group) executor.</p></li> |
| </ul> |
| |
| |
| <p>Furthermore, several bugfixes and improvements made it into this release. |
| For full release notes with all features and bug fixes, please refer to the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.1.0">CHANGELOG</a>.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 1.0.0 cluster to Mesos 1.1.0 are straightforward. There are just some minor, backwards compatible deprecations. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 1.1.0.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. |
| If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 73 contributors who made 1.1.0 possible:</p> |
| |
| <p>Aaron Wood, Abhishek Dasgupta, Alberto, Aleksandar Prokopec, Alex Clemmer, Alexander Rojas, Alexander Rukletsov, Ammar Askar, Anand Mazumdar, Andy Pang, Anindya Sinha, Artem Harutyunyan, Attila Szarvas, Avinash sridharan, Bart Spaans, Benjamin Bannier, Benjamin Hindman, Benjamin Mahler, Charles Allen, ChrisPaprocki, Daniel Pravat, Dario Rexin, Dave Lester, Gaojin CAO, Gastón Kleiman, Gilbert Song, Giulio Eulisse, Graham Taylor, Greg Mann, Guangya Liu, Haris Choudhary, Ian Babrou, Ilya Pronin, Jacob Janco, Jan Schlicht, Jay Guo, Jiang Yan Xu, Jie Yu, Joerg Schad, Joris Van Remoortere, Joseph Wu, Ken Sipe, Kevin Klues, Klaus Ma, Kunal Thakar, Lawrence Wu, Lijun Tang, Lukas Loesche, Mao Geng, Megha Sharma, Michael Park, Miguel Bernadin, Neil Conway, Pierre Cheynier, Qian Zhang, Roger Ignazio, Santhosh Kumar Shanmugham, Srinivas Brahmaroutu, Till Toenshoff, Tomasz Janiszewski, Vinod Kone, Will Rouesnel, Yong Tang, Yongqiao Wang, Yubo Li, Zhitao Li, anthony caiafa, gnolan, haosdent huang, janisz, uzyexe, zhou xing</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-1-0-1-released/</id> |
| <link href="/blog/mesos-1-0-1-released/" /> |
| <title> |
| Apache Mesos 1.0.1 Released |
| </title> |
| <updated>2016-08-23T00:00:00Z</updated> |
| <author> |
| <name>Vinod Kone</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 1.0.1, is now available for <a href="http://mesos.apache.org/downloads">download</a>. This release includes some important bug fixes and improvements on top of 1.0.0. It is highly recommended to use this version if you are considering using Mesos 1.0. More specifically, this release includes the following fixes and improvements:</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5388">MESOS-5388</a> - MesosContainerizerLaunch flags execute arbitrary commands via shell.</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5862">MESOS-5862</a> - External links to .md files broken.</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5911">MESOS-5911</a> - Webui redirection to leader in browser does not work</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5913">MESOS-5913</a> - Stale socket FD usage when using libevent + SSL.</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5922">MESOS-5922</a> - mesos-agent &ndash;help exit status is 1</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5923">MESOS-5923</a> - Ubuntu 14.04 LTS GPU Isolator &ldquo;/run&rdquo; directory is noexec</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5927">MESOS-5927</a> - Unable to run &ldquo;scratch&rdquo; Dockerfiles with Unified Containerizer.</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5928">MESOS-5928</a> - Agent&rsquo;s &lsquo;&ndash;version&rsquo; flag doesn&rsquo;t work</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5930">MESOS-5930</a> - Orphan tasks can show up as running after they have finished.</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5943">MESOS-5943</a> - Incremental http parsing of URLs leads to decoder error</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5945">MESOS-5945</a> - NvidiaVolume::create() should check for root before creating volume</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5959">MESOS-5959</a> - All non-root tests fail on GPU machine</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5969">MESOS-5969</a> - Linux &lsquo;MountInfoTable&rsquo; entries not sorted as expected</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5982">MESOS-5982</a> - NvidiaVolume errors out if any binary is missing</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5986">MESOS-5986</a> - SSL Socket CHECK can fail after socket receives EOF</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5988">MESOS-5988</a> - PollSocketImpl can write to a stale fd.</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5830">MESOS-5830</a> - Make a sweep to trim excess space around angle brackets</p> |
| |
| <p><a href="https://issues.apache.org/jira/browse/MESOS-5970">MESOS-5970</a> - Remove HTTP_PARSER_VERSION_MAJOR &lt; 2 code in decoder.</p> |
| |
| <p>Full release notes are available in the release <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.1">CHANGELOG</a></p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 1.0.0 cluster to Mesos 1.0.1 are straightforward. Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 1.0.1.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing ld Slack/IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 12 contributors who made 1.0.1 possible</p> |
| |
| <p>Anand Mazumdar, Benjamin Mahler, Gilbert Song, Greg Mann, Jiang Yan Xu, Jie Yu, Joris Van Remoortere, Kevin Klues, Pierre Cheynier, Vinod Kone, haosdent huang and zhou xing.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-1-0-0-released/</id> |
| <link href="/blog/mesos-1-0-0-released/" /> |
| <title> |
| Apache Mesos 1.0.0 Released |
| </title> |
| <updated>2016-07-27T00:00:00Z</updated> |
| <author> |
| <name>Vinod Kone</name> |
| </author> |
| <content type="html"> |
| <p>Mesos 1.0 release is finally here for <a href="http://mesos.apache.org/downloads">download</a>!</p> |
| |
| <p>As most of you know, Apache Mesos has been running in production at some of the largest Internet companies like <a href="https://twitter.com">Twitter</a>, <a href="https://netflix.com">Netflix</a>, <a href="https://uber.com">Uber</a> and <a href="http://www.jpl.nasa.gov/">NASA JPL</a> for many years now. It has been proven to scale to tens of thousands of nodes, running hundreds of thousands of containers serving live traffic without interruption for months at a time.</p> |
| |
| <p>Given its track record at these high profile companies, Apache Mesos could have reached its 1.0 milestone a long time ago. But one thing we really wanted to improve upon before doing a 1.0 release was to develop new HTTP APIs to ease the lives of both framework developers and cluster operators alike. These new APIs make it really easy to write a new framework or develop a new tool with off-the-shelf HTTP libraries written in the language of your choice. After iterating on the new APIs for nearly a year, we are confident that they are now ready for widespread use. Combined with a versioning scheme for the new APIs and a well-formulated <a href="http://mesos.apache.org/documentation/latest/versioning/">release and support process</a>, we are happy to call our latest release of Apache Mesos 1.0.</p> |
| |
| <p>In addition to the new APIs, the 1.0 release is jam-packed with features that makes running stateless and stateful workloads easy. Below, we will discuss some of the highlights in this release. For further details please refer to the <a href="https://github.com/apache/mesos/blob/1.0.0/CHANGELOG">CHANGELOG</a>.</p> |
| |
| <h3>HTTP API</h3> |
| |
| <p>Before 1.0, there were essentially two types of APIs exposed by Mesos &ndash; the driver-based Framework API used by schedulers and executors and the REST-based HTTP API used by operators and tools. While the driver-based API made writing frameworks easier by hiding the complexities of interfacing with Mesos itself (e.g., leader detection, reliable reconnection, message delivery, etc.) it had several drawbacks. For example, only a few languages had bindings for the driver (specifically, C++, Java and Python), limiting the languages that frameworks could be written in. Moreover, the driver required both the client (e.g., scheduler) and the server (e.g., master) to open connections to one another in order to communicate. This requirement for a bi-directional connection between clients and servers made it really hard for clients to run inside containers or behind firewalls.</p> |
| |
| <p>The new <a href="https://www.youtube.com/watch?v=mDn_iyFSv38&amp;index=13&amp;list=PLGeM09tlguZQVL7ZsfNMffX9h1rGNVqnC">HTTP API</a> aims to solve these problems by providing an RPC-based HTTP API for both frameworks (i.e. <a href="http://mesos.apache.org/documentation/latest/scheduler-http-api/">schedulers</a> and <a href="http://mesos.apache.org/documentation/latest/executor-http-api/">executors</a>) and <a href="http://mesos.apache.org/documentation/latest/operator-http-api/">operators</a>. Since the API client libraries can be written in any language that speaks HTTP, it immediately opens the door for frameworks to be written in new languages. More importantly, the HTTP API doesn’t require servers to open a connection back to the client to communicate with it. As such, robust strategies for handling network partitions can now be implemented easily within the Mesos codebase itself.</p> |
| |
| <p>Apart from simplifying the API for framework developers and operators, one of the most exciting new features in the new HTTP API is <strong>experimental</strong> support for <a href="http://mesos.apache.org/documentation/latest/operator-http-api/">event streams</a>. Event streams are a frequently requested &ndash; and long awaited feature &ndash; that have finally made their way into the Mesos codebase. Instead of continuously polling the heavy weight /state endpoint, clients (e.g, service discovery systems) can now get events streamed to them directly by the master.</p> |
| |
| <h3>Unified Containerizer</h3> |
| |
| <p>Before the unified containerizer support was available, Mesos depended on external daemons to run containers based on a specific image format; <code>docker</code> daemon to run docker images, <code>rkt</code> to run appc images and so on. This made the system architecture complex and added more failure points to the platform. With the <a href="https://www.youtube.com/watch?v=rHUngcGgzVM&amp;index=14&amp;list=PLGeM09tlguZQVL7ZsfNMffX9h1rGNVqnC">unified containerizer</a>, we can now use a single container runtime engine, the <code>MesosContainerizer</code> to run containers off the most popular image formats (Docker, Appc, and soon OCI) without dependency on any external daemons. This makes the platform extremely robust, simplifies the system architecture and gives a unified isolation model for containers, allowing developers to achieve higher feature velocity in improving Mesos.</p> |
| |
| <h3>Networking</h3> |
| |
| <p>With the addition of support for the Container Networking Interface (<a href="https://github.com/containernetworking/cni">CNI</a>) in 1.0, we have made significant strides towards a comprehensive networking story in Mesos. Now, each container gets its own network namespace, which provides network isolation and allows users to work with containers as if they were running on bare metal or VM. Without network isolation, users have to manage network resources such as TCP/UDP ports on the agent. Managing these resources complicates the design of applications significantly.</p> |
| |
| <p>One of the highlights of the new CNI support is the ability to now provide a single IP per container in Mesos. This is one of the most requested features that Mesos has ever had!! Since the CNI interface is widely supported by networking vendors, this gives Mesos tremendous flexibility in orchestrating containers on a wide variety of networking technologies (e.g, VxLAN, <a href="https://dcos.io/docs/1.8/administration/overlay-networks/">DC/OS overlay</a>, <a href="https://www.projectcalico.org/">Calico</a>, <a href="https://github.com/weaveworks/weave-cni">Weave</a>, <a href="https://github.com/containernetworking/cni/blob/master/Documentation/flannel.md">Flannel</a>).</p> |
| |
| <h3>Storage</h3> |
| |
| <p>Starting from Mesos 1.0, we added <strong>experimnental support</strong> for external storage to Mesos. Before this feature, while users could use persistent volumes for running stateful services, there were some limitations. First, the users were not able to easily use non-local storage volumes. Second, data migrations for local persistent volumes had to be manually handled by operators. The newly added <code>docker/volume</code> isolator addresses these limitations. Currently, the isolator interacts with the Docker volume plugins (e.g., <a href="https://github.com/emccode/rexray">REX-Ray</a>, <a href="https://github.com/ClusterHQ/flocker">Flocker</a>, <a href="https://github.com/rancher/convoy">Convoy</a>) using a tool called <code>dvdcli</code>. By speaking the Docker volume plugin API, Mesos containers can connect with external volumes from numerous storage providers (e.g., Amazon EBS, Ceph, EMC ScaleIO).</p> |
| |
| <h3>Security</h3> |
| |
| <p>Mesos 1.0 comes with significant improvements in authentication and authorization. While we have long supported framework authentication and SSL/TLS encryption for frameworks and REST endpoints, not all HTTP endpoints were authenticated or authorized. With 1.0, all the sensitive endpoints have support for authentication and authorization.</p> |
| |
| <p>More importantly, we have added foundations for multi-tenancy by adding <a href="https://www.youtube.com/watch?v=-yWHuxXwuAA&amp;index=20&amp;list=PLGeM09tlguZQVL7ZsfNMffX9h1rGNVqnC">fine-grained authorization</a> controls. For example, it is now possible to set up ACLs so that a user can only view information about her own tasks in the WebUI and/or HTTP endpoints. This is a must-have for enterprises that need to enforce strict policies around access to information. As part of this effort, the Authorizer interface has been completely overhauled to make it easy for module writers to plugin enterprise-specific security policies.</p> |
| |
| <h3>GPU Support</h3> |
| |
| <p>That’s right, you can now run your <a href="https://www.tensorflow.org/">TensorFlow</a> jobs <a href="https://www.youtube.com/watch?v=giJ4GXFoeuA&amp;list=PL903xBaKIoaWc0hnSVyAAGAJUPxq2MCd0">directly on Mesos</a>. The custom GPU isolator handles all of the details of allocating GPUs to your application and making sure they are isolated from other jobs running on the system. All you have to worry about is making sure your newest deep learning algorithm is ready for deployment!</p> |
| |
| <p>As a bonus, we mimic the functionality of <a href="https://github.com/NVIDIA/nvidia-docker">nvidia-docker</a> so you can take your existing GPU docker containers and run them on Mesos without modification. This means you can test your applications locally on docker and be assured that they will run as expected once you deploy them on Mesos.</p> |
| |
| <p>We are working closely with the <a href="http://spark.apache.org/">Spark</a>, <a href="https://mesosphere.github.io/marathon/">Marathon</a>, and <a href="http://aurora.apache.org/">Aurora</a> teams to make scheduling your GPU workloads as easy as possible. We’ll keep you posted as more things develop!</p> |
| |
| <h3>Windows Support</h3> |
| |
| <p>Mesos 1.0 comes with <strong>experimental</strong> support for running Mesos Agent on Windows. It is now possible to build Mesos Agent and all its dependencies on Windows using CMake and Microsoft Visual Studio compiler. We are actively working on a tighter integration of Mesos Agent with Windows Container API (scheduled for release later this year), as well as adding support for launching Docker containers. The recent <a href="https://www.youtube.com/watch?v=bbyK1EBxrek">Mesoscon talk</a> gives an overview of the current state of this work as well as presents the roadmap for Mesos Agent on Windows.</p> |
| |
| <h3>Community</h3> |
| |
| <p>We would like to take this opportunity to give a huge thank you to the incredible Mesos community, without which none of this would be possible. We are fortunate to have a dedicated and enthusiastic community that not only finds and reports bugs but contributes code. In fact, all the highlighted features described above were done in close collaboration with several independent members and organizations in the community (e.g, IBM, Microsoft, Nvidia). It is rewarding to see an ever growing list of organizations using Mesos in production at scale and <a href="http://mesos.apache.org/blog/dev-community-status/">contributing back to the community</a>. Some of these companies have not only built frameworks but entire platforms (e.g., <a href="https://azure.microsoft.com/en-us/documentation/videos/azurecon-2015-deep-dive-on-the-azure-container-service-with-mesos/">Azure Container Service</a>, <a href="https://dcos.io/">DC/OS</a>, <a href="http://rancher.com/mesos/">Rancher</a>) on top of Mesos, which is truly humbling.</p> |
| |
| <p>If you are new to Mesos and interested in learning more, please <a href="http://mesos.apache.org/community/">join us</a> on this incredible journey. We are nowhere close to done implementing all the things that we want to build in Mesos and we could always use more help.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/dev-community-status/</id> |
| <link href="/blog/dev-community-status/" /> |
| <title> |
| Mesos Developer Community Status Report |
| </title> |
| <updated>2016-07-21T00:00:00Z</updated> |
| <author> |
| <name>Michael Park</name> |
| </author> |
| <content type="html"> |
| <p>The Mesos project has a large and rapidly growing community of users and contributors. |
| In this post we would like to reflect on the current state |
| of the community as well as speak about some benefits and challenges that the |
| growth brings.</p> |
| |
| <p>One of such challenges is that the we have to make sure that everyone’s interests |
| are met. This isn’t always easy due to occasional conflicts of interest. For example, |
| developers are eager to see their patches vetted and committed to the codebase as |
| rapidly as possible, whereas production users of Mesos want to make sure that the stability of the software is never |
| compromised for the sake of rolling out new features. Both are essential components |
| of a healthy open source infrastructure project, and we want to strike a harmonizing |
| balance.</p> |
| |
| <p>Transparency is the key for being able to grow the community while also making |
| sure that participants understand and agree with the development direction. In |
| this post - much of which derives from a recent <a href="https://www.youtube.com/watch?list=PLGeM09tlguZQVL7ZsfNMffX9h1rGNVqnC&amp;v=SnPmU61fVjQ">MesosCon 2016 presentation</a> - |
| we are going to present some statistics that reflect the current state of the |
| community participation. The time frame for the following statistics ranges from |
| the 0.24 release (July 2015) until 1.0.0-rc2 (June/July 2016).</p> |
| |
| <p>We mined the data for this post from Mesos <a href="https://git1-us-west.apache.org/repos/asf?p=mesos.git;a=tree;f=docs;h=b8c6cfa978ea6986fa7e9181f209448f4984a3ab;hb=9c8bfa9b1bfe52fa6b44aaf883333311bdde5519">git log</a> and used the recently added |
| <a href="https://git1-us-west.apache.org/repos/asf?p=mesos.git;a=blob;f=docs/contributors.yaml;h=e17fed49ea358837eb33827dc3aceea9cd69c1b3;hb=9c8bfa9b1bfe52fa6b44aaf883333311bdde5519">contributors.yaml</a> file for mapping contributors to organizations.</p> |
| |
| <h3>Community Growth and Diversity</h3> |
| |
| <div id="number_of_contributors_and_committers_per_release"></div> |
| |
| |
| <p>The number of unique contributors has been increasing steadily over time. As of |
| this writing, the number of contributors for the most recent release is greater |
| than 100. This is a more than factor two improvement over the 0.24 release for |
| which there were about 50 unique contributors!</p> |
| |
| <p>Historically there have always been large organizations from which the significant |
| amount of contributions came from. In recent times, Mesosphere, IBM and Microsoft have |
| been leading in terms of number of contributions made to the codebase. However, |
| in terms of numbers of people, the individual contributors greatly outnumber those |
| from Mesosphere, IBM and Microsoft.</p> |
| |
| <p>This is a great milestone for all of our individual contributors out there! |
| We greatly appreciate your contribution to the project and we&rsquo;re looking forward |
| to seeing even more commits from individual contributors in the future.</p> |
| |
| <div id="commit_breakdown_by_organizations_and_releases"></div> |
| |
| |
| <p>In terms of numbers of commits from an organization, Mesosphere has the highest number after |
| contributing 62.8% of the commits. It is followed by &lsquo;Other&rsquo; (which is a default organization |
| for all the authors who do not have an affiliation entry in the <a href="https://git1-us-west.apache.org/repos/asf?p=mesos.git;a=blob;f=docs/contributors.yaml;h=e17fed49ea358837eb33827dc3aceea9cd69c1b3;hb=9c8bfa9b1bfe52fa6b44aaf883333311bdde5519">contributors.yaml</a>), IBM and Microsoft. We are actively working on involving more members from the community |
| and are looking forward to seeing an even greater community participation.</p> |
| |
| <p>It is important to note that 1.0 release has been in the making for a longer time |
| than previous releases, and that is why there is a significant spike in the number of |
| commits for 1.0-rc2. |
| Here is how the same graph looks like once we change the breakdown from releases to months.</p> |
| |
| <div id="commit_breakdown_by_organizations_and_months"></div> |
| |
| |
| <p>It presents a fuller picture where the upward trend is still there, but one can also notice |
| that the smooth growth trend has been there for a while.</p> |
| |
| <p>The last graph that we want to present shows the breakdown of commits per release |
| between contributors and the PMC members (aka Mesos Committers). As one can see |
| the number of commits authored by non-committers vastly outnumbers the ones originating |
| from committers. This shows that the active committers spend a lot of time shepherding |
| and landing patches from contributors.</p> |
| |
| <div id="commit_breakdown_by_contributors_and_committers"></div> |
| |
| |
| <p>Going forward we are going to introduce a page on our website where we will continuously |
| publish up-to-date statistics around the developer community. We are also going to double |
| down on initiatives to improve the contribution experience on the Mesos project. We |
| started by doing a spring cleaning on our GitHub and Reviewboard backlogs, as well as the Kanban |
| board in JIRA. This will make sure that shepherds do not get drowned in stale reviews, and that |
| everyone can see what the community is working on. We also have some ideas around improving the |
| developer tools, collecting and analyzing metrics around reviews, as well as some other initiatives |
| that should foster a greater participation. If you are interested in helping us improve the |
| community participation and drive some of these initiatives please join the &lsquo;Community&rsquo; working group.</p> |
| |
| <p>Stay tuned for more news on the dev list!</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-27-3-released/</id> |
| <link href="/blog/mesos-0-27-3-released/" /> |
| <title> |
| Apache Mesos 0.27.3 Released |
| </title> |
| <updated>2016-06-19T00:00:00Z</updated> |
| <author> |
| <name>Jie Yu</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos point release for 0.27, 0.27.3, is now available for |
| <a href="http://mesos.apache.org/downloads">download</a>. This release includes fixes and |
| improvements for the following:</p> |
| |
| <ul> |
| <li>[MESOS-4705] - Linux &lsquo;perf&rsquo; parsing logic may fail when OS distribution has perf backports.</li> |
| <li>[MESOS-4869] - /usr/libexec/mesos/mesos-health-check using/leaking a lot of memory.</li> |
| <li>[MESOS-5018] - FrameworkInfo Capability enum does not support upgrades.</li> |
| <li>[MESOS-5021] - Memory leak in subprocess when &lsquo;environment&rsquo; argument is provided.</li> |
| <li>[MESOS-5449] - Memory leak in SchedulerProcess.declineOffer.</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release |
| <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.3">CHANGELOG</a>.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.27.2 cluster to Mesos 0.27.3 are |
| straightforward. Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade |
| guide</a> for detailed |
| information on upgrading to Mesos 0.27.3.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. If you |
| run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and |
| IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 4 contributors who made 0.27.3 possible:</p> |
| |
| <p>Fan Du, Vinod Kone, Benjamin Mahler, Dario Rexin, Yongqiao Wang, Jie Yu</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-28-2-released/</id> |
| <link href="/blog/mesos-0-28-2-released/" /> |
| <title> |
| Apache Mesos 0.28.2 Released |
| </title> |
| <updated>2016-06-13T00:00:00Z</updated> |
| <author> |
| <name>Jie Yu</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.28.2, is now available for <a href="http://mesos.apache.org/downloads">download</a>. This release includes some important bug fixes and improvements on top of 0.28.1. It is highly recommended that users use this version if you are considering using Mesos 0.28. More specifically, this release includes the following fixes and improvements:</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4705">MESOS-4705</a> - Linux &lsquo;perf&rsquo; parsing logic may fail when OS distribution has perf backports.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5239">MESOS-5239</a> - Persistent volume DockerContainerizer support assumes proper mount propagation setup on the host.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5253">MESOS-5253</a> - Isolator cleanup should not be invoked if they are not prepared yet.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5282">MESOS-5282</a> - Destroy container while provisioning volume images may lead to a race.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5312">MESOS-5312</a> - Env <code>MESOS_SANDBOX</code> is not set properly for command tasks that changes rootfs.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4885">MESOS-4885</a> - Unzip should force overwrite.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5449">MESOS-5449</a> - Memory leak in SchedulerProcess.declineOffer.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5380">MESOS-5380</a> - Killing a queued task can cause the corresponding command executor to never terminate.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5307">MESOS-5307</a> - Sandbox mounts should not be in the host mount namespace.</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2">CHANGELOG</a></p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.28.1 cluster to Mesos 0.28.2 are straightforward. Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.28.2.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 10 contributors who made 0.28.2 possible:</p> |
| |
| <p>Fan Du, Tomasz Janiszewski, Vinod Kone, Shuai Lin, Ben Mahler, Dario Rexin, Silas Snider, Gilbert Song, Yongqiao Wang, Jie Yu</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-26-1-and-more-released/</id> |
| <link href="/blog/mesos-0-26-1-and-more-released/" /> |
| <title> |
| Apache Mesos 0.26.1 and More Released |
| </title> |
| <updated>2016-04-12T00:00:00Z</updated> |
| <author> |
| <name>Michael Park</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos 0.26.1, 0.25.1 and 0.24.2 are now available for <a href="/downloads">download</a>. |
| The applicable subset of the following issues were backported.</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-920">MESOS-920</a> - GLOG performance.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3046">MESOS-3046</a> - UUID performance.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3051">MESOS-3051</a> - Port Ranges performance.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3052">MESOS-3052</a> - Allocator filter performance.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3307">MESOS-3307</a> - Configurable task/framework history.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3560">MESOS-3560</a> - JSON-based credential files.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3602">MESOS-3602</a> - HDFS.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3738">MESOS-3738</a> - Mesos health check within docker container.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3773">MESOS-3773</a>, <a href="https://issues.apache.org/jira/browse/MESOS-4069">MESOS-4069</a> - SSL.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3834">MESOS-3834</a> - Agent upgrade compatibility</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4106">MESOS-4106</a> - Health checks.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4235">MESOS-4235</a> - <code>/state</code> endpoint performance.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4302">MESOS-4302</a> - Offer filter timeout fix for backlogged allocator.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4687">MESOS-4687</a> - Fixed point resources math.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4711">MESOS-4711</a> - Libevent.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4979">MESOS-4979</a> - Deletion of special files.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-5021">MESOS-5021</a> - Memory leak in subprocess.</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://github.com/apache/mesos/blob/master/CHANGELOG">CHANGELOG</a>.</p> |
| |
| <p>Upgrading to 0.26.1 can be done seamlessly on a 0.26.0 cluster. If upgrading from an earlier version, please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrades</a> documentation.</p> |
| |
| <h2>Contributors</h2> |
| |
| <p>Thanks to the 20 contributors who made 0.26.1, 0.25.1, and 0.24.2 possible:</p> |
| |
| <p>Alexander Rojas, Alexander Rukletsov, Anand Mazumdar, Benjamin Mahler, Felix Abecassis, Gilbert Song, haosdent huang, Isabel Jimenez, James Peach, Joerg Schad, Jojy Varghese, Joris Van Remoortere, Joseph Wu, Kapil Arya, Kevin Klues, Klaus Ma, Michael Park, Neil Conway, Till Toenshoff, Timothy Chen.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-28-0-released/</id> |
| <link href="/blog/mesos-0-28-0-released/" /> |
| <title> |
| Apache Mesos 0.28.0 Released |
| </title> |
| <updated>2016-03-17T00:00:00Z</updated> |
| <author> |
| <name>Vinod Kone</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.28.0, is now available for <a href="http://mesos.apache.org/downloads">download</a>.</p> |
| |
| <p>This release includes the following features and improvements:</p> |
| |
| <ul> |
| <li><p>[MESOS-4343] - A new cgroups isolator for enabling the net_cls subsystem in |
| Linux. The cgroups/net_cls isolator allows operators to provide network |
| performance isolation and network segmentation for containers within a Mesos |
| cluster. To enable the cgroups/net_cls isolator, append <code>cgroups/net_cls</code> to |
| the <code>--isolation</code> flag when starting the slave. Please refer to |
| docs/mesos-containerizer.md for more details.</p></li> |
| <li><p>[MESOS-4687] - The implementation of scalar resource values (e.g., &ldquo;2.5 |
| CPUs&rdquo;) has changed. Mesos now reliably supports resources with up to three |
| decimal digits of precision (e.g., &ldquo;2.501 CPUs&rdquo;); resources with more than |
| three decimal digits of precision will be rounded. Internally, resource math |
| is now done using a fixed-point format that supports three decimal digits of |
| precision, and then converted to/from floating point for input and output, |
| respectively. Frameworks that do their own resource math and manipulate |
| fractional resources may observe differences in roundoff error and numerical |
| precision.</p></li> |
| <li><p>[MESOS-4479] - Reserved resources can now optionally include &ldquo;labels&rdquo;. |
| Labels are a set of key-value pairs that can be used to associate metadata |
| with a reserved resource. For example, frameworks can use this feature to |
| distinguish between two reservations for the same role at the same agent |
| that are intended for different purposes.</p></li> |
| <li><p>[MESOS-2840] - <strong>Experimental</strong> support for container images in Mesos |
| containerizer (a.k.a. Unified Containerizer). This allows frameworks to |
| launch Docker/Appc containers using Mesos containerizer without relying on |
| docker daemon (engine) or rkt. The isolation of the containers is done using |
| isolators. Please refer to docs/container-image.md for currently supported |
| features and limitations.</p></li> |
| <li><p>[MESOS-4793] - <strong>Experimental</strong> support for v1 Executor HTTP API. This |
| allows executors to send HTTP requests to the /api/v1/executor agent |
| endpoint without the need for an executor driver. Please refer to |
| docs/executor-http-api.md for more details.</p></li> |
| <li><p>[MESOS-4370] Added support for service discovery of Docker containers that |
| use Docker Remote API v1.21.</p></li> |
| </ul> |
| |
| |
| <p>Additional API Changes:</p> |
| |
| <ul> |
| <li>[MESOS-4066] - Agent should not return partial state when a request is made to /state endpoint during recovery.</li> |
| <li>[MESOS-4547] - Introduce TASK_KILLING state.</li> |
| <li>[MESOS-4712] - Remove &lsquo;force&rsquo; field from the Subscribe Call in v1 Scheduler API.</li> |
| <li>[MESOS-4591] - Change the object of ReserveResources and CreateVolume ACLs to <code>roles</code>.</li> |
| <li>[MESOS-3583] - Add stream IDs for HTTP schedulers.</li> |
| <li>[MESOS-4427] - Ensure ip_address in state.json (from NetworkInfo) is valid</li> |
| </ul> |
| |
| |
| <p>Furthermore, several bugfixes and improvements made it into this release. |
| For full release notes with all features and bug fixes, please refer to the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.0">CHANGELOG</a>.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.27.0 cluster to Mesos 0.28.0 are straightforward. There are just some minor, backwards compatible deprecations. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.28.0.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. |
| If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 44 contributors who made 0.28.0 possible:</p> |
| |
| <p>Abhishek Dasgupta,Alex Clemmer,Alex Naparu,Alexander Rojas,Alexander Rukletsov,Anand Mazumdar,Avinash sridharan,Benjamin Bannier,Benjamin Mahler,Bernd Mathiske,Cong Wang,Daniel Pravat,David Forsythe,Diana Arroyo,Disha Singh,Gilbert Song,Greg Mann,Guangya Liu,Isabel Jimenez,James Peach,Jan Schlicht,Jie Yu,Joerg Schad,Jojy Varghese,Joris Van Remoortere,Joseph Wu,Kapil Arya,Kevin Devroede,Kevin Klues,Klaus Ma,M Lawindi,Michael Browning,Michael Lunøe,Michael Park,Neil Conway,Shuai Lin,Till Toenshoff,Timothy Chen,Vinod Kone,Yong Tang,Yongqiao Wang,Zhiwei Chen,haosdent huang,mlawindi</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-27-2-released/</id> |
| <link href="/blog/mesos-0-27-2-released/" /> |
| <title> |
| Apache Mesos 0.27.2 Released |
| </title> |
| <updated>2016-03-07T00:00:00Z</updated> |
| <author> |
| <name>Michael Park</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.27.2, is now available for <a href="http://mesos.apache.org/downloads">download</a>. |
| This release includes fixes and improvements for the following:</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4693">MESOS-4693</a> - Variable shadowing in HookManager::slavePreLaunchDockerHook.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4711">MESOS-4711</a> - Race condition in libevent poll implementation causes crash.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4754">MESOS-4754</a> - The &ldquo;executors&rdquo; field is exposed under a backwards incompatible schema.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4687">MESOS-4687</a> - Implement reliable floating point for scalar resources.</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.2">CHANGELOG</a>.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.27.1 cluster to Mesos 0.27.2 are straightforward. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.27.2.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. |
| If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 4 contributors who made 0.27.2 possible:</p> |
| |
| <p>Alexander Rojas, Kevin Devroede, Michael Park, Neil Conway</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-27-1-released/</id> |
| <link href="/blog/mesos-0-27-1-released/" /> |
| <title> |
| Apache Mesos 0.27.1 Released |
| </title> |
| <updated>2016-02-22T00:00:00Z</updated> |
| <author> |
| <name>Michael Park</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.27.1, is now available for <a href="http://mesos.apache.org/downloads">download</a>. |
| This release includes fixes and improvements for: reconnection logic for Zookeeper client, <code>/state</code> endpoint and <code>systemd</code> integration.</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4546">MESOS-4546</a> - Mesos Agents needs to re-resolve hosts in zk string on leader change / failure to connect.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-4582">MESOS-4582</a> - state.json serving duplicate &ldquo;active&rdquo; fields.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3007">MESOS-3007</a> - Support systemd with Mesos.</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.1">CHANGELOG</a>.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.27.0 cluster to Mesos 0.27.1 are straightforward. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.27.1.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. |
| If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 8 contributors who made 0.27.1 possible:</p> |
| |
| <p>Jie Yu, Joerg Shad, Joris Van Remoortere, Joseph Wu, Kapil Arya, Michael Park, Neil Conway, Shuai Lin</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesoscon-2016-cfp-is-now-open/</id> |
| <link href="/blog/mesoscon-2016-cfp-is-now-open/" /> |
| <title> |
| MesosCon 2016 CFP is now open! |
| </title> |
| <updated>2016-02-12T00:00:00Z</updated> |
| <author> |
| <name>Michael Park</name> |
| </author> |
| <content type="html"> |
| <p>MesosCon North America 2016 will be held in Denver, CO on June 1-2, 2016.</p> |
| |
| <p>Talk submissions, sponsorship opportunities, and early-bird registration are now open for the conference.</p> |
| |
| <h2>Speak at MesosCon</h2> |
| |
| <p>Several formats are being accepted for speaking proposals, including: |
| Presentations, Panels, Keynotes and Lightning Talks. |
| Submissions are being accepted through <strong>March 9, 2016</strong>.</p> |
| |
| <p>You can take a look at <a href="https://www.youtube.com/playlist?list=PLVjgeV_avap2arug3vIz8c6l72rvh9poV">MesosCon 2015 list of talks</a> |
| for ideas. If you&rsquo;re unsure about your proposal, or want some feedback or advice in general, |
| please don&rsquo;t hesitate to reach out to the <a href="https://mail-archives.apache.org/mod_mbox/mesos-dev">mesos-dev</a> mailing list. |
| We&rsquo;ll be happy to help out! Further details are available on the <a href="http://events.linuxfoundation.org/events/mesoscon/program/cfp">CFP website</a>.</p> |
| |
| <p>All submissions for MesosCon North America will also be considered for the upcoming MesosCon Europe and China events (details to be announced shortly).</p> |
| |
| <h2>Sponsor MesosCon</h2> |
| |
| <p>The <a href="http://events.linuxfoundation.org/events/mesoscon/sponsors">sponsorship prospectus for MesosCon</a> is now available, |
| including several opportunities with limited availability.</p> |
| |
| <h2>Attend MesosCon</h2> |
| |
| <p><a href="http://events.linuxfoundation.org/events/mesoscon/attend/register">Early-Bird registration</a> is open through April 22nd!</p> |
| |
| <p>We look forward to seeing you at MesosCon North America, as well as MesosCon Europe and MesosCon China taking place later this year!</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-27-0-released/</id> |
| <link href="/blog/mesos-0-27-0-released/" /> |
| <title> |
| Apache Mesos 0.27.0 Released |
| </title> |
| <updated>2016-02-02T00:00:00Z</updated> |
| <author> |
| <name>Kapil Arya</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.27.0, is now available for <a href="http://mesos.apache.org/downloads">download</a>. |
| This release includes the following features and improvements:</p> |
| |
| <ul> |
| <li><p><a href="https://issues.apache.org/jira/browse/MESOS-1791">[MESOS-1791]</a>: Support for <em>resource quota</em> that provides non-revocable resource guarantees without tying reservations to particular Mesos agents. Please refer to <a href="http://mesos.apache.org/documentation/latest/quota">the quota documentation</a> for more information.</p></li> |
| <li><p><a href="https://issues.apache.org/jira/browse/MESOS-191">[MESOS-191]</a>: <em>Multiple disk</em> support to allow for disk IO intensive applications to achieve reliable, high performance.</p></li> |
| <li><p><a href="https://issues.apache.org/jira/browse/MESOS-4085">[MESOS-4085]</a>: Flexible roles with the introduction of <em>implicit roles</em>. It deprecates the whitelist functionality that was implemented by specifying <code>--roles</code> during master startup to provide a static list of roles.</p></li> |
| <li><p><a href="https://issues.apache.org/jira/browse/MESOS-2353">[MESOS-2353]</a>: Performance improvement of the state endpoint for large clusters.</p></li> |
| </ul> |
| |
| |
| <p>Furthermore, 167+ bugfixes and improvements made it into this release. |
| For full release notes with all features and bug fixes, please refer to the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.0">CHANGELOG</a>.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.26.0 cluster to Mesos 0.27.0 are straightforward. There are just some minor, backwards compatible deprecations. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.27.0.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. |
| If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 55 contributors who made 0.27.0 possible:</p> |
| |
| <p>Adam B, Alexander Rojas, Alexander Rukletsov, Alex Clemmer, Anand Mazumdar, Andy Pang, Anindya Sinha, Artem Harutyunyan, Avinash sridharan, Bartek Plotka, Benjamin Bannier, Benjamin Hindman, Benjamin Mahler, Bernd Mathiske, Bhuvan Arumugam, BrickXu, Chi Zhang, Cong Wang, Dario Rexin, David Forsythe, Diana Arroyo, Diogo Gomes, Felix Abecassis, Gilbert Song, Greg Mann, Guangya Liu, haosdent huang, James Peach, Jan Schlicht, Jian Qiu, Jie Yu, Jihun Kang, Jiri Simsa, Jocelyn De La Rosa, Joerg Schad, Jojy Varghese, Joris Van Remoortere, Joseph Wu, Kapil Arya, Kevin Klues, Klaus Ma, Mandeep Chadha, Michael Park, Neil Conway, Olivier Sallou, Qian Zhang, Shuai Lin, Stephan Erb, Steve Hoffman, Till Toenshoff, Timothy Chen, Vaibhav Khanduja, Vinod Kone, Vivek Juneja, and Zhitao Li.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-26-0-released/</id> |
| <link href="/blog/mesos-0-26-0-released/" /> |
| <title> |
| Apache Mesos 0.26.0 Released |
| </title> |
| <updated>2015-12-16T00:00:00Z</updated> |
| <author> |
| <name>Till Toenshoff</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.26.0, is now available for <a href="http://mesos.apache.org/downloads">download</a>. |
| 103+ bugfixes and improvements made it into this release. |
| For full release notes with all features and bug fixes, please refer to the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.26.0">CHANGELOG</a>.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.25.0 cluster to Mesos 0.26.0 are straightforward. There are just some minor, backwards compatible deprecations. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.26.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. |
| If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 45 contributors who made 0.26.0 possible:</p> |
| |
| <p>Adam B, Alex Clemmer, Alexander Rojas, Alexander Rukletsov, Anand Mazumdar, Andrey Dyatlov, Artem Harutyunyan, Avinash sridharan, Benjamin Bannier, |
| Benjamin Hindman, Benjamin Mahler, Bernd Mathiske, Bhuvan Arumugam, Chengwei Yang, Chi Zhang, Connor Doyle, Dave Lester, Elsmore, Felix Abecassis, |
| Gastón Kleiman, Gilbert Song, Greg Mann, Guangya Liu, haosdent huang, Isabel Jimenez, James Peach, Jian Qiu, Jie Yu, Joerg Schad, Jojy Varghese, |
| Jonathon Rossi, Joris Van Remoortere, Joseph Wu, Kapil Arya, Klaus Ma, Marco Massenzio, Michael Park, Neil Conway, Rossi, Spike Curtis, |
| Till Toenshoff, Timothy Chen, Tomasz Janiszewski, Vinod Kone, Yong Qiao Wang</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-25-0-released/</id> |
| <link href="/blog/mesos-0-25-0-released/" /> |
| <title> |
| Apache Mesos 0.25.0 Released |
| </title> |
| <updated>2015-10-12T00:00:00Z</updated> |
| <author> |
| <name>Niklas Q. Nielsen</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.25.0, is now available for <a href="http://mesos.apache.org/downloads">download</a>. |
| This release includes the following features and improvements:</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1474">[MESOS-1474]</a> - Experimental support for maintenance primitives. Please refer to <a href="http://mesos.apache.org/documentation/latest/maintenance/">the maintenance documentation</a> for more information.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2600">[MESOS-2600]</a> - Added master endpoints /reserve and /unreserve for dynamic reservations. Please refer to <a href="http://mesos.apache.org/documentation/latest/reservation/">the reservation documentation</a> for more information.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2044">[MESOS-2044]</a> - Extended Module APIs to enable IP per container assignment, isolation and resolution. Please refer to <a href="http://mesos.apache.org/documentation/latest/networking-for-mesos-managed-containers/">the container networking documentation</a> for more information.</li> |
| </ul> |
| |
| |
| <p>Furthermore, 100+ bugs and improvements have made it into this release. |
| For full release notes with all features and bug fixes, please refer to the <a href="https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.25.0">CHANGELOG</a>.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.24.x cluster to Mesos 0.25 are straightforward, but there are a few caveats/deprecations. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.25.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. |
| If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 40 contributors who made 0.25.0 possible: |
| Adam B, Aditi Dixit, Alex Clemmer, Alexander Rukletsov, Anand Mazumdar, Artem Harutyunyan, Ben Mahler, Bernd Mathiske, Chi Zhang, Cong Wang, Eijsermans, Eren Güve, Felix Abecassis, Greg Mann, Guangya Liu, Isabel Jimenez, James Peach, Jan Schlicht, Jiang Yan Xu, Jie Yu, Joerg Schad, Jojy Varghese, Joris Van Remoortere, Joseph Wu, Kapil Arya, Klaus Ma, Lily Chen, M Bauer, Marco Massenzio, Michael Park, Neil Conway, Niklas Nielsen, Paul Brett, Qian Zhang, Timothy Chen, Vaibhav Khanduja, Vinod Kone, Wojciech Sielski, Yong Qiao Wang and Haosdent Huang</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/announcing-mesoscon-eu-2015-hackathon/</id> |
| <link href="/blog/announcing-mesoscon-eu-2015-hackathon/" /> |
| <title> |
| Announcing the #MesosCon Europe Hackathon |
| </title> |
| <updated>2015-09-30T00:00:00Z</updated> |
| <author> |
| <name>Casey Bisson</name> |
| </author> |
| <content type="html"> |
| <p>We are proud to announce the first ever <a href="http://events.linuxfoundation.org/events/mesoscon-europe">MesosCon Europe</a> hackathon on Friday, October 9th, 2015. This event is an opportunity to contribute to the project, learn from other members of the community, and build some fantastic hacks.</p> |
| |
| <p>The hackathon is being sponsored by <a href="https://www.joyent.com/">Joyent</a>, and, though not required, participants are invited to use Joyent&rsquo;s cloud during the hack day. Joyent is offering each participant substantial service credits in their cloud to kickstart work and continue hacking after the event.</p> |
| |
| <h3>Award categories</h3> |
| |
| <p>We are challenging participants to hack on Mesos in two categories:</p> |
| |
| <ul> |
| <li><em>Community need</em>: These are issues logged in the Mesos issue tracker that have received a large amount of activity (comments, votes, etc), and address some of the larger problems or pain points for the community. Suggested projects include new features, bugs, or documentation.</li> |
| <li><em>People’s choice</em>: These contributions will be voted on by your peers, and our guidance is intentionally open-ended so teams will run wild with their ideas. We’re excited to see what you come up with.</li> |
| </ul> |
| |
| |
| <p>Additionally, Joyent is offering a <em>container-native bonus</em> award to one hack in each of the above categories that best leverages Joyent&rsquo;s Triton bare metal container infrastructure. Joyent&rsquo;s judges may award the container-native bonus at their discretion.</p> |
| |
| <h3>Rules</h3> |
| |
| <ul> |
| <li>Coding may not begin until the hackathon officially begins, although we encourage you to plan and scheme ahead of time!</li> |
| <li>Sourcecode from the hackathon must be fully available on Github, Bitbucket, or a public source repo in order to be successfully submitted. Code must additionally be licensed in a manner compatible with Mesos' licensing.</li> |
| <li>Submitted applications must run.</li> |
| <li>Teams may have a maximum of four contributors.</li> |
| <li>A team may only win one category.</li> |
| <li>Submissions must be related to Mesos in some way.</li> |
| </ul> |
| |
| |
| <p>These rules are subject to change. Please hack the code, not the rules: if you think you&rsquo;re doing something that&rsquo;s against the rules or that gives you an unfair advantage, you probably shouldn&rsquo;t do it.</p> |
| |
| <h3>Schedule</h3> |
| |
| <p>9:00 - Hacking begins at conference center</p> |
| |
| <p>13:00 - Lunch arrives</p> |
| |
| <p>17:00 - Coding stops, refreshments are served</p> |
| |
| <p>17:15 - Re-explain the voting rules</p> |
| |
| <p>17:20 - Presentations start - Each team gets 5 minutes to pitch what they built and show it off</p> |
| |
| <p>18:00 - Voting occurs</p> |
| |
| <p>18:15 - Winners announced</p> |
| |
| <h3>Registration</h3> |
| |
| <p>The hackathon is open to all <a href="http://events.linuxfoundation.org/events/mesoscon-europe">MesosCon Europe 2015</a> attendees. Please indicate your interest in the hackathon while registering for the conference or update your registration to reflect it.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-24-1-and-more-released/</id> |
| <link href="/blog/mesos-0-24-1-and-more-released/" /> |
| <title> |
| Apache Mesos 0.24.1 and More Released |
| </title> |
| <updated>2015-09-24T00:00:00Z</updated> |
| <author> |
| <name>Adam B</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos 0.24.1 is now available for <a href="/downloads">download</a>. 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 <a href="/downloads">downloads</a> page.</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2986">MESOS-2986</a> - Docker version output is not compatible with Mesos</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-3136">MESOS-3136</a> - COMMAND health checks with Marathon 0.10.0 are broken</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://github.com/apache/mesos/blob/master/CHANGELOG">CHANGELOG</a>.</p> |
| |
| <p>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 <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrades</a> documentation.</p> |
| |
| <h2>Contributors</h2> |
| |
| <p>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.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-24-0-released/</id> |
| <link href="/blog/mesos-0-24-0-released/" /> |
| <title> |
| Apache Mesos 0.24.0 Released |
| </title> |
| <updated>2015-09-21T00:00:00Z</updated> |
| <author> |
| <name>Vinod Kone</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.24.0, is now available for <a href="http://mesos.apache.org/downloads">download</a>. This release includes the following features and improvements:</p> |
| |
| <h4>Scheduler HTTP API (<a href="https://issues.apache.org/jira/browse/MESOS-2288">MESOS-2288</a>)</h4> |
| |
| <p>Mesos 0.24 provides <strong>experimental</strong> support for scheduler HTTP API. Framework schedulers can communicate with Mesos by sending HTTP POST requests to <code>/api/v1/scheduler</code> instead of depending on the native libmesos library. The endpoint accepts both JSON and Protobuf requests. Additionally, the master talks back to the scheduler using the same connection opened by the scheduler, mitigating communication issues in firewalled/NATed environments. Refer to the <a href="http://mesos.apache.org/documentation/latest/scheduler_http_api/">scheduler http api documentation</a> for more information.</p> |
| |
| <p>Note that, this release only adds the support for scheduler HTTP API. Support for HTTP executor API is currently in the works and will be released soon!</p> |
| |
| <h3>API Versioning (<a href="https://issues.apache.org/jira/browse/MESOS-3167">MESOS-3167</a>)</h3> |
| |
| <p>As part of this release, we have also outlined the versioning scheme for Mesos HTTP API going forward. At a high level, the Mesos API (constituting Scheduler, Executor, Internal, Operator/Admin APIs) will have a version in the URL. The versioned URL will have a prefix of <code>/api/vN</code> where <code>N</code> is the version of the API. For simplicity, the stable version of the API will correspond to the major release version of Mesos. For example, v1 of the API will be supported by Mesos release versions 1.0.0, 1.4.0, 1.20.0 etc. Refer to the <a href="https://docs.google.com/document/d/1-iQjo6778H_fU_1Zi_Yk6szg8qj-wqYgVgnx7u3h6OU/edit#">versioning design document</a> for more information.</p> |
| |
| <h3>Changelog</h3> |
| |
| <p>Hundreds of other bug fixes/improvements are included in Mesos 0.24.0. |
| 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> for a full list of resolved JIRA issues.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.23.x cluster to Mesos 0.24 are straightforward, but there are a few caveats/deprecations. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.24.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 37 contributors who made 0.24.0 possible:</p> |
| |
| <p>Adam B, Aditi Dixit, Alex Clemmer, Alexander Rojas, Alexander Rukletsov, Anand Mazumdar, Anindya Sinha, Artem Harutyunyan, Bartek Plotka, Benjamin Hindman, Benjamin Mahler, Bernd Mathiske, Chi Zhang, Chris Heller, Dave Lester, Greg Mann, Guangya Liu, Ian Downes, Isabel Jimenez, James DeFelice, James Peach, Jan Schlicht, Jiang Yan Xu, Jie Yu, Joerg Schad, Jojy Varghese, Joris Van Remoortere, Joseph Wu, Kapil Arya, Klaus Ma, Lily Chen, Marco Massenzio, Mark Wang, Michael Park, Michael Schenck, Niklas Nielsen, Paul Brett, Ryuichi Okumura, Shuai Lin, Till Toenshoff, Tim Anderegg, Timothy Chen, Vinod Kone, Yong Qiao Wang, ayouwei, haosdent huang, usultrared.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesoscon-europe-2015-schedule-announced/</id> |
| <link href="/blog/mesoscon-europe-2015-schedule-announced/" /> |
| <title> |
| MesosCon Europe Schedule and Diversity Scholarship Available |
| </title> |
| <updated>2015-09-17T00:00:00Z</updated> |
| <author> |
| <name>Michael Hausenblas</name> |
| </author> |
| <content type="html"> |
| <p><a href="http://events.linuxfoundation.org/events/mesoscon-europe">MesosCon Europe 2015</a> will take place in Dublin, Ireland in three weeks, and we’re excited to announce the event schedule and availability of a diversity scholarship program.</p> |
| |
| <h2>Schedule</h2> |
| |
| <p>The program committee was overwhelmed by the number of submissions to the first European edition of MesosCon — 65 talks and tutorials have been submitted, you all rock — <a href="http://markmail.org/message/qf5dbzmugoh4gswf">we turned to you</a>, the community to help us select the most interesting and relevant talks. Given we had hard constraints concerning time and space we ended up selecting 14 talks and four lightning talks based on your overall ranking.</p> |
| |
| <p>The talks range from introductory presentations that aim helping the onboarding of new Mesos community members to deep dives: in the afternoon we will split into two tracks to be able to accommodate more topics. Sessions will take place on Thursday, October 8th 2015. Check out the <a href="http://events.linuxfoundation.org/events/mesoscon-europe/program/schedule">schedule</a> yourself!</p> |
| |
| <p>We&rsquo;ll also be holding a Mesos hackathon on Friday October 9th, and look forward to seeing what members of the community build and dream up.</p> |
| |
| <h2>Diversity Scholarship Program</h2> |
| |
| <p>As important as the schedule might be, if you can’t be there in person, what gives? So, we&rsquo;re repeating the successful offering of a <a href="http://events.linuxfoundation.org/events/mesoscon-europe/attend/scholarship">scholarship program</a>: it provides support to women, people of color, and people with disabilities who may not otherwise have the opportunity to attend MesosCon for financial reasons. <a href="https://docs.google.com/a/twitter.com/forms/d/1YavIUe3-xjjmqxqpE_QYbBkDz3z72iada568NyPxRRg/viewform">Apply</a> today and hope to see you in Dublin.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesoscon-goes-europe/</id> |
| <link href="/blog/mesoscon-goes-europe/" /> |
| <title> |
| MesosCon goes Europe |
| </title> |
| <updated>2015-08-05T00:00:00Z</updated> |
| <author> |
| <name>Michael Hausenblas</name> |
| </author> |
| <content type="html"> |
| <p>The Mesos <a href="http://mesos.apache.org/community/">community</a> has been growing steadily over the past years and on behalf of the #MesosCon Program Committee I’m excited and proud to be able to share the great news with you: MesosCon is now a world-wide event and this fall it comes to Europe. Organized by the Apache Mesos community, <a href="http://events.linuxfoundation.org/events/mesoscon-europe">#MesosCon Europe</a> brings together users and developers to share and learn about the project and its growing ecosystem.</p> |
| |
| <p>MesosCon Europe 2015 will take place in Dublin, Ireland and feature a full day of sessions to learn more about the Mesos core, an ecosystem developed around the project, and related technologies. The program will include workshops to get started with Mesos, keynote speakers from industry leaders, and sessions led by adopters and contributors. Day two will feature a hackathon held at the conference.</p> |
| |
| <p>Now is a good time to start preparing yourself for #MesosCon Europe: no matter if you want to contribute through a talk submission (see the <a href="http://events.linuxfoundation.org/events/mesoscon-europe/program/cfp">CfP</a> for details) or want to support us through a sponsorship. Stay tuned via <a href="http://twitter.com/mesoscon">@MesosCon</a> and mark these dates in your calendar:</p> |
| |
| <ul> |
| <li>Early bird registration closes: 24 August 2015</li> |
| <li>CfP deadline: 25 August 2015</li> |
| <li>Schedule announced: 15 September 2015</li> |
| <li>Conference dates: 8 and 9 October 2015</li> |
| </ul> |
| |
| |
| <p>More info: <a href="http://events.linuxfoundation.org/events/mesoscon-europe">http://events.linuxfoundation.org/events/mesoscon-europe</a></p> |
| |
| <p>Help us make this first European #MesosCon event a big success by spreading the word and <a href="http://events.linuxfoundation.org/events/mesoscon-europe/attend/register">register today</a>!</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-23-0-released/</id> |
| <link href="/blog/mesos-0-23-0-released/" /> |
| <title> |
| Apache Mesos 0.23.0 Released |
| </title> |
| <updated>2015-07-29T00:00:00Z</updated> |
| <author> |
| <name>Adam B</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.23.0, is now available for <a href="http://mesos.apache.org/downloads">download</a>. This release includes the following features and improvements:</p> |
| |
| <h4>Per-container network isolation (<a href="https://issues.apache.org/jira/browse/MESOS-1585">MESOS-1585</a>)</h4> |
| |
| <p>Mesos 0.23 provides support for per-container network monitoring and isolation. Network isolation prevents a single container from exhausting the available network ports, consuming an unfair share of the network bandwidth or significantly delaying packet transmission for others. Network statistics for each active container are published through the /monitor/statistics.json endpoint on the slave. Network isolation is transparent for the majority of tasks running on a slave (those that bind to port 0 and let the kernel allocate their port). This feature is only available on Linux and requires a configure-time flag. |
| Refer to the <a href="http://mesos.apache.org/documentation/latest/network-monitoring/">network monitoring and isolation documentation</a> for more information.</p> |
| |
| <h4>SSL (<a href="https://issues.apache.org/jira/browse/MESOS-910">MESOS-910</a>)</h4> |
| |
| <p>Experimental support for SSL encryption of any libprocess communication via libevent. Encrypting traffic between the Mesos master and its slaves and frameworks is important for information security, as it prevents eavesdropping and impersonation. This feature requires a configure-time flag and will have some performance impact. |
| Refer to the <a href="http://mesos.apache.org/documentation/latest/mesos-ssl/">Mesos SSL documentation</a> for instructions on building and enabling SSL.</p> |
| |
| <h4>Oversubscription (<a href="https://issues.apache.org/jira/browse/MESOS-354">MESOS-354</a>)</h4> |
| |
| <p>Experimental support for launching tasks/executors on revocable resources. These resources can be revoked by Mesos at any time, causing the tasks using them to be throttled or preempted.</p> |
| |
| <p>High-priority user-facing services are typically provisioned on large clusters for peak load and unexpected load spikes. Hence, for most of time, the provisioned resources remain underutilized. Oversubscription takes advantage of temporarily unused resources to execute best-effort tasks such as background analytics, video/image processing, chip simulations, and other low priority jobs.</p> |
| |
| <p>Oversubscription adds two new slave components: a Resource Estimator and a Quality of Service (QoS) Controller, alongside extending the existing resource allocator, resource monitor, and mesos slave. |
| Refer to the <a href="http://mesos.apache.org/documentation/latest/oversubscription/">oversubscription documentation</a> for more information.</p> |
| |
| <h4>Persistent volumes (<a href="https://issues.apache.org/jira/browse/MESOS-1554">MESOS-1554</a>)</h4> |
| |
| <p>Experimental support for frameworks creating Persistent Volumes from disk resources. This enables stateful services such as HDFS and Cassandra to store their data within Mesos rather than having to resort to network-mounted EBS volumes or unmanaged disk resources that need to be placed in a well-known location. |
| Refer to the <a href="http://mesos.apache.org/documentation/latest/persistent-volume/">persistent volume documentation</a> for more information.</p> |
| |
| <h4>Dynamic reservations (<a href="https://issues.apache.org/jira/browse/MESOS-2018">MESOS-2018</a>)</h4> |
| |
| <p>Experimental support for frameworks dynamically reserving resources on specific slaves for their role. Rather than requiring an operator to specify a fixed, precalculated set of &ldquo;static&rdquo; reservations on slave startup, a framework can now reserve resources as they are being offered, without requiring a slave restart. |
| No breaking changes were introduced with dynamic reservation, which means the existing static reservation mechanism continues to be fully supported. |
| Refer to the <a href="http://mesos.apache.org/documentation/latest/reservation/">reservation documentation</a> for more information.</p> |
| |
| <h4>Fetcher caching (<a href="https://issues.apache.org/jira/browse/MESOS-336">MESOS-336</a>)</h4> |
| |
| <p>Experimental support for fetcher caching of executor/task binaries. The fetcher can be instructed to cache URI downloads in a dedicated directory for reuse by subsequent downloads. If the URI’s “cache” field has the value “true”, then the fetcher cache is in effect. If a URI is encountered for the first time (for a particular user), it is first downloaded into the cache, then copied to the sandbox directory from there. If the same URI is encountered again (for the same user), and a corresponding cache file is resident in the cache or still en route into the cache, then downloading is omitted and the fetcher proceeds directly to copying from the cache. |
| Refer to the <a href="http://mesos.apache.org/documentation/latest/fetcher/">fetcher documentation</a> for more information.</p> |
| |
| <h4>NOTE: Experimental status</h4> |
| |
| <p>SSL, Oversubscription, Persistent Volumes, Dynamic Reservations, and Fetcher Caching are all released as &ldquo;experimental&rdquo; features, meaning that they are feature complete, at least for some use case, but have not yet been tested in production environments. We welcome your feedback.</p> |
| |
| <h3>Changelog</h3> |
| |
| <p>Hundreds of other bug fixes/improvements are included in Mesos 0.23.0. |
| 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> for a full list of resolved JIRA issues.</p> |
| |
| <h3>Upgrades</h3> |
| |
| <p>Rolling upgrades from a Mesos 0.22.x cluster to Mesos 0.23 are straightforward, but there are a few caveats/deprecations. |
| Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to Mesos 0.23.</p> |
| |
| <h3>Compiler version requirement</h3> |
| |
| <p>Please note that Mesos 0.23.0 now requires gcc 4.8+ or clang 3.5+, so that we can take advantage of C++11 language features.</p> |
| |
| <h3>Try it out</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks!</h3> |
| |
| <p>Thanks to the 52 contributors who made 0.23.0 possible: |
| Aaron Bell, Adam B, Aditi Dixit, Akanksha Agrawal, Alexander Rojas, Alexander Rukletsov, Anand Mazumdar, Artem Harutyunyan, Bartek Plotka, Benjamin Hindman, Benjamin Mahler, Bernd Mathiske, Brendan Chang, Brian Wickman, Chi Zhang, Christos Kozyrakis, Cody Maloney, Cong Wang, Connor Doyle, Dave Lester, Dominic Hamon, Evelina Dumitrescu, Gajewski, Greg Mann, haosdent huang, Ian Babrou, Ian Downes, Isabel Jimenez, Itamar Ostricher, James Peach, Jan Schlicht, Jay Buffington, Jiang Yan Xu, Jie Yu, Joerg Schad, Jojy Varghese, Joris Van Remoortere, Kapil Arya, Marco Massenzio, Mark Wang, Michael Park, Nancy Ko, Niklas Q. Nielsen, Oliver Nicholas, Paul Brett, Ricardo Cervera-Navarro, Stan Teresen, Till Toenshoff, Timothy Chen, Vinod Kone, weitao zhou, and Zhiwei Chen</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/register-for-mesoscon-seattle-save/</id> |
| <link href="/blog/register-for-mesoscon-seattle-save/" /> |
| <title> |
| Register for MesosCon by 7/31 and Save $100 |
| </title> |
| <updated>2015-07-28T00:00:00Z</updated> |
| <author> |
| <name>Steven Borrelli</name> |
| </author> |
| <content type="html"> |
| <p><a href="http://www.mesoscon.org">MesosCon</a> is less than a month away, and the standard registration fee of $399 expires July 31, 2015. <a href="http://events.linuxfoundation.org/events/mesoscon/attend/register">Register today</a>. Beginning August 1, 2015 the registration fee will be $499. Students are eligible for a special registration fee of US$99 (Note that a valid student id will be required at onsite check-in).</p> |
| |
| <p>MesosCon is an annual conference organized by the Apache Mesos community, bringing together users and developers to share and learn about the project and its growing ecosystem.</p> |
| |
| <h2>This Year&rsquo;s Conference</h2> |
| |
| <p>This year MesosCon will take place August 20 - 21, 2015 at Sheraton Seattle in Seattle, WA, and features four tracks of talks for developers, operations and users. <a href="http://events.linuxfoundation.org/events/mesoscon/program/schedule">MesosCon Schedule</a></p> |
| |
| <p>MesosCon’s Keynote speakers feature Adrian Crockroft (Battery Ventures), Benjamin Hindman (Mesosphere), Neha Narula (MIT), and Peter Bailis (Berkeley).</p> |
| |
| <p>The Mesos community will once again hold a <a href="https://www.eventbrite.com/e/mesoscon-2015-pre-conference-hackathon-tickets-17752101012">day-long hackathon</a>, this year on Wednesday, August 19th and sponsored by SignalFx.</p> |
| |
| <p>On behalf of the #MesosCon Program Committee, we couldn’t be more excited about this year’s conference and what this means for the open source project’s community. We hope that you’ll join us!</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesoscon-seattle-preconference-and-social-activities/</id> |
| <link href="/blog/mesoscon-seattle-preconference-and-social-activities/" /> |
| <title> |
| Announcing MesosCon pre-conference and social activities |
| </title> |
| <updated>2015-07-13T00:00:00Z</updated> |
| <author> |
| <name>Dave Lester</name> |
| </author> |
| <content type="html"> |
| <p>The countdown until <a href="http://www.mesoscon.org">#MesosCon</a> 2015 in Seattle continues: only 38 days until the event! <a href="http://events.linuxfoundation.org/events/mesoscon/attend/register">Register today</a>!</p> |
| |
| <p>We&rsquo;re pleased to announce several pre-conference and social activities that we hope will make this year’s conference even more enjoyable.</p> |
| |
| <h2>MesosCon Hackathon, Wednesday August 19th</h2> |
| |
| <p>Join us for a <a href="https://www.eventbrite.com/e/mesoscon-2015-pre-conference-hackathon-tickets-17752101012">pre-conference hackathon on Wednesday, August 19th</a>; space is limited so be sure to register today! The hackathon is sponsored by <a href="https://signalfx.com">SignalFx</a>, and hosted by <a href="http://www.moz.com">Moz</a> at their office in downtown Seattle a short distance from the Sheraton Seattle conference hotel. The hackathon will take place from 8:30-5:00pm.</p> |
| |
| <p>What should you work on? It&rsquo;s really up to you, as long as it&rsquo;s Mesos-related. Here are a few broad categories of projects to consider.</p> |
| |
| <ul> |
| <li>Frameworks (build your own Mesos framework or add features to an existing framework)</li> |
| <li>Mesos Core (squashing bugs, adding new features, or even proposing a design document)</li> |
| <li>Ops (tools to make it easier to operate a Mesos cluster; examples may include monitoring, logging, etc)</li> |
| </ul> |
| |
| |
| <p>Additional details about the hackathon are available on the <a href="https://www.eventbrite.com/e/mesoscon-2015-pre-conference-hackathon-tickets-17752101012">Eventbrite registration page</a>.</p> |
| |
| <h2>Attendee Offsite Reception, Thursday Evening, August 20th</h2> |
| |
| <p>Open to all #MesosCon attendees, join us at the <a href="http://www.empmuseum.org/">Experience Music Project</a> (EMP), a leading-edge nonprofit museum, dedicated to the ideas and risk-taking that fuel contemporary popular culture. Appetizers and drinks included as well as the opportunity to check out some of the current exhibits. Shuttles will be provided from the Sheraton to the EMP starting at 7:30pm and returning later in the evening.</p> |
| |
| <h2>Mesos Evening Event, Wednesday, August 19th</h2> |
| |
| <p>Twitter plans to host a Mesos event the night before the conference at their Seattle office. More details will be announced in the coming week, so stay tuned!</p> |
| |
| <h2>About MesosCon</h2> |
| |
| <p>MesosCon will take place August 20 - 21, 2015 at Sheraton Seattle in Seattle, WA with a hackathon taking place the day prior to the event. The standard attendee registration fee will be US$399 (Through July 31, 2015), and late registration US$499 beginning August 1, 2015. Students are eligible for a special registration fee of US$99 (Note that a valid student id will be required at onsite check-in).</p> |
| |
| <p>Hope to see you at this year’s MesosCon!</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesoscon-seattle-keynote-speakers-announced/</id> |
| <link href="/blog/mesoscon-seattle-keynote-speakers-announced/" /> |
| <title> |
| MesosCon Seattle 2015 Keynote Speakers Announced |
| </title> |
| <updated>2015-07-01T00:00:00Z</updated> |
| <author> |
| <name>Dave Lester</name> |
| </author> |
| <content type="html"> |
| <p>The countdown until <a href="http://events.linuxfoundation.org/events/mesoscon">#MesosCon</a> has begun:</p> |
| |
| <blockquote class="twitter-tweet" lang="en"><p lang="en" dir="ltr">Only 7 weeks until <a href="https://twitter.com/hashtag/MesosCon?src=hash">#MesosCon</a>! Register today and join us in Seattle <a href="http://t.co/bVJ9dL5CEO">http://t.co/bVJ9dL5CEO</a></p>&mdash; #MesosCon (@mesoscon) <a href="https://twitter.com/mesoscon/status/616320613922275332">July 1, 2015</a></blockquote> |
| |
| |
| <script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script> |
| |
| |
| <p>MesosCon is an annual conference organized by the Apache Mesos community, bringing together users and developers to share and learn about the project and its growing ecosystem. <a href="http://events.linuxfoundation.org/events/mesoscon/attend/register">Register now</a> and join us in Seattle this August!</p> |
| |
| <p>Here’s a rundown of several conference announcements:</p> |
| |
| <h2>Keynote Speakers</h2> |
| |
| <p>We’ve curated a stellar line-up of invited keynote speakers, including:</p> |
| |
| <ul> |
| <li>Adrian Crockroft (Battery Ventures)</li> |
| <li>Benjamin Hindman (Mesosphere)</li> |
| <li>Neha Narula (MIT)</li> |
| <li>Peter Bailis (Berkeley)</li> |
| </ul> |
| |
| |
| <p>You don’t want to miss these! We’ll also feature platinum sponsored keynotes from Cisco, Intel, and Mesosphere.</p> |
| |
| <h2>Mesos Hackathon</h2> |
| |
| <p>The Mesos community will once again hold a day-long hackathon, this year on Wednesday, August 19th and sponsored by SignalFx. More details will be announced soon including the location and registration; stay tuned and hold the date!</p> |
| |
| <h2>Lightning Talks</h2> |
| |
| <p>Want to present at MesosCon, but missed the call for full sessions? We’ve opened a <a href="http://events.linuxfoundation.org/events/mesoscon/program/lighting-talks">CFP for lightning talks</a>; the application deadline is July 15th.</p> |
| |
| <h2>Diversity Scholarship Program</h2> |
| |
| <p>The <a href="http://events.linuxfoundation.org/events/mesoscon/attend/scholarship">MesosCon scholarship program</a> provides support to women, people of color, and people with disabilities who may not otherwise have the opportunity to attend MesosCon for financial reasons. Equal access and diversity are important to MesosCon, and we aim to remove this obstacle for underrepresented attendee groups. We want you at MesosCon, and we want to help you get there! |
| Applications are beginning to be reviewed, and will be reviewed on a rolling basis. Apply today! We also encourage MesosCon attendees to donate toward the diversity scholarship program directly during the time of registration using the online system.</p> |
| |
| <h2>Stay In Touch</h2> |
| |
| <p>As we make future announcements about the conference, stay in the loop and help us get the word out! We’ll be tweeting from @ApacheMesos and @MesosCon, blogging on the <a href="http://mesos.apache.org/blog/">Apache Mesos blog</a>, and sharing updates on the project’s user@ mailing lists.</p> |
| |
| <h2>About MesosCon</h2> |
| |
| <p>MesosCon will take place August 20 - 21, 2015 at Sheraton Seattle in Seattle, WA with a hackathon taking place the day prior to the event. The standard attendee registration fee will be US$399 (Through July 31, 2015), and late registration US$499 beginning August 1, 2015. Students are eligible for a special registration fee of US$99 (Note that a valid student id will be required at onsite check-in).</p> |
| |
| <p>Hope to see you at this year’s MesosCon!</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-22-1-released/</id> |
| <link href="/blog/mesos-0-22-1-released/" /> |
| <title> |
| Apache Mesos 0.22.1 Released |
| </title> |
| <updated>2015-05-12T00:00:00Z</updated> |
| <author> |
| <name>Adam B</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.22.1 is now available for <a href="http://mesos.apache.org/downloads">download</a>. This release includes fixes to containerizer recovery, sandbox permissions, and the Java and Python bindings. Also, certain fields of FrameworkInfo are now updated on reregistration.</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1795">MESOS-1795</a> - Assertion failure in state abstraction crashes JVM.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2161">MESOS-2161</a> - AbstractState JNI check fails for Marathon framework.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2461">MESOS-2461</a> - Slave should provide details on processes running in its cgroups</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2583">MESOS-2583</a> - Tasks getting stuck in staging.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2592">MESOS-2592</a> - The sandbox directory is not chown'ed if the fetcher doesn&rsquo;t run.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2601">MESOS-2601</a> - Tasks are not removed after recovery from slave and mesos containerizer</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2614">MESOS-2614</a> - Update name, hostname, failover_timeout, and webui_url in master on framework re-registration</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2643">MESOS-2643</a> - Python scheduler driver disables implicit acknowledgments by default.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2668">MESOS-2668</a> - Slave fails to recover when there are still processes left in its cgroup</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://github.com/apache/mesos/blob/master/CHANGELOG">CHANGELOG</a>.</p> |
| |
| <p>Upgrading to 0.22.1 can be done seamlessly on a 0.22.0 cluster. If upgrading from an earlier version, please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrades</a> documentation.</p> |
| |
| <h2>Contributors</h2> |
| |
| <p>Thanks to all the contributors for 0.22.1: Benjamin Hindman, Benjamin Mahler, Ian Downes, Jie Yu, Joris Van Remoortere, Niklas Nielsen, and Timothy Chen.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-22-0-released/</id> |
| <link href="/blog/mesos-0-22-0-released/" /> |
| <title> |
| Apache Mesos 0.22.0 Released |
| </title> |
| <updated>2015-03-25T00:00:00Z</updated> |
| <author> |
| <name>Niklas Q. Nielsen</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.22.0, is now available for <a href="http://mesos.apache.org/downloads">download</a>. This release includes several major features:</p> |
| |
| <ul> |
| <li>Disk quota isolation in Mesos containerizer; refer to the <a href="http://mesos.apache.org/documentation/latest/mesos-containerizer/">containerization documentation</a> to enable disk quota monitoring and enforcement.</li> |
| <li>Support for explicitly sending status updates acknowledgements from schedulers; refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrades document</a> for upgrading schedulers.</li> |
| <li>Rate-limiting slave removal, to safeguard against unforeseen bugs which may lead to widespread slave removal.</li> |
| <li>Support for module hooks in task launch sequence. Refer to the <a href="http://mesos.apache.org/documentation/latest/modules/">modules documentation</a> for more information.</li> |
| <li>Anonymous modules: a new kind of module that does not receive any callbacks but coexists with its parent process.</li> |
| <li>New service discovery info in task info allows framework users to specify discoverability of tasks for external service discovery systems. |
| Refer to the <a href="http://mesos.apache.org/documentation/latest/app-framework-development-guide/">framework development guide</a> for more information.</li> |
| </ul> |
| |
| |
| <p>Furthermore, many bugs have been fixed in this release. For full release notes with all features and bug fixes, please refer to the <a href="https://github.com/apache/mesos/blob/master/CHANGELOG">CHANGELOG</a>.</p> |
| |
| <p>Rolling upgrades may be done seamlessly, however some things have changed in 0.22.0 with regard to external tooling and upgrade paths; please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade guide</a> for detailed information on upgrading to this release from a 0.21.1 cluster.</p> |
| |
| <h2>Contributors</h2> |
| |
| <p>Thanks to the 35 contributors who made 0.22.0 possible: |
| Adam B, Alexander Rojas, Alexander Rukletsov, Ankur Chauhan, Benjamin Hindman, Benjamin Mahler, Bernd Mathiske, Chengwei Yang, Chi Zhang, Christos Kozyrakis, Cody Maloney, Connor Doyle, Dario Rexin, Dave Lester, David Robinson, Dominic Hamon, Evelina Dumitrescu, Gabriel Monroy, Ian Downes, Jake Farrell, Jiang Yan Xu, Jie Yu, Joerg Schad, Joris Van Remoortere, Kapil Arya, Kiyonari Harigae, Michael Park, Niklas Nielsen, Palak Choudhary, R.B. Boyer, Ryan Thomas, Samuel, Till Toenshoff, Timothy Chen and Vinod Kone.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-21-1-released/</id> |
| <link href="/blog/mesos-0-21-1-released/" /> |
| <title> |
| Apache Mesos 0.21.1 Released |
| </title> |
| <updated>2015-01-20T00:00:00Z</updated> |
| <author> |
| <name>Tim Chen</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.21.1 is now available for <a href="http://mesos.apache.org/downloads">download</a>. This release includes bug fixes that fixes a few performance issues and isolator cleanup, and also includes a few improvements around building mesos on OSX and the docker containerizer.</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2047">MESOS-2047</a> - Isolator cleanup failures shouldn&rsquo;t cause TASK_LOST.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2071">MESOS-2071</a> - Libprocess generates invalid HTTP</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2147">MESOS-2147</a> - Large number of connections slows statistics.json responses.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2182">MESOS-2182</a> - Performance issue in libprocess SocketManager.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1925">MESOS-1925</a> - Docker kill does not allow containers to exit gracefully</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-2113">MESOS-2113</a> - Improve configure to find apr and svn libraries/headers in OSX</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://github.com/apache/mesos/blob/master/CHANGELOG">CHANGELOG</a>.</p> |
| |
| <p>Upgrading to 0.21.1 can be done seamlessly on a 0.21.0 cluster. If upgrading from an earlier version, please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrades</a> documentation.</p> |
| |
| <h2>Contributors</h2> |
| |
| <p>Thanks to all the contributors for 0.21.1: Timothy Chen, Benjamin Mahler, Kapil Arya, Ryan Thomas, Jie Yu, Dario Rexin and Michael Park.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesoscon-2015-earlybird-registration-now-open/</id> |
| <link href="/blog/mesoscon-2015-earlybird-registration-now-open/" /> |
| <title> |
| MesosCon Early-Bird Registration Now Open |
| </title> |
| <updated>2015-01-14T00:00:00Z</updated> |
| <author> |
| <name>Dave Lester</name> |
| </author> |
| <content type="html"> |
| <p>A limited number of early-bird tickets are now available for <a href="http://mesoscon.org">#MesosCon 2015</a>, an annual conference organized by the Apache Mesos community. MesosCon brings together users and developers to share and learn about the project and its growing ecosystem, and will take place in Seattle, WA.</p> |
| |
| <blockquote class="twitter-tweet" lang="en"><p>.<a href="https://twitter.com/mesoscon">@MesosCon</a> early-bird registration is now open to the first 140 attendees! Join us! <a href="http://t.co/LcIclfttgq">http://t.co/LcIclfttgq</a> More info: <a href="http://t.co/Dnd5XWhoOH">http://t.co/Dnd5XWhoOH</a></p>&mdash; Apache Mesos (@ApacheMesos) <a href="https://twitter.com/ApacheMesos/status/555445970595368960">January 14, 2015</a></blockquote> |
| |
| |
| <p> <script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script></p> |
| |
| <p><a href="http://events.linuxfoundation.org/events/mesoscon/attend/register">Early-bird registration is open today</a> to the first 140 attendees / through February 14th, 2015.</p> |
| |
| <p>MesosCon will take place August 20 - 21, 2015 at Sheraton Seattle in Seattle, WA. The cost of early-bird registration is US$299. The standard attendee registration fee will be US$399 (Through July 31, 2015), and late registration US$499 beginning August 1, 2015. Students are eligible for a special registration fee of US$99 (Note that a valid student id will be required at onsite check-in).</p> |
| |
| <p>As part of the registration process, you&rsquo;ll have an opportunity to donate to a <a href="http://events.linuxfoundation.org/events/mesoscon/attend/scholarship">Diversity Scholarship</a> which has been established for the conference. MesosCon’s scholarship program provides support to women, people of color, and people with disabilities who may not otherwise have the opportunity to attend MesosCon for financial reasons. Equal access and diversity are important to MesosCon, and we aim to remove this obstacle for underrepresented attendee groups. We encourage you to donate what you can! If you have any questions regarding the diversity scholarship, please contact <a href="mailto:mesoscon-diversity@googlegroups.com">mesoscon-diversity@googlegroups.com</a>.</p> |
| |
| <p>On behalf of the #MesosCon Program Committee, we couldn’t be more excited about this year’s conference and what this means for the open source project’s community. We hope that you’ll join us!</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-21-0-released/</id> |
| <link href="/blog/mesos-0-21-0-released/" /> |
| <title> |
| Mesos 0.21.0 Released |
| </title> |
| <updated>2014-11-17T00:00:00Z</updated> |
| <author> |
| <name>Ian Downes</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.21.0, is now available for <a href="http://mesos.apache.org/downloads/">download</a>. This version includes the following features and improvements:</p> |
| |
| <ul> |
| <li>Task reconciliation for frameworks (<a href="https://issues.apache.org/jira/browse/MESOS-1407">MESOS-1407</a>)</li> |
| <li>Support for Mesos modules (<a href="https://issues.apache.org/jira/browse/MESOS-1931">MESOS-1931</a>)</li> |
| <li>Task status now includes source and reason (<a href="https://issues.apache.org/jira/browse/MESOS-343">MESOS-343</a>, <a href="https://issues.apache.org/jira/browse/MESOS-1143">MESOS-1143</a>)</li> |
| <li>A shared filesystem isolator (<a href="https://issues.apache.org/jira/browse/MESOS-1586">MESOS-1586</a>)</li> |
| <li>A pid namespace isolator (<a href="https://issues.apache.org/jira/browse/MESOS-1765">MESOS-1765</a>)</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://github.com/apache/mesos/blob/master/CHANGELOG">CHANGELOG</a>.</p> |
| |
| <h3>State Reconciliation</h3> |
| |
| <p>Frameworks are now able to reconcile task state through the mesos API, to ensure that they remain eventually consistent in the face of failures. Read more about reconciliation <a href="http://mesos.apache.org/documentation/latest/reconciliation/">here</a>.</p> |
| |
| <h3>Mesos Modules</h3> |
| |
| <p>Experimental support for Mesos modules was introduced in Mesos 0.21.0; |
| please note the <a href="http://mesos.apache.org/documentation/latest/modules">disclaimer</a>.</p> |
| |
| <p>Mesos modules provide a way to easily extend inner workings of Mesos by creating and using shared libraries that are loaded on demand. Modules can be used to customize Mesos without having to recompiling/relinking for each specific use case. Modules can isolate external dependencies into separate libraries, thus resulting into a smaller Mesos core. Modules also make it easy to experiment with new features. For example, imagine loadable allocators that contain a VM (Lua, Python, …) which makes it possible to try out new allocator algorithms written in scripting languages without forcing those dependencies into the project. Finally, modules provide an easy way for third parties to easily extend Mesos without having to know all the internal details.</p> |
| |
| <p>For more details, please read the <a href="http://mesos.apache.org/documentation/latest/modules">modules documentation</a></p> |
| |
| <h3>Task Status Includes Source and Reason</h3> |
| |
| <p>The <code>TaskStatus</code> associated with a status update has relied on a single enum and free-form string to communicate the status. There are benefits to adding more data to the status update, and in Mesos 0.21.0, we have introduced the notion of a <code>Source</code> and <code>Reason</code>.</p> |
| |
| <p>The source of a status update is, broadly speaking, the actor that changed the status. This can currently be Master, Slave, or Executor. Similarly, we have added an enumeration of reasons for the status update. The list can be found in <code>include/mesos/mesos.proto</code> and is fairly extensive.</p> |
| |
| <p>Our hope is that frameworks can use the source and reason to better communicate status updates to end users, and make better scheduling decisions.</p> |
| |
| <p>We have also introduced the notion of a <code>TASK_ERROR</code> state, distinct from <code>TASK_LOST</code>. The semantic difference is that tasks that are updated as lost can be rescheduled and should succeed, while tasks with status error will continue to fail if they are rescheduled. In Mesos 0.21.0 we do not send <code>TASK_ERROR</code> but it has been defined so frameworks can prepare to receive it. We will start sending it in Mesos 0.22.0.</p> |
| |
| <h3>Shared Filesystem Isolator</h3> |
| |
| <p>Mesos 0.21.0 introduces an optional shared filesystem isolator for the Mesos Containerizer. The isolator does not provide full filesystem encapsulation like Docker. It is intended for deployments where containers share the host&rsquo;s root filesystem but certain parts of the filesystem should be made private to each container.</p> |
| |
| <p>One example use-case is a private <code>/tmp</code> directory for each container. Processes running in the container will see a normal <code>/tmp</code> directory but it actually refers to a subdirectory of the executor work directory, e.g., the relative path <code>./tmp</code>. Processes will not be able to see files in the host&rsquo;s <code>/tmp</code> directory or the <code>/tmp</code> directory of any other container.</p> |
| |
| <p>This isolator is available only on Linux.</p> |
| |
| <h3>Pid Namespace Isolator</h3> |
| |
| <p>Mesos 0.21.0 also introduces an optional pid namespace isolator for the Mesos Containerizer. The isolator runs each container in its own pid namespace such that processes inside a container will not have visibility to processes running on the host or in other containers.</p> |
| |
| <p>The Mesos Containerizer Launcher has been updated to use the pid namespace to terminate all processes when destroying a container. This avoids known kernel bugs and race conditions when using the freezer cgroup. If the container is not running inside a pid namespace (started with an earlier slave version), the launcher will fall back to the prior behavior and use the freezer cgroup.</p> |
| |
| <p>This isolator is only available on Linux.</p> |
| |
| <h3>Getting Involved</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks</h3> |
| |
| <p>Thanks to the 27 <a href="https://github.com/apache/mesos/graphs/contributors">contributors</a> who made 0.21.0 possible:</p> |
| |
| <p>Adam Bordelon, Alexander Rukletsov, Benjamin Hindman, Benjamin Mahler, Bernd Mathiske, Chengwei Yang, Chi Zhang, Cody Maloney, Dave Lester, Dominic Hamon, Evelina Dumitrescu, Ian Downes, Jie Yu, Joe Gordon, Joris Van Remoortere, Dharmesh Kakadia, Kapil Arya, Michael Park, Niklas Q. Nielsen, R.B. Boyer, Thomas Rampelberg, Till Toenshoff, Timothy Chen, Timothy St. Clair, Tobi Knaup, Vinod Kone.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-20-1-released/</id> |
| <link href="/blog/mesos-0-20-1-released/" /> |
| <title> |
| Apache Mesos 0.20.1 Released |
| </title> |
| <updated>2014-09-23T00:00:00Z</updated> |
| <author> |
| <name>Adam B</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.20.1 is now available for <a href="http://mesos.apache.org/downloads">download</a>. One of the major features of Mesos 0.20.0 was native Docker support, and that support has been improved in 0.20.1 by the following bug fixes and improvements:</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1621">MESOS-1621</a> - Docker run networking should be configurable and support bridge network</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1724">MESOS-1724</a> - Can&rsquo;t include port in DockerInfo&rsquo;s image</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1730">MESOS-1730</a> - Should be an error if commandinfo shell=true when using docker containerizer</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1732">MESOS-1732</a> - Mesos containerizer doesn&rsquo;t reject tasks with container info set</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1737">MESOS-1737</a> - Isolation=external result in core dump on 0.20.0</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1755">MESOS-1755</a> - Add docker support to mesos-execute</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1758">MESOS-1758</a> - Freezer failure leads to lost task during container destruction.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1762">MESOS-1762</a> - Avoid docker pull on each container run</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1770">MESOS-1770</a> - Docker with command shell=true should override entrypoint</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1809">MESOS-1809</a> - Modify docker pull to use docker inspect after a successful pull</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://github.com/apache/mesos/blob/master/CHANGELOG">CHANGELOG</a>.</p> |
| |
| <p>Upgrading to 0.20.1 can be done seamlessly on a 0.20.0 cluster. If upgrading from 0.19.x, please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrades</a> documentation.</p> |
| |
| <h2>Contributors</h2> |
| |
| <p>Thanks to all the contributors for 0.20.1: Timothy Chen, Jie Yu, Timothy St. Clair, Vinod Kone, Chris Heller, Kamil Domański, and Till Toenshoff.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-20-0-released/</id> |
| <link href="/blog/mesos-0-20-0-released/" /> |
| <title> |
| Mesos 0.20.0 Released |
| </title> |
| <updated>2014-09-03T00:00:00Z</updated> |
| <author> |
| <name>Jie Yu</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.20.0, is now available for <a href="http://mesos.apache.org/downloads/">download</a>. This version includes the following features and improvements:</p> |
| |
| <ul> |
| <li>Native Docker support (<a href="https://issues.apache.org/jira/browse/MESOS-1524">MESOS-1524</a>)</li> |
| <li>Container level network monitoring (<a href="https://issues.apache.org/jira/browse/MESOS-1228">MESOS-1228</a>)</li> |
| <li>Framework authorization (<a href="https://issues.apache.org/jira/browse/MESOS-1342">MESOS-1342</a>)</li> |
| <li>Framework rate limiting (<a href="https://issues.apache.org/jira/browse/MESOS-1306">MESOS-1306</a>)</li> |
| <li>Building against installed third-party dependencies (<a href="https://issues.apache.org/jira/browse/MESOS-1071">MESOS-1071</a>)</li> |
| </ul> |
| |
| |
| <p>Full release notes are available in the release <a href="https://github.com/apache/mesos/blob/master/CHANGELOG">CHANGELOG</a>.</p> |
| |
| <h3>Native Docker Support</h3> |
| |
| <p>Mesos 0.20.0 introduces first-class <a href="https://www.docker.com/">Docker</a> support. Framework writers can now launch Docker containers for tasks by specifying <code>ContainerInfo</code> in <code>TaskInfo</code> or <code>ExecutorInfo</code>. The initial version allows the framework writers to specify Docker images for containers, and supports Docker primitives like volumes, entrypoints, etc.</p> |
| |
| <p>Native Docker support is enabled by a new containerizer called DockerContainerizer, which can launch a Docker container as either a Task or an Executor. In 0.20.0, Mesos supports running multiple containerizers simultaneously and allows containerizers to be chosen dynamically based on task/executor info (<a href="https://issues.apache.org/jira/browse/MESOS-1527">MESOS-1527</a>). Therefore, users can enable native Docker support without changing the containerizer strategy for their existing tasks.</p> |
| |
| <p>Details about native Docker support can be found in the <a href="http://mesos.apache.org/documentation/latest/docker-containerizer/">Docker containerizer documentation</a>.</p> |
| |
| <h3>Container Level Network Monitoring</h3> |
| |
| <p>Prior to Mesos 0.20.0, it was not possible to get the network statistics for each container, which made triaging or debugging network problems difficult in cases where multiple active tasks/executors were running on slave machines. Mesos 0.20.0 solves this problem by adding support for <a href="http://mesos.apache.org/documentation/latest/network-monitoring/">per-container network monitoring</a>. If you use the Mesos containerizer with the port_mapping isolator, network statistics for each active container can be retrieved through the <code>/monitor/statistics.json</code> endpoint on the slave.</p> |
| |
| <p>This network monitoring solution is completely transparent to the tasks running on the slave. Tasks will not notice any difference to running on a slave without network monitoring enabled and were sharing the network of the slave. There is no need for users to change their service discovery mechanism.</p> |
| |
| <h3>Framework Authorization</h3> |
| |
| <p>Authorization support has been implemented via Access Control Lists (ACLs). Authorization allows:</p> |
| |
| <ol> |
| <li>Frameworks to (re-)register with authorized ‘roles’</li> |
| <li>Frameworks to launch tasks/executors as authorized ‘users’</li> |
| <li>Authorized ‘principals’ to shutdown framework(s) through “/shutdown” HTTP endpoint</li> |
| </ol> |
| |
| |
| <p>For instance, operators can use authorization to only allow framework &ldquo;foo&rdquo; (and no other frameworks) to launch executors as &ldquo;root&rdquo;. For more details please read the <a href="http://mesos.apache.org/documentation/latest/authorization/">authorization documentation</a>.</p> |
| |
| <h3>Framework Rate Limiting</h3> |
| |
| <p>In a multi-framework environment, <a href="http://mesos.apache.org/documentation/latest/framework-rate-limiting/">framework rate limiting</a> aims to protect the throughput of high-SLA (e.g., production, service) frameworks by having the master throttle messages from other (e.g., development, batch) frameworks. Using this feature, an operator can specify the maximum number of queries per second and outstanding messages for the low-SLA frameworks on the master.</p> |
| |
| <h3>Building Against Installed Third-party Dependencies</h3> |
| |
| <p>Mesos 0.20.0 now supports building using system installed dependencies. Prior to this release, most of the third-party dependencies of Mesos were included in the project and statically linked into the resulting binaries and libraries. See <a href="https://issues.apache.org/jira/browse/MESOS-1071">MESOS-1071</a> for more details about these changes.</p> |
| |
| <h3>Future Work</h3> |
| |
| <p>Looking forward, here are a few upcoming features that are being worked on:</p> |
| |
| <ul> |
| <li>Improvement of Docker support in Mesos (<a href="https://issues.apache.org/jira/browse/MESOS-1524">MESOS-1524</a>)</li> |
| <li>On top of network monitoring, evaluating and providing support for per-container network isolation (<a href="https://issues.apache.org/jira/browse/MESOS-1585">MESOS-1585</a>)</li> |
| <li>Continued work on state reconciliation for frameworks (<a href="https://issues.apache.org/jira/browse/MESOS-1407">MESOS-1407</a>)</li> |
| </ul> |
| |
| |
| <h3>Getting Involved</h3> |
| |
| <p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://mesos.apache.org/community">user mailing list and IRC</a>.</p> |
| |
| <h3>Thanks</h3> |
| |
| <p>Thanks to the 29 <a href="https://github.com/apache/mesos/graphs/contributors">contributors</a> who made 0.20.0 possible:</p> |
| |
| <p>Adam B, Alexandra Sava, Anton Lindström, Benjamin Hindman, Benjamin Mahler, Bernardo Gomez Palacio, Bill Farner, Chengwei Yang, Chi Zhang, Connor Doyle, Craig Hansen-Sturm, Dave Lester, Dominic Hamon, Gaudio, Ian Downes, Isabel Jimenez, Jiang Yan Xu, Jie Yu, Ken Sipe, Niklas Nielsen, Thomas Rampelberg, Timothy Chen, Timothy St. Clair, Tobias Weingartner, Tom Arnfeld, Vinod Kone, Yifan Gu, Zuyu Zhang</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesoscon-2014-hackathon-details-announced/</id> |
| <link href="/blog/mesoscon-2014-hackathon-details-announced/" /> |
| <title> |
| #MesosCon Hackathon Details Announced |
| </title> |
| <updated>2014-07-24T00:00:00Z</updated> |
| <author> |
| <name>Dave Lester</name> |
| </author> |
| <content type="html"> |
| <p>After a <a href="http://mesoscon14.sched.org">full day of workshops and talks</a> at <a href="http://events.linuxfoundation.org/events/mesoscon">MesosCon</a>, we&rsquo;re challenging participants to hack on <a href="http://mesos.apache.org">Mesos</a> during an <a href="http://www.atlassian.com">Atlassian</a>-sponsored hackathon taking place Friday, August 22nd. This event is an opportunity to contribute to the project, collaborate with other members of the community, and learn in the process.</p> |
| |
| <p>We&rsquo;ve identified two categories of hacks that we hope participants will focus on:</p> |
| |
| <ul> |
| <li><em>Community Need</em>: These are issues logged in the <a href="https://issues.apache.org/jira/browse/MESOS/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel">Mesos issue tracker</a> that have received a large amount of activity (comments, votes, etc), and address some of the larger problems or pain points for the community. Suggested projects include new features, bugs, or documentation.</li> |
| <li><em>People&rsquo;s Choice</em>: These contributions will be voted on by your peers, and our guidance is intentionally open-ended so teams will run wild with their ideas. We&rsquo;re excited to see what you come up with.</li> |
| </ul> |
| |
| |
| <h2>Forming Groups</h2> |
| |
| <p>We strongly encourage hackathon participants to use the public <a href="https://issues.apache.org/jira/browse/MESOS/">JIRA issue tracker</a> to log and discuss their ideas prior to the hackathon, using the <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20MESOS%20AND%20labels%20%3D%20%22MesosConHack%22">MesosConHack label</a>. The <a href="http://mesos.apache.org/community/">project mailing lists and IRC</a> are good places to discover and share project ideas in advance.</p> |
| |
| <p>Thursday evening of MesosCon, teams will form and ideas may be pitched. Additionally, project committers will be on-site to act as mentors and shepherds throughout the hackathon.</p> |
| |
| <h2>Hackathon Rules</h2> |
| |
| <ul> |
| <li>Actual development on submissions should begin the evening of August 21st and must not begin earlier. However, teams are encouraged to have community discussions prior to the event.</li> |
| <li>In order for an entry to be valid, a pull request or review board patch must be submitted.</li> |
| <li>Submitted applications must run.</li> |
| <li>Teams may have a maximum of four contributors.</li> |
| <li>A team may only win one category.</li> |
| <li>Submissions must be related to Mesos in some way.</li> |
| </ul> |
| |
| |
| <h2>Schedule</h2> |
| |
| <h3>Thursday Evening</h3> |
| |
| <p>Following sessions on day one of MesosCon, we will hold a hackathon kickoff that includes an explanation of the rules, and a chance for ideas to be pitched and teams formed. Hacking may begin at this time, although evening hacking is optional.</p> |
| |
| <h3>Friday</h3> |
| |
| <p>9:00 - Hacking begins at conference center</p> |
| |
| <p>13:00 - Lunch arrives</p> |
| |
| <p>17:00 - Coding stops, refreshments are served</p> |
| |
| <p>17:15 - Re-explain the voting rules</p> |
| |
| <p>17:20 - Presentations start - Each team gets 5 minutes to pitch what they built and show it off</p> |
| |
| <p>18:00 - Voting occurs</p> |
| |
| <p>18:15 - Winners announced</p> |
| |
| <h2>Registration</h2> |
| |
| <p>Interested in participating in the hackathon? Participants must <a href="https://www.regonline.com/register/login.aspx?eventID=1533330&amp;MethodId=0&amp;EventsessionId=">register for MesosCon</a>.</p> |
| |
| <p>For new MesosCon registrants, you will see a checkbox at the time of registration. If you&rsquo;ve already registered for MesosCon, you will be contacted to confirm whether you plan to participate in the hackathon.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-19-1-released/</id> |
| <link href="/blog/mesos-0-19-1-released/" /> |
| <title> |
| Apache Mesos 0.19.1 Released |
| </title> |
| <updated>2014-07-21T00:00:00Z</updated> |
| <author> |
| <name>Ben Mahler</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.19.1 is now available for <a href="http://mesos.apache.org/downloads">download</a>. This release fixes a bug in the Java and Python APIs in which the garbage collection of a MesosSchedulerDriver object leads to a framework unregistration.</p> |
| |
| <p>More details can be found in <a href="https://issues.apache.org/jira/browse/MESOS-1550">MESOS-1550</a>, the <a href="http://mail-archives.apache.org/mod_mbox/mesos-user/201406.mbox/%3CCAFeOQnXVBBfgg4WQFatkHix2B1y-1o3EH3-mqtsgbEDeMH4Tbw%40mail.gmail.com%3E">report thread</a> from Whitney Sorenson, and the <a href="http://mail-archives.apache.org/mod_mbox/mesos-user/201406.mbox/%3CCAFeOQnVfhNo-mgkFsRn%3DvFsCQG%2Bj47xE3kdbFUDspWeOKjXA%3Dg%40mail.gmail.com%3E">follow up thread</a> from Benjamin Hindman.</p> |
| |
| <p>This release has the following bug fixes:</p> |
| |
| <ul> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1448">MESOS-1448</a> - Mesos Fetcher doesn&rsquo;t support URLs that have 30X redirects.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1534">MESOS-1534</a> - Scheduler process is not explicitly terminated in the destructor of MesosSchedulerDriver.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1538">MESOS-1538</a> - A container destruction in the middle of a launch leads to CHECK failure.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1539">MESOS-1539</a> - No longer able to spin up Mesos master in local mode.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1550">MESOS-1550</a> - MesosSchedulerDriver should never, ever, call &lsquo;stop&rsquo;.</li> |
| <li><a href="https://issues.apache.org/jira/browse/MESOS-1551">MESOS-1551</a> - Master does not create work directory when missing.</li> |
| </ul> |
| |
| |
| <p>Upgrading to 0.19.1 can be done seamlessly on a 0.19.0 cluster. If upgrading from 0.18.x, please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrades</a> documentation.</p> |
| |
| <h2>Contributors</h2> |
| |
| <p>Thanks to all the contributors for 0.19.1: Tom Arnfeld, Ian Downes, Benjamin Hindman, Benjamin Mahler, Vinod Kone, Whitney Sorenson.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-community-survey-2014-results/</id> |
| <link href="/blog/mesos-community-survey-2014-results/" /> |
| <title> |
| 2014 Mesos Community Survey Results |
| </title> |
| <updated>2014-06-24T00:00:00Z</updated> |
| <author> |
| <name>Dave Lester</name> |
| </author> |
| <content type="html"> |
| <p>Below are results of a community survey I led in May to get the pulse of the Apache Mesos community and improve our understanding of how others are using the software. We received a total of 55 responses.</p> |
| |
| <p>While I think the responses below speak for themselves, I wanted to highlight a few things:</p> |
| |
| <ul> |
| <li>A majority of responses came from adopters who have been using Mesos for more than 2 months.</li> |
| <li>Mesos had a <a href="http://www.netpromoter.com/why-net-promoter/know/">Net Promoter Score</a> of 41.5.</li> |
| <li>Documentation was the #1 community request for improving Mesos, followed by integrated Docker support. Unedited responses have been published as a <a href="https://gist.github.com/davelester/b40e3b5d0347540abf36">GitHub gist</a>.</li> |
| <li>36% of adopters are running Mesos in a cluster of 6-20 machines.</li> |
| <li>Almost half of Mesos adopters are running in private data centers. A majority of adopters running in the public cloud use AWS.</li> |
| <li>Hadoop, Marathon, and Chronos were the most-popular frameworks that are running in production.</li> |
| </ul> |
| |
| |
| <p>This is the first time we&rsquo;ve run a community survey like this; feedback is welcome on how we may improve it when we run it again.</p> |
| |
| <h3>How long have you been using Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_howlong.png" alt="How long have you been using Mesos" /></p> |
| |
| <h3>How many machines are you running in your Mesos cluster?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_howmanymachines.png" alt="How many machines are you running in your Mesos cluster" /></p> |
| |
| <h3>Frameworks: Are you using <a href="http://aurora.incubator.apache.org">Aurora</a> on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_aurora.png" alt="Are you using Aurora on Mesos" /></p> |
| |
| <h3>Frameworks: Are you using <a href="https://github.com/mesosphere/cassandra-mesos">Cassandra</a> on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_cassandra.png" alt="Are you using Cassandra on Mesos" /></p> |
| |
| <h3>Frameworks: Are you using <a href="https://github.com/airbnb/chronos">Chronos</a> on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_chronos.png" alt="Are you using Chronos on Mesos" /></p> |
| |
| <h3>Frameworks: Are you using <a href="https://github.com/mesos/hadoop">Hadoop</a> on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_hadoop.png" alt="Are you using Hadoop on Mesos" /></p> |
| |
| <h3>Frameworks: Are you using <a href="https://github.com/jenkinsci/mesos-plugin">Jenkins</a> on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_jenkins.png" alt="Are you using Jenkins on Mesos" /></p> |
| |
| <h3>Frameworks: Are you using <a href="http://www.grandlogic.com/content/html_docs/products.shtml#jobserverprod">JobServer</a> on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_jobserver.png" alt="Are you using JobServer on Mesos" /></p> |
| |
| <h3>Frameworks: Are you using <a href="https://github.com/mesosphere/marathon">Marathon</a> on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_marathon.png" alt="Are you using Marathon on Mesos" /></p> |
| |
| <h3>Frameworks: Are you using <a href="http://spark.apache.org/">Spark</a> on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_spark.png" alt="Are you using Spark on Mesos" /></p> |
| |
| <h3>Frameworks: Are you using <a href="https://github.com/mesosphere/storm-mesos">Storm</a> on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_storm.png" alt="Are you using Storm on Mesos" /></p> |
| |
| <h3>Frameworks: Are you using a custom framework on Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_framework_custom.png" alt="Are you using a custom framework on Mesos" /></p> |
| |
| <h3>Where do you run Mesos?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_wheredoyourun.png" alt="Where do you run Mesos" /></p> |
| |
| <h3>How likely are you to recommend Mesos to your friends and colleagues?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_nps.png" alt="How likely are you to recommend Mesos to your friends and colleagues?" /></p> |
| |
| <h3>Are you interested in contributing to Mesos in any of the following ways?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_contributions.png" alt="Are you interested in contributing to Mesos in any of the following way" /></p> |
| |
| <h3>Is your company listed on our <a href="http://mesos.apache.org/documentation/latest/powered-by-mesos/">#PoweredByMesos</a> page? If not, can we list you?</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_poweredby.png" alt="Is your company listed on our #PoweredByMesos page?" /></p> |
| |
| <p>(34 responses for &ldquo;No, but please refrain from adding us at this time&rdquo;, 8 responses for &ldquo;No, please add us&rdquo;, and 15 responses for &ldquo;Yes, we&rsquo;re on the list!&rdquo;)</p> |
| |
| <h3>Number of daily responses</h3> |
| |
| <p><img src="/assets/img/blog/communitysurvey_2014_responses.png" alt="Number of daily response" /></p> |
| |
| <h3>What features do you think are missing from Mesos?</h3> |
| |
| <p>The unedited responses to this question have been published as a <a href="https://gist.github.com/davelester/b40e3b5d0347540abf36">GitHub gist</a>.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-19-0-released/</id> |
| <link href="/blog/mesos-0-19-0-released/" /> |
| <title> |
| Apache Mesos 0.19.0 Released |
| </title> |
| <updated>2014-06-12T00:00:00Z</updated> |
| <author> |
| <name>Ben Mahler</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, 0.19.0 is now available for <a href="http://mesos.apache.org/downloads/">download</a>. This new version includes the following features and improvements:</p> |
| |
| <ul> |
| <li>The master now persists the list of registered slaves in a durable replicated manner using the Registrar and the replicated log.</li> |
| <li>Alpha support for custom container technologies has been added with the <a href="https://github.com/apache/mesos/blob/0.19.0/src/slave/containerizer/external_containerizer.hpp#L74">ExternalContainerizer</a>.</li> |
| <li>Metrics reporting has been overhauled and is now exposed on &lt;ip:port>/metrics/snapshot.</li> |
| <li>Slave Authentication: optionally, only authenticated slaves can register with the master.</li> |
| <li>Numerous bug fixes and stability improvements.</li> |
| </ul> |
| |
| |
| <p>Full release notes are available on <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&amp;version=12326253">JIRA</a>.</p> |
| |
| <h3>Registrar</h3> |
| |
| <p>Mesos 0.19.0 introduces the <a href="https://cwiki.apache.org/confluence/display/MESOS/Registrar+Design+Document">&ldquo;Registrar&rdquo;</a>: the master now persists the list of registered slaves in a durable replicated manner. The previous lack of durable state was an intentional design decision that simplified failover and allowed masters to be run and migrated with ease. However, the stateless design had issues:</p> |
| |
| <ul> |
| <li>In the event of a dual failure (slave fails while master is down), no lost task notifications are sent. This leads to a task running according to the framework but unknown to Mesos.</li> |
| <li>When a new master is elected, we may allow rogue slaves to re-register with the master. This leads to tasks running on the slave that are not known to the framework.</li> |
| </ul> |
| |
| |
| <p>Persisting the list of registered slaves allows failed over masters to detect slaves that do not re-register, and notify frameworks accordingly. It also allows us to prevent rogue slaves from re-registering; terminating the rogue tasks in the process.</p> |
| |
| <p>The state is persisted using the <a href="http://mesos.apache.org/blog/mesos-0-17-0-released-featuring-autorecovery/">replicated log</a> (available since 0.9.0).</p> |
| |
| <h3>External Containerization</h3> |
| |
| <p>As <a href="http://mesos.apache.org/blog/mesos-0-18-0-released/">alluded to</a> during the containerization / isolation refactor in 0.18.0, the ExternalContainerizer has landed in this release. This provides <strong>alpha</strong> level support for custom containerization.</p> |
| |
| <p><img src="/assets/img/documentation/containerizer_isolator_api.png" alt="Mesos Containerizer Isolator APIs" /></p> |
| |
| <p>Developers can implement their own external containerizers to provide support for custom container technologies. Initial Docker support is now available through some community driven external containerizers: <a href="https://github.com/duedil-ltd/mesos-docker-containerizer">Docker Containerizer for Mesos</a> by Tom Arnfeld and <a href="https://github.com/mesosphere/deimos">Deimos</a> by Jason Dusek. Please reach out on the mailing lists with questions!</p> |
| |
| <h3>Metrics</h3> |
| |
| <p>Previously, Mesos components had to use custom metrics code and custom HTTP endpoints for exposing metrics. This made it difficult to expose additional system metrics and often required having an endpoint for each libprocess Process (Actor) for which metrics were desired. Having metrics spread across endpoints was operationally complex.</p> |
| |
| <p>We needed a consistent, simple, and global way to expose metrics, which led to the creation of a metrics library within <a href="https://github.com/apache/mesos/tree/0.19.0/3rdparty/libprocess">libprocess</a>. All metrics are now exposed via /metrics/snapshot. The /stats.json endpoint remains for backwards compatibility.</p> |
| |
| <h3>Upgrading</h3> |
| |
| <p>For backwards compatibility, the &ldquo;Registrar&rdquo; will be enabled in a phased manner. By default, the &ldquo;Registrar&rdquo; is write-only in 0.19.0 and will be read/write in 0.20.0.</p> |
| |
| <p>If running in high-availability mode with ZooKeeper, operators must now specify the <code>--work_dir</code> for the master, along with the <code>--quorum</code> size of the ensemble of masters. This means adding or removing masters must be done carefully! The best practice is to only ever add or remove a single master at a time and to allow a small amount of time for the replicated log to catch up on the new master. Maintenance documentation will be added to reflect this.</p> |
| |
| <p>Please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrades</a> document, which details how to perform an upgrade from 0.18.x.</p> |
| |
| <h3>Future Work</h3> |
| |
| <p>Thanks to the Registrar, reconciliation primitives can now be provided to ensure that the state of tasks between Mesos and frameworks is kept consistent. This will remove the need for frameworks to implement out-of-band task reconciliation to inspect the state of slaves. Reconciliation work is being tracked at <a href="https://issues.apache.org/jira/browse/MESOS-1407">MESOS-1407</a>.</p> |
| |
| <p>The addition of state through the Registrar opens up a rich set of possible features that were previously not possible due to the lack of persistent state in the master. These include:</p> |
| |
| <ul> |
| <li>Cluster maintenance primitives (<a href="https://issues.apache.org/jira/browse/MESOS-1474">MESOS-1474</a>)</li> |
| <li>Repair automation (<a href="https://issues.apache.org/jira/browse/MESOS-695">MESOS-695</a>)</li> |
| <li>Global resource reservations</li> |
| </ul> |
| |
| |
| <h3>Getting Involved</h3> |
| |
| <p>We encourage you to try out this release, and let us know what you think and if you hit any issues on the user mailing list. You can also get in touch with us via <a href="http://twitter.com/ApacheMesos">@ApacheMesos</a> or via <a href="http://mesos.apache.org/community/">mailing lists and IRC</a>.</p> |
| |
| <h3>Thanks</h3> |
| |
| <p>Thanks to the 32 contributors who made 0.19.0 possible:</p> |
| |
| <p>Ashutosh Jain, Adam B, Alexandra Sava, Anton Lindström, Archana kumari, Benjamin Hindman, Benjamin Mahler, Bernardo Gomez Palacio, Bernd Mathiske, Charlie Carson, Chengwei Yang, Chi Zhang, Dave Lester, Dominic Hamon, Ian Downes, Isabel Jimenez, Jake Farrell, Jameel, Al-Aziz, Jiang Yan Xu, Jie Yu, Nikita Vetoshkin, Niklas Q. Nielsen, Ritwik Yadav, Sam Taha, Steven Phung, Till Toenshoff, Timothy St. Clair, Tobi Knaup, Tom Arnfeld, Tom Galloway, Vinod Kone, Vinson Lee</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesoscon-2014-program-announced/</id> |
| <link href="/blog/mesoscon-2014-program-announced/" /> |
| <title> |
| #MesosCon Program Announced, Now Including Hackathon |
| </title> |
| <updated>2014-06-11T00:00:00Z</updated> |
| <author> |
| <name>Dave Lester</name> |
| </author> |
| <content type="html"> |
| <p>Today we’re excited to announce the <a href="http://mesoscon14.sched.org/">program</a> for <a href="http://events.linuxfoundation.org/events/mesoscon">#MesosCon</a> 2014, the first ever conference dedicated to the Mesos ecosystem. It will take place in Chicago August 21-22, 2014, and be co-located with <a href="http://events.linuxfoundation.org/events/linuxcon-north-america">LinuxCon</a> 2014.</p> |
| |
| <p>MesosCon welcomes attendees who are advanced users, along with those that are new to the project. There will be time to socialize, share and learn from adopters to core committers. The first day will begin with an introductory <em>Mesos 101</em> workshop and keynote presentations from Mesos PMC lead Benjamin Hindman (Twitter) and John Wilkes (Google). Day one will include single track talks featuring:</p> |
| |
| <ul> |
| <li>Mesos <a href="http://mesos.apache.org/documentation/latest/mesos-frameworks/">frameworks</a>: including <a href="http://aurora.incubator.apache.org">Apache Aurora</a>, <a href="https://github.com/mesosphere/marathon">Marathon</a>, <a href="https://github.com/apache/spark">Spark</a>, and a stream processing framework developed by Netflix.</li> |
| <li>An operations perspective on Mesos: including talks on the challenges of running an elastic cluster, and using <a href="http://www.docker.com">Docker</a> with Mesos.</li> |
| <li>Presentations from companies who use Mesos in production: including eBay, HubSpot, and Airbnb. These presenters will also participate in a panel discussion.</li> |
| </ul> |
| |
| |
| <p>The final day will include a Mesos hackathon, generously sponsored by Atlassian. In advance of the hackathon, the community will seed ideas for specific features and projects to work on the <a href="http://www.mail-archive.com/user@mesos.apache.org/">community mailing list</a>.</p> |
| |
| <p><a href="https://www.regonline.com/Register/Checkin.aspx?EventID=1533330">Registration is open</a> and filling up quickly so register today. MesosCon is sponsored by Atlassian, eBay, Mesosphere, and Twitter. Interested companies can contact us regarding <a href="http://events.linuxfoundation.org/events/mesoscon/sponsor/become-a-sponsor">becoming a sponsor</a>.</p> |
| |
| <p>For the latest updates on #MesosCon, we invite you to follow <a href="http://twitter.com/mesoscon">@MesosCon</a> on Twitter.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-18-1-and-0-18-2-released/</id> |
| <link href="/blog/mesos-0-18-1-and-0-18-2-released/" /> |
| <title> |
| Mesos 0.18.1 and 0.18.2 Released |
| </title> |
| <updated>2014-05-29T00:00:00Z</updated> |
| <author> |
| <name>Niklas Quarfot Nielsen</name> |
| </author> |
| <content type="html"> |
| <p>We recently tagged two new bug fixes including our latest release: version <a href="http://mesos.apache.org/downloads/">0.18.2</a>. A bug was introduced in 0.18.1, prompting the release of 0.18.2. If you&rsquo;re using 0.18.1, it is highly recommended that you upgrade.</p> |
| |
| <p>The latest version of Mesos is available on our <a href="http://mesos.apache.org/downloads/">downloads</a> page.</p> |
| |
| <h3>Changes since 0.18.0</h3> |
| |
| <p>With the release of 0.18.1, Maven is now used to compile and package Mesos' Java files. In addition, the Mesos Java artifacts shade the protocol buffer dependency, allowing frameworks to independently declare their protobuf dependency version. Furthermore, a new extract flag has been added to the URI protocol buffer which makes it possible to control whether the fetcher should extract a given artifact. Various bugs in the Mesos master, the containerizer and the JNI code have been fixed as well. (see <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&amp;version=12326752">0.18.1 release notes</a>)</p> |
| |
| <p>0.18.2 fixed a bug which caused the mesos-fetcher to not apply the executer bit. For additional details, please see: <a href="https://issues.apache.org/jira/browse/MESOS-1313">MESOS-1313</a>.</p> |
| |
| <h3>Upgrading</h3> |
| |
| <p>If upgrading from 0.18.0 or 0.18.1, an upgrade can be applied seamlessly to running clusters. However, Maven is now a build dependency and must be installed in order to build Mesos with Java support.</p> |
| |
| <p>If upgrading from earlier versions than 0.18.0, please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">Upgrades</a> document.</p> |
| |
| <h3>Getting Involved</h3> |
| |
| <p>We encourage you to try out this release, and let us know what you think on the <a href="user@mesos.apache.org">user mailing list</a>. You can also get in touch with us via <a href="https://twitter.com/intent/user?screen_name=ApacheMesos">@ApacheMesos</a> or via <a href="https://mesos.apache.org/community">mailing lists and IRC</a>.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-18-0-released/</id> |
| <link href="/blog/mesos-0-18-0-released/" /> |
| <title> |
| Mesos 0.18.0 Released |
| </title> |
| <updated>2014-04-10T00:00:00Z</updated> |
| <author> |
| <name>Ian Downes</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, <a href="http://mesos.apache.org/downloads/">0.18.0</a> is now available for <a href="http://mesos.apache.org/downloads">download</a>. A major part of the 0.18.0 release is a refactor of the project’s isolation strategy, making it easier to develop and use different isolation technologies with Mesos including alternative implementations. The refactor does not introduce any new isolation features; instead, we’ve established a set of APIs that others can use to extend Mesos.</p> |
| |
| <h2>Isolation -> Containerization</h2> |
| |
| <p>The first change is in terminology. The Mesos Slave now uses a Containerizer to provide an environment for each executor and its tasks to run in. Containerization includes resource isolation but is a more general concept that can encompass such things as packaging.</p> |
| |
| <h2>Containerizer API</h2> |
| |
| <p>The Containerizer API specifies the interface between the slave and a Containerizer. An internal containerization implementation, called MesosContainerizer, includes all isolation features present in earlier releases of Mesos: basic isolation on Posix systems and CPU and memory isolation using Cgroups on Linux systems.</p> |
| |
| <p>One of the goals of the refactor was to enable alternative containerizer implementations. In particular, we encourage the community to add containerizer implementations which <em>delegate</em> containerization to other, existing technologies, e.g., LXC, Docker, VMware, Virtualbox, KVM and others.</p> |
| |
| <p>The folks at <a href="http://mesosphere.io">Mesosphere</a> are working on one approach for a general ExternalContainerizer which provides a simple shim interface between the Mesos slave and an external program that performs isolation. When complete, the ExternalContainerizer could connect to any external containerizer such as, for example, <a href="https://github.com/mesosphere/deimos">Deimos</a>, another Mesosphere project, to use Docker for containerization.</p> |
| |
| <h2>Isolator API</h2> |
| |
| <p>A second goal of the refactor was to make it easier to both develop and use different isolation components of the MesosContainerizer. To do this, we separated the coordination logic from the isolation logic. Users of Mesos now have more granular control over which isolation components a slave uses.</p> |
| |
| <p>MesosContainerizer accepts a list of Isolators, each implementing the Isolator API, to isolate resources. For example, the CgroupsMemIsolator uses the memory cgroup subsystem on Linux to limit the amount of memory available to an executor. We have plans to release new Isolators including a NetworkIsolator, a FilesystemIsolator, and a DiskIsolator and also to support isolation features provided by Linux namespaces such as pid and user namespaces.</p> |
| |
| <p><img src="/assets/img/documentation/containerizer_isolator_api.png" alt="Mesos Containerizer Isolator APIs" /></p> |
| |
| <h2>Cgroup layout change</h2> |
| |
| <p>While we were doing the refactor we took the opportunity to update the cgroup layout to current best practices, making it easier to run Mesos on recent Linux distributions and alongside other cgroup users such as LXC, Docker, and systemd. The expected layout has changed from a single mount point for all controllers to a separate mount point for each controller. This change requires reconfiguring the host system for every slave and we highly recommend a system reboot.</p> |
| |
| <p>Further details on the upgrade procedure are in the 0.18.0 <a href="http://mesos.apache.org/documentation/latest/upgrades">upgrade document</a> and, as always, please ask questions on the <a href="http://mesos.apache.org/community">mailing list</a>, file tickets via <a href="https://issues.apache.org/jira/browse/MESOS">JIRA</a>, or discuss on <a href="http://mesos.apache.org/community">IRC</a>.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-community-update-1/</id> |
| <link href="/blog/mesos-community-update-1/" /> |
| <title> |
| Mesos Community Update #1 |
| </title> |
| <updated>2014-03-28T00:00:00Z</updated> |
| <author> |
| <name>Matt Trifiro</name> |
| </author> |
| <content type="html"> |
| <p><em>This is a cross post from the <a href="http://mesosphere.io/community/2014/03/20/mesos-community-update-1/">Mesosphere blog</a>.</em></p> |
| |
| <p>Our community is in the midst of a revolution. Mesos is no longer an edge technology, only for the Twitters and Airbnbs of the world; it’s going mainstream and we are at its center. There is more activity on the Apache mailing lists, more commits in the code, more frameworks being developed, more developers building tools around Mesos—and, perhaps most excitingly, there are more companies deploying Mesos into production.</p> |
| |
| <p>All of this activity makes it harder to keep up!</p> |
| |
| <p>The Mesosphere team wants to help you keep up with all of the community activity by curating a concise semi-regular update, of which this is the first. We are looking to share the most interesting and important activities in the Mesos community.</p> |
| |
| <h3>Here are some recent highlights:</h3> |
| |
| <ul> |
| <li><p>Venture capital icon <a href="http://en.wikipedia.org/wiki/Vinod_Khosla">Vinod Khosla</a> gave a call-out to Mesos in his 2014 Open Networking Summit keynote, where he waxed about the need for a data center OS. The Mesos portion begins at 24:07 in the <a href="http://youtu.be/q61VkqZRjck?t=24m7s%20">ONS2014 Keynote YouTube video</a>.</p></li> |
| <li><p>Lab49 software engineer <a href="https://twitter.com/anvarkarimson">Anvar Karimson</a> re-implemented Stripe’s legendary Capture the Flag (CTF) system on Mesos. Read his blow-by-blow description here: <a href="http://karimson.com/posts/ctf-mesos/">Running Stripe CTF 2.0 on Mesos</a>.</p></li> |
| <li><p>Community member <a href="https://twitter.com/barton_tomas">Tomas Barton</a> gave an introductory talk on Mesos at the <a href="http://www.installfest.cz/if14/">InstallFest</a> in Prague. In his 59-slide talk, he covered everything from workload balancing to Mesos fault tolerance. View his presentation on SlideShare: <a href="http://www.slideshare.net/tomasbart/introduction-to-apache-mesos">Introduction to Apache Mesos</a>.</p></li> |
| <li><p>On February 27, <a href="http://mesos.apache.org/blog/mesos-0-17-0-released-featuring-autorecovery/">Mesos 0.17.0 was released</a> and you can <a href="http://mesosphere.io/downloads/#apache-mesos-0.17.0">download it here</a>. The 0.17.0 release features auto-recovery of the replicated log, which enhances Mesos’s high-availability and fault-tolerance. Read more here: <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&amp;version=12325669">Mesos 0.17.0 release notes</a></p></li> |
| <li><p>On the path toward fully implementing the <a href="https://cwiki.apache.org/confluence/display/MESOS/Registrar+Design+Document">Mesos Registrar Design</a>, we saw progress toward creating <a href="https://issues.apache.org/jira/browse/MESOS-764">persistence of state information for slaves</a>. Placing a small amount of state information in highly-available storage will make recovery of slaves faster and more graceful (this has been <a href="http://https//issues.apache.org/jira/browse/MESOS-295">lacking for a while</a>).</p></li> |
| <li><p>Mesosphere has packaged a pre-release version of Mesos 0.18.0 (release candidate 4) that you can now <a href="http://mesosphere.io/downloads/#apache-mesos-0.18.0-rc4">download</a>. The primary features of the <a href="https://github.com/apache/mesos/blob/0.18.0-rc4/CHANGELOG">upcoming 0.18.0 release</a> are changes that make it easier to insert pluggable container technologies, like Docker. 0.18.0 foreshadows some pretty interesting Docker integrations with Mesos.</p></li> |
| </ul> |
| |
| |
| <h3>Upcoming events:</h3> |
| |
| <ul> |
| <li><p>BBQ at Mesosphere HQ, 6-8 pm, March 28th. Come join us for a low-key BBQ. 145A Hampshire St, San Francisco (near Potrero @ 15th). Swing by and meet <a href="http://mesosphere.io/team/">our team</a>.</p></li> |
| <li><p><a href="http://apacheconnorthamerica2014.sched.org/">ApacheCon</a>, April 7-9 in Denver. Come see two Mesos presentations: <a href="http://apacheconnorthamerica2014.sched.org/event/d83ffc7d7c56620474eac1a2d8f09967">Mesos: Elastically Scalable Operations, Simplified</a> and <a href="http://apacheconnorthamerica2014.sched.org/event/803cb2a6f321ee02957b1c4eb4ebc01c">Building and Running Distributed Systems using Apache Mesos</a>.</p></li> |
| </ul> |
| |
| |
| <p>We hope to publish these updates at least a few times each month, and we’re interested in your suggestions. Please let us know what you think about the length, content and style, and send us your tips on what to publish each week. Do you have something to share? Write to us at <a href="mailto:community@mesosphere.io">community@mesosphere.io</a>.</p> |
| |
| <p><em>This post was co-authored by Abhishek Parolkar. Follow him on Twitter at <a href="https://twitter.com/parolkar">@parolkar</a>.</em></p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-17-0-released-featuring-autorecovery/</id> |
| <link href="/blog/mesos-0-17-0-released-featuring-autorecovery/" /> |
| <title> |
| Mesos 0.17.0 Released, Featuring Autorecovery for the Replicated Log |
| </title> |
| <updated>2014-03-13T00:00:00Z</updated> |
| <author> |
| <name>Jie Yu</name> |
| </author> |
| <content type="html"> |
| <p>The latest Mesos release, <a href="http://mesos.apache.org/downloads/">0.17.0</a> was made available for <a href="http://mesos.apache.org/downloads">download</a> last week, introducing a new autorecovery feature for the replicated log that handles additional disk failure and operator error scenarios.</p> |
| |
| <h2>What is the replicated log?</h2> |
| |
| <p>The replicated log is a distributed <em>append-only</em> log that stores arbitrary data as entries. Replication comes into play as at least a quorum of log replicas are stored on different machines, protecting the data from individual disk or network failures. The replicated log uses the <a href="http://en.wikipedia.org/wiki/Paxos_(computer_science%29">Paxos algorithm</a>. We will describe additional implementation details in both an upcoming blog post and project documentation.</p> |
| |
| <p>Mesos has had replicated log since version 0.9.0 and <a href="http://aurora.incubator.apache.org/">Apache Aurora</a>, a framework used in production at Twitter, uses replicated log for its persistent storage. Additionally, the Mesos master will start using the replicated log to persist some cluster state with the introduction of the <a href="https://issues.apache.org/jira/browse/MESOS-764">registrar</a>.</p> |
| |
| <h2>New feature in Mesos 0.17.0: <em>autorecovery</em></h2> |
| |
| <p>Before Mesos version 0.17.0, the replicated log could become inconsistent if a replica’s disk was replaced or the data was accidentally deleted by an operator. That meant that an operator couldn’t safely, or easily, replace a replica’s disk while the other replicas kept running. Instead, an operator had to stop all replicas, replace the disk, copy a pre-existing log, then restart all the replicas.</p> |
| |
| <p>As of this release, a replica with a new disk can automatically recover without operator involvement. As long as a quorum of replicas are available, applications using the replicated log won’t notice a thing!</p> |
| |
| <h2>Future work</h2> |
| |
| <p>The new autorecovery feature enables replacing a single replica at a time, but it does not allow an operator to easily add or remove replicas, known as <em>reconfiguration</em>. You can follow <a href="https://issues.apache.org/jira/browse/MESOS-683">MESOS-683</a> for the latest on this future work.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-16-0-released/</id> |
| <link href="/blog/mesos-0-16-0-released/" /> |
| <title> |
| Mesos 0.16.0 Released |
| </title> |
| <updated>2014-02-11T00:00:00Z</updated> |
| <author> |
| <name>Yan Xu</name> |
| </author> |
| <content type="html"> |
| <p>We recently released Mesos v0.16.0 on our <a href="http://mesos.apache.org/downloads/">downloads</a> page. It includes major <a href="https://issues.apache.org/jira/browse/MESOS-496">refactoring work</a> of the leading master election and detection process. This improves the reliability and flexibility of running multiple masters in your cluster, which provides Mesos with high availability.</p> |
| |
| <p>In high availability mode, if a leading master machine fails, Mesos holds elections to determine a new leader. Slave machines and schedulers detect the new leading master and connect to it, without disrupting services running on Mesos. Leader election implementation details, including how it works with <a href="http://zookeeper.apache.org">Zookeeper</a>, are detailed in the <a href="http://mesos.apache.org/documentation/latest/high-availability/">high availablity documentation</a>.</p> |
| |
| <h2>What&rsquo;s Changed</h2> |
| |
| <p>Aside from the refactoring, v0.16.0 includes fixes for bugs which caused incorrect termination of Mesos masters and slaves:</p> |
| |
| <ul> |
| <li>Fixed ZooKeeper related bugs which terminated Mesos processes instead of automatically retrying them: <a href="https://issues.apache.org/jira/browse/MESOS-463">MESOS-463</a>, <a href="https://issues.apache.org/jira/browse/MESOS-465">MESOS-465</a>, <a href="https://issues.apache.org/jira/browse/MESOS-814">MESOS-814</a>.</li> |
| <li>Non-leading Master now stays up after ZooKeeper session expiration or after it is partitioned from ZooKeeper.</li> |
| <li>Slave no longer attempts to recover checkpointed data after a reboot: <a href="https://issues.apache.org/jira/browse/MESOS-844">MESOS-844</a>.</li> |
| </ul> |
| |
| |
| <p>Click to read the full <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311242&amp;version=12325295">release notes</a>.</p> |
| |
| <h2>Upgrading</h2> |
| |
| <p>To upgrade a live cluster, please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">Upgrades document</a>.</p> |
| |
| <h2>Getting Involved</h2> |
| |
| <p>We encourage you to try out this release, and let us know what you think on the <a href="mailto:user@mesos.apache.org">user mailing list</a>. You can also get in touch with us via <a href="https://twitter.com/intent/user?screen_name=ApacheMesos">@ApacheMesos</a> or via <a href="https://mesos.apache.org/community">mailing lists and IRC</a>.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/framework-authentication-in-apache-mesos-0-15-0/</id> |
| <link href="/blog/framework-authentication-in-apache-mesos-0-15-0/" /> |
| <title> |
| Mesos 0.15 and Authentication Support |
| </title> |
| <updated>2014-01-09T00:00:00Z</updated> |
| <author> |
| <name>Vinod Kone</name> |
| </author> |
| <content type="html"> |
| <p>With the latest Mesos release, <a href="http://mesos.apache.org/downloads/">0.15.0</a>, we are pleased to report that we’ve added Authentication support for frameworks (see <a href="https://issues.apache.org/jira/browse/MESOS-418">MESOS-418</a>) connecting to Mesos. In a nutshell, this feature allows only authenticated frameworks to register with Mesos and launch tasks. Authentication is important as it prevents rogue frameworks from causing problems that may impact the usage of resources within a Mesos cluster.</p> |
| |
| <h2>How it works</h2> |
| |
| <ul> |
| <li><p><strong>SASL</strong></p> |
| |
| <p> Mesos uses the <a href="http://asg.web.cmu.edu/sasl/">Cyrus SASL library</a> to provide authentication. SASL is a very flexible authentication framework that allows two endpoints to authenticate with each other and also has support for various authentication mechanisms (ANONYMOUS, PLAIN, CRAM-MD5, GSSAPI etc).</p> |
| |
| <p> In this release, Mesos uses SASL with the CRAM-MD5 authentication mechanism. The process for enabling authentication begins with the creation of an authentication credential that is unique to the framework. This credential constitutes a <strong>principal</strong> and <strong>secret</strong> pair, where <strong>principal</strong> refers to the identity of the framework. Note that the <strong>principal</strong> is different from the framework <strong>user</strong> (the Unix user which executors run as) or the resource <strong>role</strong> (role that has reserved certain resources on a slave). These credentials should be shipped to the Mesos master machines, as well as given access to the framework, meaning that both the framework and the Mesos masters should be started with these credentials.</p> |
| |
| <p> Once authentication is enabled, Mesos masters only allow authenticated frameworks to register. Authentication for frameworks is performed under the hood by the new scheduler driver.</p></li> |
| </ul> |
| |
| |
| <p>For specific instructions on how to do this please read the <a href="http://mesos.apache.org/documentation/latest/upgrades/">upgrade</a> instructions.</p> |
| |
| <h2>Looking ahead</h2> |
| |
| <ul> |
| <li><p><strong>Adding authentication support for slaves</strong></p> |
| |
| <p> Similar to adding authentication support to frameworks, it would be great to add authentication support to the slaves. Currently any node in the network can run a Mesos slave process and register with the Mesos master. Requiring slaves to authenticate with the master before registration would prevent rogue slaves from causing problems (e.g., DDoSing the master, getting access to users tasks etc) in the cluster.</p></li> |
| <li><p><strong>Integrating with Kerberos</strong></p> |
| |
| <p> Currently the authentication support via shared secrets between frameworks and masters is basic to benefit usability. To improve upon this basic approach, a more powerful solution would be to integrate with an industry standard authentication service like <a href="http://en.wikipedia.org/wiki/Kerberos_(protocol">Kerberos</a>). A nice thing about SASL and one of the reasons we picked it is because of its support for integration with GSSAPI/Kerberos. We plan to leverage this support to integrate Kerberos with Mesos.</p></li> |
| <li><p><strong>Data encryption</strong></p> |
| |
| <p> Authentication is only part of the puzzle when it comes to deploying and running applications securely in the cloud. Another crucial component is data encryption. Currently all the messages that flow through the Mesos cluster are un-encrypted making it possible for intruders to intercept and potentially control your task. We plan to add encryption support by adding SSL support to <a href="https://github.com/3rdparty/libprocess">libprocess</a>, the low-level communication library that Mesos uses which is responsible for all network communication between Mesos components.</p></li> |
| <li><p><strong>Authorization</strong></p> |
| |
| <p> We are also investigating authorizing principals to allow them access to only a specific set of operations like launching tasks or using resources. In fact, you could imagine a world where an authenticated <strong>principal</strong> will be authorized to on behalf of a subset of <strong>user</strong>s and <strong>role</strong>s for launching tasks and accepting resources respectively. This authorization information could be stored in a directory service like LDAP.</p></li> |
| </ul> |
| |
| |
| <h3>Thanks</h3> |
| |
| <p>While a lot of people contributed to this feature, we would like to give special thanks to <a href="https://twitter.com/ilimugur">Ilim Igur</a>, our <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2013">Google Summer of Code</a> intern who started this project and contributed to the intial design and implementation.</p> |
| |
| <p>If you are as excited as us about this feature please go ahead and play with <a href="http://mesos.apache.org">Mesos 0.15.0</a> and let us know what you think. You can get in touch with us via <a href="http://mesos.apache.org/community/">our mailing lists or IRC</a>.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/niklas-nielsen-becomes-mesos-committer/</id> |
| <link href="/blog/niklas-nielsen-becomes-mesos-committer/" /> |
| <title> |
| Niklas Nielsen Becomes Newest Mesos Committer and PMC Member |
| </title> |
| <updated>2013-12-16T00:00:00Z</updated> |
| <author> |
| <name>Apache Mesos</name> |
| </author> |
| <content type="html"> |
| <p>The Apache Mesos PMC has voted to make <a href="http://mesosphere.io/2013/10/24/niklas-nielsen-joins-mesosphere/">Niklas Nielsen</a> the project&rsquo;s newest committer and PMC member. Niklas is an engineer at Engineer at <a href="http://mesosphere.io">Mesosphere</a>, and has a background in virtual machines, compilers and supercomputer tooling (distributed debuggers, profilers and so on).</p> |
| |
| <p>Nielsen has particular interests in performance, scalability and tooling to give insights in otherwise fairly complex setups. Welcome, Niklas!</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/mesos-0-14-2-released/</id> |
| <link href="/blog/mesos-0-14-2-released/" /> |
| <title> |
| Apache Mesos 0.14.2 Released |
| </title> |
| <updated>2013-11-12T00:00:00Z</updated> |
| <author> |
| <name>Ben Mahler</name> |
| </author> |
| <content type="html"> |
| <p>We recently released Mesos 0.14.2, a bugfix release with only a minor change related to cgroups isolation in 0.14.1. If you&rsquo;re using 0.14.1 with cgroups isolation, it is recommended to upgrade to avoid unnecessary out-of-memory (OOM) killing of jobs. The latest version of Mesos is available on our <a href="http://mesos.apache.org/downloads/">downloads</a> page.</p> |
| |
| <h3>Upgrading</h3> |
| |
| <p>If upgrading from 0.14.x, this upgrade can be applied seamlessly to running clusters. However, if you&rsquo;re upgrading from 0.13.x on a running cluster, please refer to the <a href="http://mesos.apache.org/documentation/latest/upgrades/">Upgrades</a> document, which details how a seamless upgrade from 0.13.x to 0.14.x can be performed.</p> |
| |
| <h3>Changes since 0.14.1</h3> |
| |
| <p>With the release of 0.14.1, when using cgroups isolation, the OOM semantics were altered to enable the kernel OOM killer and to use the memory soft limit combined with memory threshold notifications to induce OOMs in user-space. This was done to attempt to capture memory statistics at the time of OOM for diagnostic purposes. However, this proved to trigger unintended OOMs as the memory purging that occurs when the hard limit is reached was no longer occurring.</p> |
| |
| <p>0.14.2 no longer uses threshold notifications; the memory hard limit is now used instead to preserve the previous OOM semantics.</p> |
| |
| <p>For additional details, please see: |
| <a href="https://issues.apache.org/jira/browse/MESOS-755">MESOS-755</a>, |
| <a href="https://issues.apache.org/jira/browse/MESOS-762">MESOS-762</a>.</p> |
| |
| </content> |
| </entry> |
| |
| <entry> |
| <id>http://mesos.apache.org/blog/slave-recovery-in-apache-mesos/</id> |
| <link href="/blog/slave-recovery-in-apache-mesos/" /> |
| <title> |
| Slave Recovery in Apache Mesos |
| </title> |
| <updated>2013-10-23T00:00:00Z</updated> |
| <author> |
| <name>Vinod Kone</name> |
| </author> |
| <content type="html"> |
| <p>High availability is one of the key features of Mesos. For example, a typical Mesos cluster in production involves 3-5 masters with one acting as <em>leader</em> and the rest on standby. When a leading master fails due to a crash or goes offline for an upgrade, a standby master automatically becomes the leader without causing any disruption to running services. Leader election is currently performed by using <a href="http://zookeeper.apache.org/">ZooKeeper</a>.</p> |
| |
| <p>With the latest Mesos release, <a href="http://mesos.apache.org/downloads/">0.14.1</a>, we are bringing high availability to the slaves by introducing a new feature called <em>Slave Recovery</em>. In a nutshell, slave recovery enables:</p> |
| |
| <ol> |
| <li><p>Executors/tasks to keep running when the slave process is down.</p></li> |
| <li><p>A restarted slave process to reconnect with running executors/tasks on the slave.</p></li> |
| </ol> |
| |
| |
| <h2>Why it matters</h2> |
| |
| <p>A recoverable slave is critical for running services in production on Mesos for several reasons:</p> |
| |
| <ul> |
| <li><p><strong>Stateful services</strong></p> |
| |
| <p> In a typical production environment there are stateful services (e.g., caches) running in the cluster. It is not uncommon for these services to have a high startup time (e.g., cache warm up time of a few hours). Even in the analytics world, there are cases where a single task is responsible for doing work that takes hours to complete. In such cases a restart of the slave (e.g, crash or upgrade) will have a huge impact on the service. While sharding the service wider mitigates this impact it is not always possible to do so (e.g, legacy services, data locality, application semantics). Such stateful applications would benefit immensely from running under a more resilient slave.</p></li> |
| <li><p><strong>Faster cluster upgrades</strong></p> |
| |
| <p> It is important for clusters to frequently upgrade their infrastructure to stay up-to-date with the latest features and bug fixes. A typical Mesos slave upgrade involves stopping the slave, upgrading the slave libraries and starting the slave. In production environments there is always tension between upgrading the infrastructure frequently and the need to not impact long running services as much as possible. With respect to Mesos upgrades, if upgrading the slave binary has no impact on the underlying services, then it is a win for both the cluster operators and the service owners.</p></li> |
| <li><p><strong>Resilience against slave failures</strong></p> |
| |
| <p> While upgrading the slaves is most often the reason for restarting slaves, there might be other causes for a slave to fail. A slave crash could happen due to a bug in the slave code or due to external factors like a bug in the kernel or ZooKeeper client library. Typically such crashes are temporary and a restart of the slave is enough to correct the situation. If such slave restarts do not affect applications running on the slave it is a huge win for the applications.</p></li> |
| </ul> |
| |
| |
| <h2>How it works</h2> |
| |
| <ul> |
| <li><p><strong>Checkpointing</strong></p> |
| |
| <p> Slave recovery works by having the slave checkpoint enough information (e.g., task information, executor information, status updates) about the running tasks and executors to local disk. Once the slave and the framework(s) enable checkpointing, any subsequent slave restarts would recover the checkpointed information and reconnect with the executors. When a checkpointing slave process goes down, both the leading master and the executors running on the slave host wait for the slave to come back up and reconnect. A nice thing about slave recovery is that frameworks and their executors/tasks are oblivious to a slave restart.</p></li> |
| <li><p><strong>Executor Driver Caching</strong></p> |
| |
| <p> As part of this feature, the executor driver has also been improved to make it more resilient in the face of a slave failure. As an example, status updates sent by the executor while the slave is down are cached by the driver and sent to the slave when it reconnects with the restarted slave. Since this is all handled by the executor driver, framework/executor writers do not have to worry about it! The executors can keep sending status updates for their tasks while remaining oblivious to the slave being up or down.</p></li> |
| <li><p><strong>Reliable status updates</strong></p> |
| |
| <p> Another benefit of slave checkpointing the status updates is that now updates are more reliably delivered to frameworks in the face of failures. Before slave recovery if the slave fails at the same time that a master is failing over, no TASK_LOST updates for tasks running on the slave were sent to the framework. This is partly because the Mesos master is stateless. A failed over master reconstructs the cluster state from the information given to it by re-registering slaves and frameworks. With slave recovery, status updates and tasks are no longer lost when slaves fail. Rather, the slave recovers tasks, status updates and reconnects with the running executors. Even if an executor does terminate when the slave is down, a recovered slave knows about it from its checkpointed state and reliably sends TASK_LOST updates to the framework.</p></li> |
| </ul> |
| |
| |
| <p>For more information about how to enable slave recovery in your cluster, please refer to the <a href="https://github.com/apache/mesos/blob/master/docs/Slave-Recovery.md">documentation</a>.</p> |
| |
| <h2>Looking ahead</h2> |
| |
| <ul> |
| <li><p><strong>Easy Executor/Task Upgrades</strong></p> |
| |
| <p> In a similar vein to how slave recovery makes upgrading a Mesos cluster easy, we would like to enable frameworks to upgrade their executors/tasks as well. Currently the only way to upgrade an executor/task is to kill the old executor/task and launch the new upgraded executor/task. For the same reasons as we have discussed earlier this is not ideal for stateful services. We are currently investigating proper primitives to provide to frameworks to do such upgrades, so that not every framework have to (re-)implement that logic.</p></li> |
| <li><p><strong>State Reconciliation</strong></p> |
| |
| <p> While slave recovery greatly improves the reliability of delivering status updates there are still some rare cases where updates could be lost. For example if a slave crashes when a master is failing over and never comes back then the new leading master doesn&rsquo;t know about the lost slave and executors/tasks running on it. In addition to status updates, any driver methods (e.g., launchTasks, killTask) invoked when the master is failing over are silently dropped. Currently, frameworks are responsible for reconciling their own task state using the <a href="https://github.com/apache/mesos/blob/master/include/mesos/scheduler.hpp#L290">reconciliation API</a>. We are currently investigating ways to provide even better guarantees around reconciliation.</p></li> |
| <li><p><strong>Self Updates of Mesos</strong></p> |
| |
| <p> Currently, updating Mesos involves a cluster operator to manually upgrade the master and slave binaries and roll them in a specific manner (e.g., masters before slaves). But what if Mesos can update itself! It is not hard to imagine a future where Mesos masters can orchestrate the upgrade of slaves and maybe also upgrade one another! This would also help making rollbacks easy incase an upgrade doesn’t work because it would be much easier Mesos to check if various components are working as expected.</p></li> |
| </ul> |
| |
| |
| <p>So what are you waiting for? Go ahead and give <a href="http://mesos.apache.org">Mesos</a> a whirl and <a href="mailto:user@mesos.apache.org">let us know</a> what you think.</p> |
| |
| </content> |
| </entry> |
| |
| </feed> |
