Chapter 1. Introducing Mesos
Figure 1.1. Frameworks sharing datacenter resources offered by Mesos
Figure 1.2. Mesos advertises the available CPU, memory, and disk as resource offers to frameworks.
Figure 1.3. Comparing VM-based and container-based application deployments
Figure 1.4. Comparing virtual machines, Docker containers, and Linux cgroups
Figure 1.5. Three applications statically partitioned in a datacenter
Figure 1.6. Three applications running on a Mesos cluster
Figure 1.7. The Mesos architecture consists of one or more masters, slaves, and frameworks.
Chapter 2. Managing datacenter resources with Mesos
Figure 2.1. Components and architecture for a standalone Spark cluster
Figure 2.2. Visualizing two statically partitioned, or siloed, clusters
Figure 2.3. Mesos managing cluster resources for two applications
Figure 2.4. Events that occur when Spark runs tasks on a Mesos cluster
Figure 2.5. The Spark Primes Example framework is consuming cluster resources and running tasks.
Figure 2.6. Files within a Mesos sandbox for a single Spark task
Figure 2.7. The Spark web interface shows the progress of the Spark Primes Example job
Chapter 3. Setting up Mesos
Figure 3.1. Components in a Mesos deployment
Figure 3.2. Mesos masters coordinate leader election using a ZooKeeper ensemble.
Figure 3.3. Mesos masters use the previously configured ZooKeeper ensemble for leader election.
Figure 3.4. Mesos slaves use ZooKeeper to detect���and register with���the leading Mesos master.