DC/OS Release 1.8.7

DownloadView Documentation →

The release notes provide a list of useful topics and links for DC/OS.

Breaking Changes

  • Manual modifications of Admin Router config are not supported. If you require a custom certificate, you must run HAProxy in front of Admin Router.
  • Network Time Protocol (NTP) must be enabled on all nodes for clock synchronization. For more information, see the documentation.

What's New

Apache Mesos 1.0 and Marathon 1.3 integrated

Container Orchestration

Services ("Built-In" Marathon)

Marathon is not just one container orchestrator out of many that we support; it is our default way to run things on DC/OS, supporting the full range of DC/OS features. In this release we'll have a major change in the Services tab in DC/OS. The native DC/OS Marathon instance UI is now fully integrated with the DC/OS UI. You can access it from the Services tab on the DC/OS UI. The new fully integrated UI no longer shows a list of frameworks, but shows an embedded Marathon. This means that all of your services and applications are in one place.

For more information, see the documentation.

Jobs - Ability to run scheduled jobs on DC/OS

There is now built-in support of running scheduled jobs. We created a new Apache Mesos framework called Metronome. Metronome is integrated natively with DC/OS and is available from the Jobs tab on the DC/OS UI. You can create and administer scheduled jobs directly from the Jobs tab. Similar to the Services tab for long-running applications, you can manage all of your Jobs from one centralized place. You can set up jobs with a scheduler by using the cron format.

Additionally, you can specify attributes like the time zone or a starting deadline. We also have a JSON view mode which allows you to specify everything in one file to easily copy and paste it. We will constantly improve and extend the given functionality. Metronome will likely replace Chronos as our DC/OS job framework. If you still need Chronos, you can get it from the DC/OS Universe.

For more information, see the documentation.

DC/OS Universal container runtime

The Universal container runtime extends the Mesos containerizer to support provisioning Docker container images (AppC coming soon). This means that you can use both the Mesos containerizer and other container image types in DC/OS. You can still use the Docker container runtime directly with DC/OS, but the Universal container runtime supports running Docker images independent of the Docker Engine, which allows for better integration with Mesos.

The Universal container runtime offers the following advantages:

  • Removes your dependency on the Docker daemon: With previous versions of Docker, if the Docker daemon was not responsive, a restart to the daemon caused all containers to stop on the host. In addition, Docker must be installed on each of your agent nodes in order to use the Docker containerizer. This means that in order to use the Docker containerizer you need to upgrade Docker on the agent nodes each time a new version of Docker comes out.
  • The Universal container runtime is more stable and allows deployment at scale.
  • The Universal container runtime offers features not available in the Docker containerizer, such as GPU and CNI support.
  • The Universal container runtime allows you to take advantage of continuing innovation within both the Mesos and DC/OS, including features such as IP per container, strict container isolation and more.

Note: The Universal container runtime is in the experimental phase. We encourage you to try it out and let us know what you think.

For more information, see the documentation.

Networking Services

IP per Container with VxLAN based Virtual Networks

DC/OS comes with built-in support for Virtual Networks leveraging the Container Network Interface (CNI) standard, and one default Virtual Network named dcos. Any container that attaches to a Virtual Network receives its own dedicated IP. This allows users to run workloads that are not friendly to dynamically assigned ports and would rather bind to the ports in their existing app configuration. Now, with dedicated IP/Container, workloads are free to bind to any port as every container has access to the entire available port range.

For more information, see the documentation.

DNS Based Service Addresses for Load Balanced Virtual IPs

DC/OS 1.8 introduces DNS Named Service Addresses for VIPs. With DNS Named VIPs, clients connect with a service address instead of an IP address. Due to the way DNS Named VIPs are generated in DC/OS, the risk of collision associated with IP VIPs does not exist. This means that administrators do not need to carefully manage DNS Named VIPs to avoid collision. This also means DNS Named VIPs can be automatically created at the time of service installation.

For more information, see the documentation.

Network Isolation of Virtual Network Subnets

DC/OS now supports the creation of multiple virtual networks at install time and will associate non-overlapping subnets with each of the virtual networks. Further, DC/OS users can program Network Isolation rules across DC/OS agent nodes to ensure that traffic across Virtual Network subnets is isolated.

For more information, see the documentation.

CLI

Binary CLIs for Linux, Windows, and Mac

Installing the DC/OS CLI is easier than ever. We’ve replaced the install script with a simple binary CLI.

For more information, see the documentation.

Download CLI binaries from DC/OS UI

Download the CLI binaries directly from the DC/OS UI. For more information, see the documentation.

Package Management Service

Easy to deploy offline Universe. For more information, see the documentation.

DC/OS Data services

  • Non-root user config (except Cassandra).
  • Binary CLIs for all services.

HDFS Service

DC/OS Universe now has a new DC/OS HDFS Service. This new DC/OS HDFS Service is an entirely new implementation sharing no code with the previous DC/OS HDFS Services. DC/OS HDFS Service can be deployed with a single command. Multiple instances of the DC/OS HDFS Service can be deployed to a single DC/OS cluster. Configuration of a DC/OS HDFS Service can updated at runtime without service interruption. DC/OS HDFS Service instances reserve all resources including CPU, Memory, Disk and Network Ports.

For more information, see the documentation.

Kafka Service

DC/OS Universe has an updated DC/OS Kafka Service. The updated DC/OS Kafka Service now supports configuring ZK service for Apache Kafka.

For more information, see the documentation.

Confluent Kafka Service

DC/OS Universe has a DC/OS Confluent Platform Service that is based on the DC/OS Kafka Service. Confluent offers support for the DC/OS Confluent Platform Service on DC/OS.

For more information, see the Universe documentation.

Cassandra Service

DC/OS Universe has an updated DC/OS Cassandra Service. The updated DC/OS Cassandra Service now supports multi-datacenter Cassandra ring topologies, and backup and restore with Azure Storage.

For more information, see the documentation.

Datastax Enterprise (DSE) Service

DC/OS Universe has a DC/OS DataStax Enterprise (DSE) Service that is based on the DC/OS Cassandra Service. DataStax offers support for the DC/OS DataStax Enterprise Service on DC/OS.

For more information, see the Universe documentation.

Spark Service

DC/OS Universe has an updated version of Apache Spark based on 1.6.2. In addition to all the of features of Apache Spark 1.6.2, the DC/OS Spark Service supports Kerberos and SSL with secure HDFS clusters. Latest stable Spark with coarse-grained scheduler.

For more information, see the documentation.

Developer Agility

  • New Artifactory Package. For more information, see the documentation.
  • Artifactory Package. For more information, see the documentation.
  • Updated Jenkins packages. For more information, see the documentation.

Enhanced Cloud Templates

  • You can use customized Amazon Machine Images (AMI) based on CentOS 7 or CoreOS to launch DC/OS with the advanced templates. For more information, see the documentation.
  • You can create custom advanced templates for DC/OS and then deploy and run DC/OS from your own private S3 bucket. For more information, see the documentation.

Improved UI and CLI improvements

Minor releases

1.8.7 - Nov 14, 2016

New and changed features

Fixed issues

  • DCOS-10959 - Update 1.8 Java to 8u112.
  • DCOS-11027 - Network performance improvements for 1,000 node clusters.
  • DCOS-11260 - In some situations, Marathon can fail to elect a leader during ZooKeeper restart.
  • Warning: constraint validation change: Constraint validation in Marathon is significantly improved with Marathon 1.3.x. Previously acceptable values for regular expressions, such as LIKE and UNLIKE, may no longer pass validation since they are not valid regular expressions. Where possible, Marathon will correct the regular expression (specifically * to .*); however, when this is not possible, the constraint will be removed and a warning will be logged for the affected app IDs.

1.8.6 - October 19, 2016

Fixed issues

  • DCOS-450 - Fixed race condition in diagnostics service.

1.8.5 - October 13, 2016

Fixed issues

  • HTTP Proxy is now fixed. For more information, see the documentation.
  • CORE-632 - Fixes for logrotation in Mesos.
  • DCOS-9966 - Improved error messages are printed for NTP service startup check.

1.8.4 - September 15, 2016

New and changed features

  • DCOS-8848 - Experimental support for the Universal container runtime in DC/OS.
  • DOCS-1113 - dcos jobs command is now available in the CLI. For more information, see the documentation.

Fixed issues

  • DCOS-9637 - Now reports the correct URL for AWS templates.
  • DCOS-9104 - Task count and resources are correct in the UI.
  • DCOS-9617 - The UID of remote users is shown in the UI.
  • DCOS-9191 - Added DNS for discoverable services to the UI.
  • DCOS-9162 - Enabled Kill and Scale for locked services.

Known issues and limitations

  • DCOS-9783 - Package service broken with java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. The workaround is to restart the Package service (dcos-cosmos.service).

1.8.3 - September 6, 2016

New and changed features

  • You can generate custom AWS Advanced templates from the custom installer file (dcos_generate_config.sh --aws-cloudformation) and a configuration file (config.yaml). Only a subset of the configuration file options are allowed (e.g. resolvers and exhibitor_backend cannot be changed).
  • New version of the Jobs component (Metronome 0.1.9).
  • To clarify the location of the installed files, the DC/OS installer refers to genconf/ instead of /genconf/.
  • CentOS AMIs are updated to include a fix for a Docker 1.11.2 bug, which caused Docker to not start.
  • DC/OS can now be built using older Docker versions.
  • Mesos-DNS 0.5.3-rc2.
  • Updated DC/OS UI.
  • Marathon 1.3.0-RC6 release notes.
  • Updated the DC/OS Diagnostics component (dcos-3dt.service) with numerous bug fixes.
  • BUILD_DIR is no longer printed when you run the custom installer (dcos_generate_config.sh).
  • The custom DC/OS installer has been refactored and reworked.
  • gen_resolvconf.py will attempt to renameresolv.conf, but if that fails it will fall back to writing directly.
  • If you have an existing SSH connection to a master, you can quickly add a new user to your cluster with the dcos_add_user.py script. Just run sudo -i /opt/mesosphere/bin/dcos_add_user.py <password>. For more information see PR 609.

Fixed issues

1.8.2 - August 25, 2016

New and changed features

  • Marathon 1.3.0-RC5
  • CentOS 7 AMI builder scripts
  • Updated Cosmos API for DC/OS services
  • Added a flag to the custom installer, --cli-telemetry-disabled, to disable the CLI basic telemetry. For more information, see the documentation.
  • Improved handling of /etc/resolv.conf around systemd-networkd
  • Moved REX-Ray out of the agent advertised port range
  • The preflight port check is different for masters and agents
  • Removed SPDY and HTTP/2 from admin router (the nginx and OpenResty is broken)
  • Always enable EBS optimization for AWS clusters (EbsOptimized)
  • Fold dcos-vol-discovery-{priv,pub}-agent.service into the appropriate dcos-mesos-slave service, making it easier to change the resources on a host and reset the agent
  • Marathon and Metronome run as non-root
  • Switch to /etc/os-release for OS Detection
  • Switch to argparse's default help for dcos_generate_config.sh
  • General internal code cleanup and technical debt fixes

Fixed issues

  • Named VIPS with 2 or more ports in use.
  • dcos-adminrouter-reload.service
  • Diagnostics component checking of timer units which exit non-zero (found the dcos-adminrouter-reload bug).

1.8.1 - August 2016

Fixes and enhancements

Over 1350 other fixes and enhancements to DC/OS and DC/OS Services, including:

  • DCOS-7415 - Unable to fetch /v2/tasks as plaintext for Marathon 0.15.3 in some cases.
  • DCOS-7422 - Improved reconnect logic in the case of root Marathon / Mesos master disconnections.
  • DCOS-7810 - Invalid IDs inside of nested groups leading to unexpected blocked deployments.
  • DCOS-7926 - Improved Marathon performance while deploying thousands of tasks.
  • DCOS-8128 - Improved Marathon task recovery in the case of some network events.
  • DCOS-8370 - Apps should not be able to share the same service port on a single host.
  • DCOS-8730 - Admin Router does not respect ports provided by external proxy.
  • MARATHON-888 - Improved handled of orphaned containers after master failover.
  • MARATHON-956 - Improved Marathon performance to prevent occurrence of "futures timed out" errors.

Known issues and limitations

  • DCOS-270 - Docker version 1.12.x is not supported.
  • DCOS-8975 - Port mapping for virtual networks is not displayed correctly.