Mesosphere Releases Datacenter Operating System Version 1.4

Add Your Comments

Version 1.4 of the Mesosphere Datacenter Operating System (DCOS) is now generally available, featuring user interface updates, support for Marathon 0.13.0 and Chronos, and the Mesos 0.25.0 kernel.

The release notes detail some of the improvements to DCOS, which uses modern Linux containers to quickly deploy applications and services such as Spark, Kubernetes, Jenkins, and Hadoop across clouds, VMs and local servers. DCOS can also ensure high availability automatically re-allocates resources from servers that fail to ensure workloads stay running.

Interface Improvements

In the DCOS UI, side panels display new details about nodes, services, and tasks, and include the ability to download files from a task and task failure rates shown correctly now. Graphs now give an indication of network interruption and hanging requests.

The Cassandra Command Line Interface (CLI) has also been added.

Marathon and Chronos

DOCS 1.4 also has support for Chronos, a lightweight and fault-tolerant scheduling tool originally built by Airbnb to run on top of Mesos and use Mesos’ primitives for storing state and distributing work.

It supports the latest verion of Marathon 0.13.0 (verison 0.13.0), which has a brand new UI. This version of Marathon ships with the ability to load and use external plugins, allowing extension and adaptability in Marathon to specific needs. The first plugins include pluggable authentication and authorization hooks.

There’s new support for Apache ZooKeeper scheduler task keys and storage formatting, as well as Zookeeper compression. It also supports the logging backend Logback.

Mesos 0.25 Support

Mesos 0.25.0 is included, meaning there’s now experimental support for maintenance primitives. Maintenance primitives facilitate communication between the frameworks and operator within a Mesos cluster and let most Mesos upgrades to be done without affecting running tasks.

It also adds master endpoints, reserve and /unreserve for dynamic reservations. And extended module APIs would enable IP per container assignment, isolation and resolution.

There are still a few known issues in this version of DCOS such as not being able to consistently render more than 5,000 tasks in the the Service and Agent panels web interface. So, some of these small refinements are due to be addressed in future releases.

Add Your Comments

  • (will not be published)