cloudfoundry-mesos icon indicating copy to clipboard operation
cloudfoundry-mesos copied to clipboard

Project rationale missing from the docs

Open opaugam opened this issue 10 years ago • 1 comments

Great job !

I couldn't find in the documentation + links provided a good overview of the rationale for this effort. In other words, why would I want to replace the auction process from Diego by Mesos offers? Are we talking about better performance, more features, etc. ? What in your particular case led you to bridge between both systems and host the cells into a docker container controlled by Mesos?

Do you have any insight to share ?

opaugam avatar Jan 25 '16 14:01 opaugam

+1.

I've read a few motivations, in the README and press releases, namely:

  • ability to use Diego alongside other frameworks so that mesos can manage resources across the whole datacenter efficiently
  • ability to scale Diego to run a large number of workloads

I'm curious about the latter. In particular, how is performance at scale actually being assessed?

Amit-PivotalLabs avatar Jan 26 '16 01:01 Amit-PivotalLabs