[one-users] scheduler interval

[Shankhadeep Shome]

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 cluster of 50 hypervisors like in our environment is 6000 VMs
per hour!


On Fri, Mar 7, 2014 at 10:29 AM, Andrea Gardiman
<andreagardiman at gmail.com>wrote:

> 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, tell to the scheduler to schedule that request?
>
> My question comes because I'm working on improving the deployment time of
> VMs for my master thesis, and I understood that I can choose to deploy VMs
> little by little, or immediately as they come but I can't see the cases in
> which deploy VMs little by little would be better that process them
> immediately.
>
> Thanks a lot,
>
>  Andrea Gardiman.
> On Mar 7, 2014 10:58 AM, "Carlos Martín Sánchez" <cmartin at opennebula.org>
> wrote:
>
>> Hi,
>>
>> On Thu, Mar 6, 2014 at 1:30 PM, Andrea Gardiman <andreagardiman at 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 be
>>> event-driven and schedule immediately a request?
>>> What are the benefits and the drawbacks, besides the wait?
>>>
>>> Thanks a lot,
>>>  Andrea Gardiman.
>>>
>>
>> The scheduler is a separate daemon. So it polls the core periodically to
>> look for pending VMs.
>>
>> The usefulness of the SCHED_INTERVAL is that, combined with the other
>> config parameters [1] MAX_DISPATCH and MAX_HOST, allows you to configure a
>> "buffer" to deploy VMs little by little, or immediately as they come.
>>
>> Regards
>>
>> [1] http://docs.opennebula.org/stable/administration/references/schg.html
>>
>> --
>> Carlos Martín, MSc
>> Project Engineer
>> OpenNebula - Flexible Enterprise Cloud Made Simple
>> www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>
>>
>>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140404/46a8730e/attachment.htm>