Kubernetes Borg/Omega history topic 9: Scheduling constraints. I have volumes more to write about configuration, but will move on with history topics for now. Borg's set of constraints grew organically over time. It started with just required memory, before multicore and NPTL
-
Show this thread
-
-
Replying to @mikejk8s
Thanks. Many more topics to go, even in just resource management: PodDisruptionBudget, QoS, oversubscription, vertical autoscaling, ...
1 reply 0 retweets 9 likes -
Replying to @bgrant0607
These are like a trip down memory lane for me - love seeing this summarized and so clearly articulated. So much goodness still to do :)
1 reply 0 retweets 6 likes -
Replying to @smarterclayton
I was thinking about working with you and Derek when I wrote parts of this thread :-). I try to keep them concise, for the most part, since there is so much ground to cover
1 reply 0 retweets 2 likes -
Replying to @bgrant0607 @smarterclayton
Please continue, they are fantastic. From a SE that loves sysadm and wish we had kubernetes 20 years ago. :-)
1 reply 0 retweets 0 likes
I'm spoiled :-). I've been working with parallel and distributed computing systems since 1992: MasPar, Meiko CS-2, Intel Paragon, BBN Butterfly, PVM, MPI, LSF ... and later working on PeakStream, Borg, Omega, Google Cloud, Kubernetes.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.