On Fri, Oct 30, 2009 at 12:41 PM, Yan Gao wrote:
> Hi Andrew and Lars,
> The attachment is the first try to implement "Resource capacity limit"
> which is issued by Lars from:
> https://fate.novell.com/303384
>
> Description:
> We need a mechanism for the PE to take resource weight into account to
Hi Andrew,
I added utilization support for crm_attribute and crm_resource.
Attached the patch. Please let me know if you have any comments or
suggestions on that.
BTW, LF#2351 has been fixed. Attached the patch there:
http://developerbugs.linux-foundation.org/show_bug.cgi?id=2351
Thanks,
Yan
--
Hi Andrew,
Yan Gao wrote:
> On 12/10/09 12:56, Yan Gao wrote:
>> Hi Andrew,
>> Attached the hg export patch against the devel branch for that. Hope
>> that's easier to be merged:-)
> And the patch including the test cases.
The *.score files were adopted the wrong file name extension rather than
"s
Andrew Beekhof wrote:
> On Thu, Dec 10, 2009 at 9:52 AM, Yan Gao wrote:
>> On 12/10/09 12:56, Yan Gao wrote:
>>> Hi Andrew,
>>> Attached the hg export patch against the devel branch for that. Hope
>>> that's easier to be merged:-)
>> And the patch including the test cases.
>
> Done. Thanks for y
On Thu, Dec 10, 2009 at 9:52 AM, Yan Gao wrote:
> On 12/10/09 12:56, Yan Gao wrote:
>> Hi Andrew,
>> Attached the hg export patch against the devel branch for that. Hope
>> that's easier to be merged:-)
> And the patch including the test cases.
Done. Thanks for your efforts!
___
On 12/10/09 12:56, Yan Gao wrote:
> Hi Andrew,
> Attached the hg export patch against the devel branch for that. Hope
> that's easier to be merged:-)
And the patch including the test cases.
Thanks,
Yan
--
y...@novell.com
Software Engineer
China Server Team, OPS Engineering
Novell, Inc.
Making
Hi Andrew,
Attached the hg export patch against the devel branch for that. Hope
that's easier to be merged:-)
Thanks,
Yan
--
y...@novell.com
Software Engineer
China Server Team, OPS Engineering
Novell, Inc.
Making IT Work As One™
# HG changeset patch
# User Yan Gao
# Date 1260419866 -28800
#
Hi Andrew,
On 11/20/09 04:10, Andrew Beekhof wrote:
> Btw. You're still missing some test cases ;-)
Oh, right:-) I created some. Hope I created them in the correct way.
Sorry for so many attachments...
Thanks,
Yan
--
y...@novell.com
Software Engineer
China Server Team, OPS Engineering
Novell,
Btw. You're still missing some test cases ;-)
On Fri, Nov 13, 2009 at 8:23 AM, Yan Gao wrote:
> Hi Andrew, Lars,
>
> Andrew Beekhof wrote:
>> I'd like to see the while-block from native_color() be a function that
>> is called from native_assign_node().
> It seems to be too late to filter out the
On 2009-11-13T15:23:20, Yan Gao wrote:
> Minimal:
> Consider the utilization of nodes and resources. While if a resource has
> the same score for several available nodes, do _not_ balance the load.
> That implies that the resources will be concentrated to minimal number of
> nodes.
>
> Balance
On Thu, Nov 12, 2009 at 11:58 PM, Lars Marowsky-Bree wrote:
> On 2009-11-12T14:53:24, Andrew Beekhof wrote:
>
>> At this point in time, I can't see us going back to the way heartbeat
>> releases were done.
>> If there was a single thing that I'd credit Pacemaker's current
>> reliability to, it wo
On Fri, Nov 13, 2009 at 8:23 AM, Yan Gao wrote:
> Hi Andrew, Lars,
>
> Andrew Beekhof wrote:
>> I'd like to see the while-block from native_color() be a function that
>> is called from native_assign_node().
> It seems to be too late to filter out the nodes without enough capacity from
> native_ass
Hi Andrew, Lars,
Andrew Beekhof wrote:
> I'd like to see the while-block from native_color() be a function that
> is called from native_assign_node().
It seems to be too late to filter out the nodes without enough capacity from
native_assign_node(). I wrote a have_enough_capacity() function which
On Thu, 2009-11-12 at 14:53 +0100, Andrew Beekhof wrote:
> On Wed, Nov 11, 2009 at 1:36 PM, Lars Marowsky-Bree wrote:
> > On 2009-11-05T14:45:36, Andrew Beekhof wrote:
> >
> >> Lastly, I would really like to defer this for 1.2
> >> I know I've bent the rules a bit for 1.0 in the past, but its rea
On 2009-11-12T14:53:24, Andrew Beekhof wrote:
> At this point in time, I can't see us going back to the way heartbeat
> releases were done.
> If there was a single thing that I'd credit Pacemaker's current
> reliability to, it would be our release strategy.
Well, exactly, and that's what pacemak
On Wed, Nov 11, 2009 at 1:36 PM, Lars Marowsky-Bree wrote:
> On 2009-11-05T14:45:36, Andrew Beekhof wrote:
>
>> Lastly, I would really like to defer this for 1.2
>> I know I've bent the rules a bit for 1.0 in the past, but its really
>> late in the game now.
>
> Personally, I think the Linux kern
On Wed, Nov 11, 2009 at 1:42 PM, Lars Marowsky-Bree wrote:
> On 2009-11-06T12:45:17, Andrew Beekhof wrote:
>
>> And instead of a limit-utilization option, we'd have
>> placement-strategy=(default|utilization|minimal)
>>
>> Default ::= what we do now
>> Utilization ::= what you've implemented
>
>
On 2009-11-09T10:52:03, Michael Schwartzkopff wrote:
> I just think it would be cool solution to make the cluster itself
> doing the work if condfigured to do so. So the CRM (or the RAs) should
> have the abaility to monitor the resource consumption of resources
> dynamically. This automatism wou
On 2009-11-06T12:45:17, Andrew Beekhof wrote:
> And instead of a limit-utilization option, we'd have
> placement-strategy=(default|utilization|minimal)
>
> Default ::= what we do now
> Utilization ::= what you've implemented
These two are obvious, since we can already do them with existing code
On 2009-11-05T14:45:36, Andrew Beekhof wrote:
> Lastly, I would really like to defer this for 1.2
> I know I've bent the rules a bit for 1.0 in the past, but its really
> late in the game now.
Personally, I think the Linux kernel model works really well. ie, no
"major releases" any more, but bug
Am Freitag, 6. November 2009 08:49:06 schrieb Andrew Beekhof:
> On Fri, Nov 6, 2009 at 8:31 AM, Michael Schwartzkopff
wrote:
> > Am Donnerstag, 5. November 2009 21:37:23 schrieb Andrew Beekhof:
> >> On Thu, Nov 5, 2009 at 8:50 PM, Michael Schwartzkopff
> >>
> >
> > wrote:
> >> > Hi,
> >> >
> >>
Hi,
Andrew Beekhof wrote:
>
> I've been thinking about this more and while this will work, I think
> we can make it better.
>
> I'd like to see the while-block from native_color() be a function that
> is called from native_assign_node().
Okay.
> And instead of a limit-utilization option, we'd ha
Hi,
On Thu, Nov 05, 2009 at 07:28:16PM +0100, Andrew Beekhof wrote:
> On Thu, Nov 5, 2009 at 5:25 PM, Dejan Muhamedagic wrote:
> > Hi,
> >> Which reminds me, I need to get devel sorted out...
> >
> > While you're at it, perhaps it would be good to rethink the
> > release policy. For me in particu
On Fri, Nov 6, 2009 at 8:31 AM, Michael Schwartzkopff wrote:
> Am Donnerstag, 5. November 2009 21:37:23 schrieb Andrew Beekhof:
>> On Thu, Nov 5, 2009 at 8:50 PM, Michael Schwartzkopff
> wrote:
>> > Hi,
>> >
>> > on the list was a discussion about resource capacity limits. Yan Gao also
>> > imple
Am Donnerstag, 5. November 2009 21:37:23 schrieb Andrew Beekhof:
> On Thu, Nov 5, 2009 at 8:50 PM, Michael Schwartzkopff
wrote:
> > Hi,
> >
> > on the list was a discussion about resource capacity limits. Yan Gao also
> > implemented it.
> >
> > As far as I understood the discussion the solution
Hi Andrew,
Andrew Beekhof wrote:
> On Tue, Nov 3, 2009 at 12:15 PM, Yan Gao wrote:
>> Hi again,
>>
>> Yan Gao wrote:
>>
>> XML sample:
>> ..
>>
>>
>>
>>
>>
>>
>>
>>
>> ..
>>
>>
>>
>>
>>
>>
>>
Hi Andrew,
Thanks for your reply!
Andrew Beekhof wrote:
> On Wed, Nov 4, 2009 at 5:41 PM, Lars Marowsky-Bree wrote:
>> On 2009-11-03T19:15:59, Yan Gao wrote:
>>
>>> XML sample:
>>> ..
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ..
>>>
On Thu, Nov 5, 2009 at 8:50 PM, Michael Schwartzkopff wrote:
> Hi,
>
> on the list was a discussion about resource capacity limits. Yan Gao also
> implemented it.
>
> As far as I understood the discussion the solution is to attach nodes and
> resources capacity limits. Resources are distributed on
Hi,
on the list was a discussion about resource capacity limits. Yan Gao also
implemented it.
As far as I understood the discussion the solution is to attach nodes and
resources capacity limits. Resources are distributed on the nodes of a cluster
according to its capacatiy needs. They would be
On 2009-11-03T19:15:59, Yan Gao wrote:
> XML sample:
> ..
>
>
>
>
>
>
>
>
> ..
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ..
>
Hi again,
Yan Gao wrote:
> Hi Lars,
> Thanks for the great suggestions!
>
> Lars Marowsky-Bree wrote:
>> On 2009-10-30T19:41:35, Yan Gao wrote:
>>> Configuration example:
>>>
>>> node yingying \
>>> attributes capacity="100"
>>> primitive dummy0 ocf:heartbeat:Dummy \
>>> meta weight="90"
Hi Lars,
Thanks for the great suggestions!
Lars Marowsky-Bree wrote:
> On 2009-10-30T19:41:35, Yan Gao wrote:
>>
>> Configuration example:
>>
>> node yingying \
>> attributes capacity="100"
>> primitive dummy0 ocf:heartbeat:Dummy \
>> meta weight="90" priority="2"
>> primitive dummy1 oc
hi,
On 10/30/2009 01:20 PM, Lars Marowsky-Bree wrote:
> I think this is a two phase feature for the PE: The first phase is what
> you propose - make sure we do not overload any given node, basically
> implementing hard limits.
>
> The second phase would be for the PE to actually try to "optimize"
On 2009-10-30T19:41:35, Yan Gao wrote:
Hi Yan Gao,
excellent!
Before reviewing the code, lets review the interface/configuration
though.
> User case:
> Xen guests have memory requirements; nodes cannot host more guests than
> the node has physical memory installed.
>
>
> Configuration exampl
Hi Andrew and Lars,
The attachment is the first try to implement "Resource capacity limit"
which is issued by Lars from:
https://fate.novell.com/303384
Description:
We need a mechanism for the PE to take resource weight into account to
prevent nodes from being overloaded.
Resources would require
35 matches
Mail list logo
