After years of supporting some of the world’s most innovative and demanding applications,
Apache MesosNow version 1.0 is finally here. In fact, Mesos is growing and maturing much faster than its versions — otherwise, it wouldn’t be able to support Siri, Twitter, or our own
DC/OSPlatform and other important projects. None of this, however, detracted from the significance of the 1.0 milestone. There is no doubt that Mesos 1.0 brings with it a number of important new features that will make the project even more powerful and attractive.





Here’s a closer look at some of the highlights of the new release:


  • HTTP API: The new HTTP API makes Mesos easier for developers to write new Mesos frameworks, which means developers can build frameworks in any language that meets HTTP requirements (HTTP stands for ‘almost every major language’ here). Prior to this, developing the Mesos framework required us to deal with native Mesos drivers, which meant that you could only use a C-bound language. In addition, the HTTP API significantly simplifies the process of running various frameworks behind firewalls and inside containers.
  • Unified container tools: Say goodbye to Docker daemons. The unified container tool, already available in production environments, allows users to run their own image formats (including Docker) with Mesos tools based on the Mesos runtime. The macro benefits include further improvements in maturity and scalability, plus a significant simplification of operations. For example, you can upgrade probes within the Mesos runtime without having to restart the entire container.
  • CNI support: A new network isolation mechanism has been added to implement the Container Network Interface (CNI) specification. With the help of this feature, Mesos can now assign network namespaces to containers, while allowing different types of IP networks to be assigned to individual containers. A common use case for this feature is to implement a per-container unique IP setting.
  • GPU support: Support for GPU resource management mechanisms is also beginning to go into beta and is making good progress. This support capability was requested by the Mesos community and was a core priority — with the rapid adoption of machine learning technologies, users wanted to be able to migrate their workloads to Mesos clusters.
  • Fine-grained authorization: The authorization mechanism in Mesos has been overhauled in the new release to support fine-grained authorization of API resources. With the help of this new feature, Mesos has been able to take solid and agile steps toward becoming an enterprise multi-tenant platform.
  • Mesos on Windows: Support for Mesos on Windows is currently in beta testing, but progress is good. We expect to see a full Windows container experience in the third or fourth quarter of this year.
  • Agents, not slaves: As promised at MesosCon 15, a significant portion of the code base’s references to “slave” components have been updated to “Agent,” especially the majority of user-visible components, including websites, documents, HTTP apis, webuis, and so on. Renaming of internal components is also in progress.
  • API versioning and release strategy: The days of new API versions causing barriers to understanding and incompatibilities are over. The API versioning mechanism in Mesos 1.0 allows users to view changes between releases while ensuring that the new version is backward compatible with the original. The official release and support strategy also helps developers and operations staff have a clear expectation of its effects.





For more detailed information on Mesos 1.0, including an in-depth look at some of the key features, click here
hereSee an article by Vinod Kone on the Apache Mesos project website. For a full list of new features, improvements, and bug fixes, click here
hereReview the change record. You can also click on it
hereRead the Apache Software Foundation’s Mesos 1.0 press release.





The Mesosphere team is also excited about the release of Mesos 1.0. When we
When the open source DC/OS project was launched in April, Mesos co-founder and Mesosphere co-founder Ben Hindman
Has explained how DC/OS uses Mesos as the kernelIn order to realize the basic resource management function, plus some advanced functions related to it. For example, Mesos as a primitive implements a number of DC/ OS-specific features, including virtual networking, overlay networking, and fine-grained authorization.





The improvements in DC/OS functionality in user experience, user interface, networking, security, and container choreography would not have been possible without the solid and orderly improvements in Mesos. That’s why we’re excited to help Mesos take this next step. The DC/OS ecosystem is evolving rapidly, and the existence of Mesos has spawned a number of impressive real-world use cases.





To learn more about the origins and future direction of the Mesos project, check out Ben’s presentation at MesosCon 2016
Keynote speechAnd the University of California, Berkeley
Mesos paper. You can also see the INTRODUCTION to Mesos 1.0 provided by IBM
post.






Original link:Celebrating Apache Mesos 1.0: The world’s best cluster manager gets even better