Shulou(Shulou.com)05/31 Report--

This article mainly introduces what Apache Mesos is, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand it.

Apache Mesos is such a "pre-Kubernetes" platform. Mesos was originally an open source project at the University of California, Berkeley for next-generation cluster management.

The aim is to learn from computing platforms such as Google's Borg and Facebook's Tupperware.

Unlike Borg and Tupperware, which are monolithic, Mesos takes an absolutely modular approach to getting things done.

Mesos provides isolation, locality, and even two-tier scheduling for CPU, memory, Istroke O, and the file system.

The purpose of Mesos guidance is as follows:

Extract data center resources

Put the workloads together

Deployment, self-healing, expansion, and upgrade are all automated

Provides the ability to run new applications without modifying the cluster manager

Provide massive expansion

One might attribute the above list to Kubernetes. Mesos can run in conjunction with microservices and containers.

In 2013, the founders of the project founded a company called Mesosphere, which used the technology to create an enterprise platform: the data center operating system (DCOS).

Shortly after its launch, Mesos was adopted by big companies such as Twitter, Apple, Yelp, Uber and Netflix.

Even with such a luxurious corporate lineup using Mesos, the platform was almost moved to the attic (that is, scrapped) earlier this year.

Why did this almost happen? You might as well find out.

1. Major decisions

On the apache.org Mesos mailing list, several posts show that the community has two different voices about what to do with Mesos:

Move Mesos to attic (Attic)

Reactivate the project

It is important to note that projects at the end of their lifespan are moved to Apache Attic.

According to Vinod Kone, Chairman of the Mesos Project Management Committee (PMC), the two factions can be summed up as follows:

Move to Attic: "so far, most of the existing members of PMC who have commented seem to be in favor of moving the project to Attic."

"the main reason for this faction seems to be that it is difficult to reactivate the project with new PMC members / submitters at this juncture," Kone continued. "in addition, it is a more accurate indication of the status quo of the project."

Reactivate: "there are some active users in the community who want to see the project stay active and are even willing to step forward and become submitters / contributors."

Kone continued: "some of these users work for companies that use Mesos in a production environment. They want to know the potential new roadmap and the manpower required (I think six to eight people are needed to be responsible for different aspects of the project)."

Like every project that has entered this stage, this boils down to a struggle between those who think it is useless to continue the project and those who are still using the project (and therefore consider it valuable to continue it).

But in the end, no one on Apache Mesos's private mailing list seems to be interested in keeping the project alive.

As we all know, without developers, the project is bound to be over. Even if someone is still interested in the project. Why?

The reason is simple: the project may still work without developers, but without engineers adding security patches and bug fixes, the project will soon become a security threat.

To this end, Kone said: "since existing submitters are unable or unwilling to guide new contributors to become new submitters, I think it is the right move to move the project to the attic. If you have no objection to this, I would be happy to call for a vote on this."

In this way, Apache Mesos is destined to be reduced to the field that was moved to the attic.

But then an interesting scene happened. In a new post on the Apache Mesos mailing list, Kone announced the news:

Thanks to the further responses of several people who have a strong interest in keeping the project going!

I also had the opportunity to have an in-depth conversation with some members of the Apache Software Foundation; in this regard, the Apache Software Foundation's preferred solution seems to be to keep the project going.

In view of the above, I cancel this voting post.

I will post a separate post to select a new PMC chairman and leave the addition of new PMC members / submitters to them.

Mesos survived at the last minute.

2. Why did this happen?

In short, Kubernetes captured the imagination of those interested in orchestrating distributed workloads.

Under pressure from the market, Mesosphere redesigned DCOS's platform in 2019, integrating Kubernetes and renaming itself D2IQ.

However, Mesos is still a viable platform with many production users. That said, why was Mesos so close to being scrapped?

According to Vinod, the project has proved to be in decline due to obstacles to the granting of rights to the submitter.

In fact, Vinod said on this topic: "the criteria we currently set for new submitters are very high, and I don't think any current contributor will be immediately eligible to be selected as a submitter."

Therefore, the Apache Mesos team has two options:

Change the guidelines.

Let some existing submitters guide some contributors to become submitters.

In the end, it turned out that the Apache Software Foundation abandoned its claim and supported the third option: find a new PCM chairman so that new members could be added to the project.

Mesos is dead, Mesos is immortal!

One of the major advantages of open source software is clearly illustrated here. Apache Mesos would have been moved to the attic and become a collective good memory for developers and administrators. Fortunately, it finally avoids this outcome and will continue to exist.

However, even if Mesos is destined to be moved to the attic, it may eventually return to GitHub in the form of fork and survive, just with a different name and a different group of developers.

It's hard to say what will happen to Mesos when he finds himself at the helm of a new leader. However, which developer or team wants to keep the project can contact the Apache Software Foundation to see what options are available.

Thank you for reading this article carefully. I hope the article "what is Apache Mesos" shared by the editor will be helpful to you. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.