4 min read
- HTTP API: The new HTTP API for Mesos make it much simpler for developers to write new Mesos frameworks, because they can write frameworks in any languages that can speak HTTP (read "nearly every popular language"). Previously, developing Mesos frameworks meant dealing with the native Mesos drivers, which meant only using languages with C bindings. The HTTP API also makes it easy to run frameworks behind firewalls and inside containers.
- Unified containerizer: Say goodbye to the Docker daemon. The production-ready unified containerizer lets users run their choice of image format (including Docker) atop the Mesos runtime, using Mesos tooling. This provides macro benefits such as maturity and scalability improvements, and also operational ones. With the Mesos runtime, for example, you can upgrade the agent without restarting all containers launched by it.
- CNI support: A new network isolator has been added that implements the Container Network Interface (CNI) specification. With this feature Mesos can now allocate network namespaces to containers, allowing containers to attach to different types of IP networks. One use case for this support is the ability to have IP per container.
- GPU support: Support for managing GPU resources is also in beta and progressing nicely. This is hugely important priority for the Mesos community, especially as machine learning usage ramps up and users want to migrate those workloads to their Mesos clusters.
- Fine-grained Authorization: Authorization in Mesos was completely overhauled in this release to support fine-grained authorization of API resources. With fine-grained authorization, Mesos makes great strides toward becoming an enterprise grade multi-tenant platform.
- Mesos on Windows: Support for Mesos on Windows is currently in beta for launching basic processes, but is progressing nicely. Expect to see a fully functional Windows containers experience land in the third or fourth quarter of this year.
- Agents, not slaves: As promised during MesosCon 15, a large portion of the code base has been updated to refer to the "slave" component as "agent". Specifically, most of the user-visible components (website, documentation, HTTP API, webUI, etc.) have been updated. Renaming of internal components is a work in progress.
- API versioning and release policy: Gone are the days of new API versions showing up as black boxes or causing incompatibilities. API versioning in Mesos 1.0 lets users see what has changed between versions and ensures backward compatibility with previous versions. The formal release and support policy sets clear expectations for developers and operators.