On 06/19/2013 05:54 PM, Russell Bryant wrote:
> On 06/17/2013 05:09 PM, Brian Elliott wrote:
>>
>> On Jun 17, 2013, at 3:50 PM, Chris Behrens wrote:
>>
>>>
>>> On Jun 17, 2013, at 7:49 AM, Russell Bryant wrote:
>>>
On 06/16/2013 11:25 PM, Dugger, Donald D wrote:
> Looking into the sche
On 06/17/2013 05:09 PM, Brian Elliott wrote:
>
> On Jun 17, 2013, at 3:50 PM, Chris Behrens wrote:
>
>>
>> On Jun 17, 2013, at 7:49 AM, Russell Bryant wrote:
>>
>>> On 06/16/2013 11:25 PM, Dugger, Donald D wrote:
Looking into the scheduler a bit there's an issue of duplicated effort
-
From: Wang, Shane [mailto:shane.w...@intel.com]
Sent: Tuesday, June 18, 2013 6:13 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] Compute node stats sent to the scheduler
Hi,
I am new in this area. I got an idea but didn't know whether that works.
Fanout_cast is ex
Hi,
I am new in this area. I got an idea but didn't know whether that works.
Fanout_cast is expensive and DB could be a burden. Can we maintain the stat
data at nodes, and when and only when a scheduler needs to do any scheduling,
the scheduler proactively to ask nodes their stats?
The assumptio
On Jun 17, 2013, at 3:50 PM, Chris Behrens wrote:
>
> On Jun 17, 2013, at 7:49 AM, Russell Bryant wrote:
>
>> On 06/16/2013 11:25 PM, Dugger, Donald D wrote:
>>> Looking into the scheduler a bit there's an issue of duplicated effort that
>>> is a little puzzling. The database table `compute
On Jun 17, 2013, at 7:49 AM, Russell Bryant wrote:
> On 06/16/2013 11:25 PM, Dugger, Donald D wrote:
>> Looking into the scheduler a bit there's an issue of duplicated effort that
>> is a little puzzling. The database table `compute_nodes' is being updated
>> periodically with data about capa
On 06/16/2013 11:25 PM, Dugger, Donald D wrote:
> Looking into the scheduler a bit there's an issue of duplicated effort that
> is a little puzzling. The database table `compute_nodes' is being updated
> periodically with data about capabilities and resources used (memory, vcpus,
> ...) while a
Looking into the scheduler a bit there's an issue of duplicated effort that is
a little puzzling. The database table `compute_nodes' is being updated
periodically with data about capabilities and resources used (memory, vcpus,
...) while at the same time a periodic RPC call is being made to the
