Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project rationale missing from the docs #5

Open
opaugam opened this issue Jan 25, 2016 · 1 comment
Open

Project rationale missing from the docs #5

opaugam opened this issue Jan 25, 2016 · 1 comment

Comments

@opaugam
Copy link

opaugam commented Jan 25, 2016

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 ?

@Amit-PivotalLabs
Copy link

+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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants