java - What does Apache Mesos actually do? -
I am trying to wrap my head and clarification is required on some objects.
Understanding my is an executable which is installed on each physical / VM server (" node ") in the cluster, and then A Java API provides (somehow) that behaves as a pool of computing resources (CPU / RAM / etc), each individual node therefore, for coding programs against Java APIs, they only have one of the 1 single resources See the group, and worry about it Do not need to know how / where the code has been detected.
For one, I can basically be wrong in my understanding (in this case, please correct me!). But if I'm on target, then the Java API (provided by mesos) allows Java client to tap into these resources?!? Can anyone give a solid example of mesos in action?
Update
Take a look at my awesome drawing below, if I understand the mesos architecture correctly, then we have 3 physical servers ( phys01 , phys02 and phys03 ), each of these physical hosts is running a Ubuntu host (or whatever) via the hypervisor, Zen, we have 1 + V MS can run.
I like Doc & amp; CoreOS, so I'll use them in those examples, but I'm guessing that other non-container setups may also apply.
So we have CoreOS on every VM, running on every Core OS instance is a MSS executable / server, all the mesos nodes in the cluster see everything under them as a pool, and in the Majes Cluster Artifacts can be deployed arbitrarily and Másos will know which core OS instance is to actually implement them.
Mason's Top Marathon or Cubanets such as "Mason Framework" are various Docker Containers ( C1 - C4 ) running inside the Cubanets.
What is Mésos? Is more understanding less accurate?
Your summary is almost perfect but it does not represent the essence of representing the mesoscemic view of the mesosphere, project The company behind it, creating a "datacenter operating system" and a mesos kernel in the same parallel to the kernel of a normal OS. The API is not limited to Java, you can use C, C ++, Java / Scala or Python. If you have told about your quiz and want to use your resources, you usually do it through a structure instead of running your work load. This does not mean that it is complicated that it shows up. Framework exists for many popular distributed data processing systems, such as. There are other frameworks like the cron at the data center level or that allow you to run a dock-based application.
Update:
Yes, the mesos will take care about appointments in the cluster, as a kernel does - scheduling limited resources And there are many obvious questions raised in the management you prepared, however.
Layers under Maceio: I think it is possible but cumbersome. This is not a typical scenario for running a mesos - it is usually taken to the lowest possible layer (in your case, above Ubuntu). So I hope you have good reasons for running Coroz and a hypervisor.
Layers Above Messes: Cubernates are available in ITT Framework and Mesosphere, making a lot of effort in it. Regardless of any question, partially overlapping in terms of functionality - especially if you want to schedule basic workloads based on containers in relation to scheduling, you may be better with future or better in future If so, I hope that you have good reason for this very arrangement. Sidenot: Similar to the Kubernetes Marathon, which has a broader perspective and beautiful opinion.
Comments
Post a Comment