diego-design-notes

Oh, we're full of beans. And teaching client developers how we work is literally what Pivotal Labs aims to do. It's probably the first place I've worked that has a high rate of reverse-churn: people leaving to work at startups for the glamour or equity, then deciding they miss Labs and coming back. As for Diego, start with Onsi Fakhouri's keynote at the Cloud Foundry Summit this year[1], then read Amit Gupta's blog post on app placement as an optimisation problem[2], then you might like the Diego Design Notes repo[3]. My main pet peeve with Diego is the confusing, punny names, so it will be confusing at first. [1] https://www.youtube.com/watch?v=1OkmVTFhfLY [2] http://blog.pivotal.io/cloud-foundry-pivotal/products/app-pl... [3] https://github.com/cloudfoundry-incubator/diego-design-notes

Thanks for the reply Darren. I had actually read all of the cattle.io docs and have started poking through the source code. My initial reaction was that I really liked how the orchestration of resources was modelled as a type of state machine. It really clicked for me and I could see how something like this would have value on it's own as a sort of run-deck or the like. It also simplifies the agents.. I can see how creating a .Net agent would be dead simple, and I'm a firm believer that if you're orchestrating on Windows you'll end up wishing you were using .Net eventually if you aren't already. But to the topic at hand, I was a bit confused about how the bidding comes in to play with Diego. After reading the Diego design notes, https://github.com/cloudfoundry-incubator/diego-design-notes , I'm believing this mostly has to do with th