On Wed, 19 Feb 2014 11:57:29 +1100
Andrew Beekhof wrote:
> It appears Yan did this on purpose.
> The reason would likely be that this set is for use in a location
> constraint (not ordering or colocation). And in particular, it is
> creating a fake set for resources using the same template - so t
On 19 Feb 2014, at 10:48 am, Kristoffer Grönlund wrote:
> Hi everyone,
>
> On Mon, 17 Feb 2014 10:54:29 +0900 (JST)
> renayama19661...@ybb.ne.jp wrote:
>
>> Hi Andrew,
>>
>> I found your correction.
>>
>> https://github.com/beekhof/pacemaker/commit/37ff51a0edba208e6240e812936717fffc941a41
>>
Hi everyone,
On Mon, 17 Feb 2014 10:54:29 +0900 (JST)
renayama19661...@ybb.ne.jp wrote:
> Hi Andrew,
>
> I found your correction.
>
> https://github.com/beekhof/pacemaker/commit/37ff51a0edba208e6240e812936717fffc941a41
>
> Many Thanks!
> Hideo Yamauchi.
>
> --- On Wed, 2014/2/12, renayama1966
Hi Andrew,
I found your correction.
https://github.com/beekhof/pacemaker/commit/37ff51a0edba208e6240e812936717fffc941a41
Many Thanks!
Hideo Yamauchi.
--- On Wed, 2014/2/12, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> There is difference in two between handling of "sequential" of "resouc
Hi All,
There is difference in two between handling of "sequential" of "resouce_set" of
colocation.
Is either one not a mistake?
static gboolean
unpack_colocation_set(xmlNode * set, int score, pe_working_set_t * data_set)
{
xmlNode *xml_rsc = NULL;
resource_t *w
