[openstack-dev] Scheduler proposal
geoffocallaghan at gmail.com
Sun Oct 11 08:03:30 UTC 2015
On 11/10/2015 6:25 PM, "Clint Byrum" <clint at fewbar.com> wrote:
> Excerpts from Boris Pavlovic's message of 2015-10-11 00:02:39 -0700:
> > 2Everybody,
> > Just curios why we need such complexity.
> > Let's take a look from other side:
> > 1) Information about all hosts (even in case of 100k hosts) will be less
> > then 1 GB
> > 2) Usually servers that runs scheduler service have at least 64GB RAM
> > more on the board
> > 3) math.log(100000) < 12 (binary search per rule)
> > 4) We have less then 20 rules for scheduling
> > 5) Information about hosts is updated every 60 seconds (no updates host
> > dead)
> I'm in, except I think this gets simpler with an intermediary service
> like ZK/Consul to keep track of this 1GB of data and replace the need
> for 6, and changes the implementation of 5 to "updates its record and
> signals its presence".
I have to agree, something like ZK looks like it'd make things simpler and
they're in general well proven technology (esp ZK)
They handle the centralized coordination well and all the hard resiliency
is thrown in.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev