diego-design-notes

atures it now includes. The Cloud Foundry Foundation includes Pivotal (my employer), IBM, SAP, Google, DellEMC, VMWare, Cisco, Suse and those are just the fancy tech names. The reason you don't hear about it is that we and our partners have focused on competing for enterprise sales. It's not how you get publicity on HN, but it does mean that PivotalCF -- our commercial distribution -- has the fastest-growing sales of an opensource-based product in history. And sales are still zooming up and to the right. The nice thing is that we and other partners get very broad, specific feedback from customers who are already at massive scale and who expect utter, non-negotiable reliability. We run a public service ourselves (Pivotal Web Services), SAP have HANA Cloud, IBM runs BlueMix. We and other Cloud Foundry contributors have had the benefit of that dogfooding and feedback for longer than any other container-based platform in existence. And it turns out, there are so many things that can go wrong. So many. It's crazy. Lastly, Cloud Foundry teams have massive investments in project automation. This gives us two capabilities: one is that we can roll out complete rebuilds of the whole platform within hours of an upstream CVE patch. Users can then apply these fixes to their platform live, in-place, without any running apps noticing that it has occurred. BOSH[1] will roll out the deployment with canaries, and Diego[2] will relaunch containers as they are reaped during upgrade. The second capability is that we are confident in making very deep, very aggressive changes if it proves necessary, because we have tests upon tests upon mountains of more tests. And again: nobody notices, except that their platform gets faster or becomes reliable under even more extreme circumstances. If I sound like an utterly biased fan, it's because I am an utterly biased fan. I've watched this thing evolve up-close for years. It is amazing. We build installable superpowers. Disclosure: If it's not obvious, I work for Pivotal on Cloud Foundry. [0] https://content.pivotal.io/blog/250k-containers-in-productio... [1] http://bosh.io/ [2] https://github.com/cloudfoundry/diego-design-notes Minor edits for style.

esome, so for those who want a more approachable way to play with Diego, try Lattice[2]. Disclaimer: I work in Pivotal Labs, a division of Pivotal. Pivotal is the major donor of engineering effort to Cloud Foundry. I worked on the Buildpacks team and I've deployed commercial apps to PWS, so I'm obviously a one-eyed fan. [1] https://github.com/cloudfoundry-incubator/diego-design-notes [2] http://lattice.cf/

ttp://lattice.cf/ [2] https://github.com/cloudfoundry-incubator/diego-design-notes [2] https://www.youtube.com/watch?v=1OkmVTFhfLY (an excellent overview) [3] https://www.youtube.com/watch?v=SSxI9eonBVs (an excellent update)

tor/diego-design-notes [2] https://github.com/cloudfoundry-incubator/receptor/blob/mast... [3] http://lattice.cf/

e scheduling. So it seems to be an alternative to the omega-style serialized scheduler of Flynn, or however Fleet handles this. My current understanding is that stampede.io relies on Fleet to handle scheduling, I'm not sure how stock cattle.io gets about it.. It would seem CF still has high-level orchestration(going from staging, then running, etc) and that a comparison between the two systems would be more involved than I had thought(that and cattle.io concerns itself with IaaS as well) :|