What if you could have objects with the same name,
BUT you have to "tell" the object what the unique key is.
Then you could use a simplified version of an xpath like naming scheme
(we have been here before).
/clusternodes/cluster[name=freddy]/bla bla
/clusternodes/cluster[name=tom]/bla bla
I do
On Tue, 2009-07-28 at 20:39 -0700, Steven Dake wrote:
> On Wed, 2009-07-29 at 05:34 +0200, Fabio M. Di Nitto wrote:
> > On Wed, 2009-07-29 at 09:03 +1200, Angus Salkeld wrote:
> > > Why do you need this?
> > >
> > > I know the config file is set out like this, but why force the requirement
> > > o
On Wed, 2009-07-29 at 05:34 +0200, Fabio M. Di Nitto wrote:
> On Wed, 2009-07-29 at 09:03 +1200, Angus Salkeld wrote:
> > Why do you need this?
> >
> > I know the config file is set out like this, but why force the requirement
> > onto objdb?
> >
> > -Angus
> >
> > On Wed, Jul 29, 2009 at 8:07 A
On Wed, 2009-07-29 at 09:03 +1200, Angus Salkeld wrote:
> Why do you need this?
>
> I know the config file is set out like this, but why force the requirement
> onto objdb?
>
> -Angus
>
> On Wed, Jul 29, 2009 at 8:07 AM, Fabio M. Di Nitto
> wrote:
> > On Wed, 2009-07-29 at 07:30 +1200, Angus Sa
On Tue, 2009-07-28 at 15:27 -0700, Steven Dake wrote:
> On Wed, 2009-07-29 at 07:30 +1200, Angus Salkeld wrote:
> > Hi
> >
> > Here is a first attempt at an easier to use API for objdb.
> >
> > 1) remove the need for parent_handles.
>
> big improvement
>
> > 2) Each object/key must have a uniqu
On Wed, 2009-07-29 at 10:29 +1200, angus salkeld wrote:
> On Tue, 2009-07-28 at 14:30 -0700, Steven Dake wrote:
> > On Wed, 2009-07-29 at 09:03 +1200, Angus Salkeld wrote:
> > > Why do you need this?
> > >
> > > I know the config file is set out like this, but why force the requirement
> > > onto
On Wed, 2009-07-29 at 07:30 +1200, Angus Salkeld wrote:
> Hi
>
> Here is a first attempt at an easier to use API for objdb.
>
> 1) remove the need for parent_handles.
big improvement
> 2) Each object/key must have a unique name (as a string)
> 2.1) So no child objects named the same (service, l
On Tue, 2009-07-28 at 14:30 -0700, Steven Dake wrote:
> On Wed, 2009-07-29 at 09:03 +1200, Angus Salkeld wrote:
> > Why do you need this?
> >
> > I know the config file is set out like this, but why force the requirement
> > onto objdb?
> >
> We could always change the config file to remove this
On Wed, 2009-07-29 at 09:03 +1200, Angus Salkeld wrote:
> Why do you need this?
>
> I know the config file is set out like this, but why force the requirement
> onto objdb?
>
We could always change the config file to remove this requirement, but I
wonder about the case of something like using thi
Why do you need this?
I know the config file is set out like this, but why force the requirement
onto objdb?
-Angus
On Wed, Jul 29, 2009 at 8:07 AM, Fabio M. Di Nitto wrote:
> On Wed, 2009-07-29 at 07:30 +1200, Angus Salkeld wrote:
>> Hi
>>
>> Here is a first attempt at an easier to use API for
On Wed, 2009-07-29 at 07:30 +1200, Angus Salkeld wrote:
> Hi
>
> Here is a first attempt at an easier to use API for objdb.
> 2) Each object/key must have a unique name (as a string)
> 2.1) So no child objects named the same (service, logging,...)
This breaks current requirements from the objdb
Hi
Here is a first attempt at an easier to use API for objdb.
1) remove the need for parent_handles.
2) Each object/key must have a unique name (as a string)
2.1) So no child objects named the same (service, logging,...)
3) support persistent & runtime keys to better support IMM
4) assume all obj
good for trunk
regards
-steve
On Tue, 2009-07-28 at 09:30 +0200, Fabio M. Di Nitto wrote:
> Hi Steven,
>
> this patch updates the spec file to use macros consistently across the
> board and fix a major issue by including /var/lib/corosync in the rpm
> (taking ownership of the directory).
>
> Wi
autogen.sh should detect the tag version or honor that which is done in
the tagging script. Have you looked at how the tagging script sets the
version variable?
Regards
-steve
On Tue, 2009-07-28 at 12:17 +0200, Jan Friesse wrote:
> See SUBJ and Patch.
>
> Regards,
> Honza
> ___
Rather ignore previous mail. It's not working idea. First patch is
"correct".
Regards,
Honza
Jan Friesse wrote:
> Fabbio pointed to better solution of this problem. Patch attached.
>
> Regards,
> Honza
>
> Jan Friesse wrote:
>> See SUBJ and Patch.
>>
>> Regards,
>> Honza
>>
>>
>>
What happens if you're building from a tar-ball?
On Tue, Jul 28, 2009 at 2:50 PM, Jan Friesse wrote:
> Fabbio pointed to better solution of this problem. Patch attached.
>
> Regards,
> Honza
>
> Jan Friesse wrote:
>> See SUBJ and Patch.
>>
>> Regards,
>> Honza
>>
>>
>> -
Fabbio pointed to better solution of this problem. Patch attached.
Regards,
Honza
Jan Friesse wrote:
> See SUBJ and Patch.
>
> Regards,
> Honza
>
>
>
>
> ___
> Openais mail
See SUBJ and Patch.
Regards,
Honza
commit 01cbe593996c01af1c5fa1e507954f27a9abd106
Author: Jan Friesse
Date: Tue Jul 28 11:56:15 2009 +0200
Added support for -v (version) feature
This can be usefull for easier way to get informations
of the corosync version from users. Versi
this time with patch... :)
On Tue, 2009-07-28 at 09:39 +0200, Fabio M. Di Nitto wrote:
> same as the corosync one... this is only a cleanup patch to
> keep in sync with corosync. No real bugs are fixed.
>
> Fabio
>
> ___
> Openais mailing list
> Openai
same as the corosync one... this is only a cleanup patch to
keep in sync with corosync. No real bugs are fixed.
Fabio
___
Openais mailing list
Openais@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/openais
Hi Steven,
this patch updates the spec file to use macros consistently across the
board and fix a major issue by including /var/lib/corosync in the rpm
(taking ownership of the directory).
Without this fix, in a super clean corosync installation, corosync will
fail to start because of the lack of
21 matches
Mail list logo
