The release notes provide a list of useful topics and links for DC/OS.
AcceptEULA parameter was removed from AWS templates. Any scripts written to deploy these templates may need to be updated so the parameter is no longer passed when deploying the templates.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.
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.
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:
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.
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.
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.
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.
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 the CLI binaries directly from the DC/OS UI. For more information, see the documentation.
Easy to deploy offline Universe. For more information, see the documentation.
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.
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.
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.
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.
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.
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.
dcos jobs command is now available in the CLI. For more information, see the documentation.java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty. The workaround is to restart the Package service (dcos-cosmos.service).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). genconf/ instead of /genconf/.dcos-3dt.service) with numerous bug fixes.dcos_generate_config.sh).gen_resolvconf.py will attempt to renameresolv.conf, but if that fails it will fall back to writing directly.dcos_add_user.py script. Just run sudo -i /opt/mesosphere/bin/dcos_add_user.py <password>. For more information see PR 609.--cli-telemetry-disabled, to disable the CLI basic telemetry. For more information, see the documentation./etc/resolv.conf around systemd-networkddcos-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/etc/os-release for OS Detectiondcos_generate_config.shdcos-adminrouter-reload.servicedcos-adminrouter-reload bug).Over 1350 other fixes and enhancements to DC/OS and DC/OS Services, including:
