If you look at openstack, they use a message queue for dispatching
(rabbitmq), but I think opennebula has a more elegant and simpler solution.
VMs in large environments can be deployed in batches because there are
several nodes that can deploy them at once, so once in 30 seconds for a
opennebula
, March 07, 2014 4:30 PM
To: users@lists.opennebula.org
Subject: Re: [one-users] scheduler interval
Ok, but I don't understand why it works like a pull model instead of push. Is
so because of a too high load matter or only because the initial architectural
decision was to work like that and now
Hi,
On Thu, Mar 6, 2014 at 1:30 PM, Andrea Gardiman andreagardi...@gmail.com
wrote:
Dear all,
I do not understand the usefulness of the scheduler parameter
SCHED_INTERVAL. Why the scheduler act as a periodic task and have to wait
a fixed period to schedule all the pending jobs instead of to
Ok, but I don't understand why it works like a pull model instead of push.
Is so because of a too high load matter or only because the initial
architectural decision was to work like that and now it is still so?
What would be the drawbacks if were the core,immediately every time a
request arrive,
Dear all,
I do not understand the usefulness of the scheduler parameter
SCHED_INTERVAL. Why the scheduler act as a periodic task and have to wait
a fixed period to schedule all the pending jobs instead of to be
event-driven and schedule immediately a request?
What are the benefits and the
