Open Sourcing Peloton, Uber’s Unified Resource Scheduler
1–10 of 77 posts
Re: Open Sourcing Peloton, Uber’s Unified Resource Scheduler
#2My first reaction was "this just sounds like Mesos?". And it's cited in their page (which on first read I thought meant they were trying to act as a single pane of glass for Mesos/k8s/etc.):
In the OP blog post though, they assert "to our knowledge, there is no other open source scheduler which combines all types of workloads for web-scale companies like Uber."
And then, when you dig...it's just Mesos. They built a framework for Mesos. So, that's cool. But man, the puff piecery borders on dishonesty. I mean--Singularity has existed, and is implemented at very large scales, for a while. I'm sure Peloton is a fine scheduler, but there's a lot of huffing-one's-own-farts in the documentation here.
Re: Open Sourcing Peloton, Uber’s Unified Resource Scheduler
#3My first reaction was "this just sounds like Mesos?". And it's cited in their page (which on first read I thought meant they were trying to act as a single pane of glass for Mesos/k8s/etc.): https://eng.uber.com/peloton/ In the OP blog post though, they assert "to our knowledge, there is no other open source scheduler which combines all types of workloads for web-scale companies like Uber." And then, when you dig...i…
I second you
Re: Open Sourcing Peloton, Uber’s Unified Resource Scheduler
#4My first reaction was "this just sounds like Mesos?". And it's cited in their page (which on first read I thought meant they were trying to act as a single pane of glass for Mesos/k8s/etc.): https://eng.uber.com/peloton/ In the OP blog post though, they assert "to our knowledge, there is no other open source scheduler which combines all types of workloads for web-scale companies like Uber." And then, when you dig...i…
very early on in the article there is a "Alternate cluster schedulers" section which cites mesos.
Re: Open Sourcing Peloton, Uber’s Unified Resource Scheduler
#5Immediate reaction: Well, now there's Peloton, the fitness tech company, Peloton, the self-driving truck caravan company, and Peloton, the cluster scheduler...
Re: Open Sourcing Peloton, Uber’s Unified Resource Scheduler
#6My first reaction was "this just sounds like Mesos?". And it's cited in their page (which on first read I thought meant they were trying to act as a single pane of glass for Mesos/k8s/etc.): https://eng.uber.com/peloton/ In the OP blog post though, they assert "to our knowledge, there is no other open source scheduler which combines all types of workloads for web-scale companies like Uber." And then, when you dig...i…
very early on in the article there is a "Alternate cluster schedulers" section which cites mesos.
I think eropple's point might be that it's listed as an alternate without a (or much) difference.
Re: Open Sourcing Peloton, Uber’s Unified Resource Scheduler
#7Peloton should make a framework called Uber in response.
Re: Open Sourcing Peloton, Uber’s Unified Resource Scheduler
#8Immediate reaction: Well, now there's Peloton, the fitness tech company, Peloton, the self-driving truck caravan company, and Peloton, the cluster scheduler...
And Peleton the open source RDBMS.
Re: Open Sourcing Peloton, Uber’s Unified Resource Scheduler
#9At first glance I thought the "resources" here might be Uber drivers, which would be interesting.
Is this thing/Apache Mesos abstract enough to allow for such a use?
Re: Open Sourcing Peloton, Uber’s Unified Resource Scheduler
#10Immediate reaction: Well, now there's Peloton, the fitness tech company, Peloton, the self-driving truck caravan company, and Peloton, the cluster scheduler...
Where do all these names come from? Is it Latin or Greek or something?