|
| 1 | +--- |
| 2 | +title: DC/OS 1.9.O is Generally Available! |
| 3 | +date: 2017-03-28 |
| 4 | +author: Judith Malnick, Mesosphere |
| 5 | +author_url: https://twitter.com/JudithPatudith |
| 6 | +category: releases |
| 7 | +description: We are excited to announce that DC/OS 1.9.0 is Generally Available today! Learn all about the new features and give it a try! |
| 8 | +layout: article.jade |
| 9 | +collection: posts |
| 10 | +lunr: true |
| 11 | +--- |
| 12 | + |
| 13 | +Today we're excited to announce that [DC/OS 1.9](https://dcos.io/releases/) is generally available! It includes updates that make deploying containers alongside data services---and operating them all on a common pool of resources---even easier. Our favorite features are reviewed here, but for a full list of what's new please check out the [release notes](https://dcos.io/releases/1.9.0/) and [documentation](https://dcos.io/docs/1.9/). |
| 14 | + |
| 15 | +<img src="/assets/images/blog/2017-03-30_1-9-0_GA_image_0.png" alt="DC/OS 1.9 Dashboard" /> *DC/OS 1.9 Dashboard* |
| 16 | + |
| 17 | +# New GUI |
| 18 | + |
| 19 | +To start with the most noticeable change, the DC/OS 1.9 Graphical User Interface has some beautiful improvements! In addition to the new, light look and feel, we've added a tab in the services view to help you troubleshoot deployments. Now you can select any service, and see each host where that service is running, along with whether or not each host has matched the service's requirements, for role, constraint, CPU, memory, disk, and port. |
| 20 | + |
| 21 | +<img src="/assets/images/blog/2017-03-30_1-9-0_GA_image_1.png" alt="Services deployment troubleshooting tab" /> *Services deployment troubleshooting tab* |
| 22 | + |
| 23 | +The new GUI also includes improved navigation, especially in the service-create workflow. To learn more about the UI, take a look at the [documentation](https://dcos.io/docs/1.9/usage/webinterface/#docs-article). If you have feedback or would like to get more involved with the DC/OS user experience please join the [UX working group](https://github.com/dcos/community/tree/master/wg-ux)! |
| 24 | + |
| 25 | +# GPU based scheduling |
| 26 | + |
| 27 | +DC/OS 1.9 includes Apache Mesos 1.2, which allows DC/OS users to manage GPU consuming frameworks like [Tensor Flow](https://github.com/tensorflow/ecosystem/tree/master/marathon) on the same cluster as CPU consuming resources like [Apache Cassandra](http://cassandra.apache.org/). The addition of GPU resources to DC/OS will be especially helpful for users interested in building or running deep learning and [fast data](https://dcos.io/fast-data/) applications. |
| 28 | + |
| 29 | +Frameworks can opt-in to access particular types of GPU resources (specified in agent attributes), which prevents services that only need CPUs from consuming GPUs. GPU resources are in preview, and only accessible when using the [Universal Container Runtime](https://dcos.io/docs/1.8/usage/containerizers/), with Docker runtime support targeted for DC/OS 1.10. For more information, check out the [DC/OS documentation](https://dcos.io/docs/1.9/usage/gpu/), and the more detailed [Mesos documentation](http://mesos.apache.org/documentation/latest/gpu-support/). |
| 30 | + |
| 31 | +# Operating on DC/OS |
| 32 | + |
| 33 | +## Unified Logging |
| 34 | + |
| 35 | +Starting with DC/OS version 1.9, task, container, service, node, and host level logs can be sent to journald. Operators can then collect and filter them with the logging aggregator of their choice, which gives them the flexibility to account for their specific security and privacy concerns. To learn more about getting DC/OS logs, please read Mesosphere's great [blog post](https://mesosphere.com/blog/2016/10/05/delivering-day-2-operations-with-dcos/) on it (part of their Day 2 Operations series), and check out the [documentation](https://dcos.io/docs/1.9/administration/logging/). Logging is experimental, and because of a bug in journald, it's disabled by default in this release, but please do turn it on and try it out. |
| 36 | + |
| 37 | +## Unified Metrics |
| 38 | + |
| 39 | +In 1.9, Metrics are available through an HTTP API, and Mesosphere is in the process of building a variety of [plugins](https://github.com/dcos/dcos-metrics/tree/master/plugins) to connect that API to the most popular aggregators, starting with [Datadog](https://www.datadoghq.com/). If you'd like to request a plugin (or build your own) please join the [day 2 operations working group](https://github.com/dcos/community/tree/master/wg-day-2-ops). You can read more about the new metrics functionality on Mesosphere's [blog](https://mesosphere.com/blog/2016/10/12/day-2-operations-metrics/), and in the [docs](https://dcos.io/docs/1.9/administration/metrics/). |
| 40 | + |
| 41 | +## Remote Container Shell (Debugging API) |
| 42 | + |
| 43 | +DC/OS allows you to launch and run containers while remaining agnostic to their physical location on nodes in your cluster. Container [debugging](https://dcos.io/docs/1.9/administration/debugging/), introduced in 1.9, allows DC/OS users to interact with any container that they have permission to access, without SSH, or any information about where that container is running. Debugging is experimental, and only available if you launched your containers using the Mesos container runtime or [Universal Container Runtime](https://dcos.io/docs/1.8/usage/containerizers/). |
| 44 | + |
| 45 | +# Pods |
| 46 | + |
| 47 | +Pods let you specify a set of one or more containers that should always run together on the same node. They can make sure that apps will always be able to communicate with necessary monitoring or service discovery, or ensure that co-dependent containers will never be provisioned on separate nodes, which is especially useful if you're in the process of transitioning to microservices from a monolithic app. |
| 48 | + |
| 49 | +You can set up pods by providing Marathon with a pod definition `.json` file, much like you do when specifying a Marathon app definition. For more information on how pods work under the hood check out the [blog post](https://dcos.io/blog/2017/exploring-pods-in-dc-os-1-9/index.html) by Elizabeth K. Joseph and Karl Isenberg. To learn more about using pods, please read [this post](https://mesosphere.com/blog/2017/03/15/introducing-pods-dcos-1-9/) from Amr Abdelrazik. Note that you need to use the [Universal Container Runtime](https://dcos.io/docs/1.8/usage/containerizers/) with pods, and that they are experimental in this release. Please try them out and file some bugs [here](https://jira.dcos.io/). |
| 50 | + |
| 51 | +# Data Services |
| 52 | + |
| 53 | +In addition to improvements to DC/OS itself, we're really proud to announce new packages in the DC/OS Universe service catalog, which our amazing technical partners created using the new software development kit (SDK). The SDK itself isn't ready for general use yet, so special thanks to the companies who took the time to work with Mesosphere to both contribute the following new, awesome packages, and to help improve the SDK. |
| 54 | + |
| 55 | +<img src="/assets/images/blog/2017-03-30_1-9-0_GA_image_2.png" alt="Packages in the DC/OS Universe service catalog" /> *Packages in the DC/OS Universe service catalog* |
| 56 | + |
| 57 | +## Alluxio |
| 58 | + |
| 59 | +Alluxio Enterprise Edition is based on an open source project that, like Apache Mesos, started at UC Berkeley's AMPLab. Alluxio connects various data applications (Apache Spark, Apache Flink, Hadoop Mapreduce, and others) to data storage systems (Amazon S3, Google Cloud Storage, Hadoop, etc.), while maintaining data transfer speeds. To learn more, sign up for the [webinar](https://event.on24.com/eventRegistration/EventLobbyServlet?target=reg20.jsp&referrer=&eventid=1386725&sessionid=1&key=B6BD11CCF8367BF616B0EB55E5020048®Tag=&sourcepage=register) on April 4th. |
| 60 | + |
| 61 | +## Datastax Enterprise Max |
| 62 | + |
| 63 | +Datastax offers enterprise products built on Apache Cassandra, and contributes to the open source project as well. A few months ago they created a Universe package for Datastax Enterprise (DSE), and now have added DSE Max, which includes analytics and search. To learn more, sign up for the [webinar](http://event.on24.com/wcc/r/1386670/FB17CDAD8DFD4EB72B22C807053A0919) on April 18th. |
| 64 | + |
| 65 | +## Couchbase |
| 66 | + |
| 67 | +Couchbase Server is an open source, distributed NoSQL document database, with integrated caching, that provides the power of SQL with the flexibility of JSON. It replicates data over multiple regions, for high availability and disaster recovery (HA/DR). Couchbase Lite runs on mobile and Internet of Things (IoT) devices, and syncs to Couchbase Server. To learn more, sign up for the [webinar](http://event.on24.com/wcc/r/1386709/B6E0D2323B9B6B675410D0063A05670E) on May 2nd. |
| 68 | + |
| 69 | +## Elastic Stack |
| 70 | + |
| 71 | +Elastic Stack is an out of the box version of the popular, open source ELK stack (Elasticsearch, Kibana, and Logstash), which aso includes Beats. Elastic Stack can be used for logging, and to used to ingest, search, analyze, and visualize other types of data in real-time. Managing the subcomponents of the Elastic Stack separately can be complex, but DC/OS makes it easy to launch and maintain. |
| 72 | + |
| 73 | +## Redis |
| 74 | + |
| 75 | +Redis is a in-memory data structure store, used as a NoSQL database, cache and message broker, for high performance operations. Redis Labs, the company behind the Redis open source project, offers an enterprise product that includes automated scaling, clustering, multi-zone high availability, auto-failover, continuous monitoring and 24x7 support. To learn more sign up for the [webinar](http://event.on24.com/wcc/r/1386729/B1E7090DA4489515C8525E1B33DA7373) on May 9th. |
| 76 | + |
| 77 | +## Try out the new packages |
| 78 | + |
| 79 | +For more details about the new packages, and the Universe, check out Mesosphere's [blog post](https://mesosphere.com/blog/2017/03/14/bringing-production-proven-data-services-to-dcos/) on new data services. All packages are installable from the DC/OS UI with [just a couple clicks or commands](https://dcos.io/docs/1.8/usage/managing-services/install/), and you can browse the complete list of packages available through the DC/OS Universe [here](https://universe.serv.sh/#/). |
| 80 | + |
| 81 | +# Learn more about DC/OS 1.9 |
| 82 | + |
| 83 | +This is a featureful release, and we're excited to hear your questions. We'll have a Q&A [office hours](https://www.meetup.com/DC-OS-Online-Meetup/events/238471362/) with Tal Broda (Mesosphere's VP of Engineering) on March 30th, where you can ask about any implementation questions that come up, via video chat. For help any time, join the DC/OS community [mailing list](https://groups.google.com/a/dcos.io/d/forum/users), or [Slack](http://chat.dcos.io/). And of course, if you find bugs we'd love your reports in [JIRA](https://jira.mesosphere.com/). [Try 1.9 out today](https://dcos.io/releases/1.9.0/); we hope you enjoy it! |
0 commit comments