Missing tools

_______________________________________________
Pacemaker mailing list
Pacemaker@...
http://list.clusterlabs.org/mailman/listinfo/pacemaker

Re: Missing tools

Hi,

On Wed, Oct 01, 2008 at 02:05:28PM +0100, Szymon Bakowski wrote:
> Hi Guys,
> 
> Just a quick question:
> 
> I do have installed pacemaker-0.6.5-2.2 and it seems that some commands are
> missing from the packaged (or I missed something during installation):
> namely:
> 
> hb_addnod
> hb_delnode

These two belong to heartbeat. Pacemaker is not heartbeat. You
should install heartbeat-2.99.

> crm_shadow

This is available as of version 0.7.

> Is there some particular reason I am missing on these tools ? (old version
> of Pacemaker ?? I am using pacemaker Configuration guide 1.0 by Andrew
> Beekhof)

Conf guide 1.0 is for the future v1.0, currently (as test
release) 0.7.x

Thanks,

Dejan

> Cheers
> Simon

> _______________________________________________
> Pacemaker mailing list
> Pacemaker@...
> http://list.clusterlabs.org/mailman/listinfo/pacemaker

Re: Missing tools

_______________________________________________
Pacemaker mailing list
Pacemaker@...
http://list.clusterlabs.org/mailman/listinfo/pacemaker

Re:

sungho.kim.zd@...

--

-- 
---
Sungho KIM
Linux Technology Center
Hitachi, Ltd., Systems Development Laboratory
E-mail: sungho.kim.zd@...

Order Constraint for: stop rscA only when rscB is running ?

Hi,

I have a Heartbeat 2.1.3 two-node cluster and I wonder if there is a way to 
create constraints that work like that:

* Two resources (rscA and rscB) of class "heartbeat" that should run together 
on one node .... simple advisory colocation constraint

<rsc_colocation id="rscA-colocated-with-rscB" 
	from="rscA" to="rscB" 
	score="1" symmetrical="true"/>

* When doing maintenance on one node I put the node into standby mode and want 
rscA only stop and migrate away if rscB is already up and running on the 
other node and vice versa because  there must always run at least one of 
these resources in the cluster.

I added two order_constraints and tested it with ptest on an adapted live cib  
but they seem to produce a loop:

<rsc_order id="stop-rscA-only-after-rscB-start" 
	from="service_rscA" action="stop" 
	type="after" 
	to="service_rscB" to_action="start" 
	symmetrical="false" score="0"/>

<rsc_order id="stop-rscB-only-after-rscA-start" 
	from="service_rscB" action="stop" 
	type="after" 
	to="service_rscA" to_action="start" 
	symmetrical="false" score="0"/>

Is there a way to get the requested behavior or is a manual resource after 
resource migration the only way to achieve this?

Regards,
Andreas

-- 
: Andreas Kurz					 
: LINBIT | Your Way to High Availability
: Tel +43-1-8178292-64, Fax +43-1-8178292-82
:
: http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

This e-mail is solely for use by the intended recipient(s). Information
contained in this e-mail and its attachments may be confidential,
privileged or copyrighted. If you are not the intended recipient you are
hereby formally notified that any use, copying, disclosure or
distribution of the contents of this e-mail, in whole or in part, is
prohibited. Also please notify immediately the sender by return e-mail
and delete this e-mail from your system. Thank you for your co-operation.

_______________________________________________
Pacemaker mailing list
Pacemaker@...
http://list.clusterlabs.org/mailman/listinfo/pacemaker

How to get supported meta attributes?

Hi Andrew,
Do we have a convenient way to get a list of supported meta attributes
and available values for a specified type of object? If so, we could
keep it updated automatically in GUI insdead of do it manually

Regards,
--

-- 
Yan Gao
China R&D Software Engineer
ygao@...

Novell, Inc.
SUSE® Linux Enterprise 10
Your Linux is ready
http://www.novell.com/linux

Re: How to get supported meta attributes?

On Oct 6, 2008, at 6:46 AM, Yan Gao wrote:

> Hi Andrew,
> Do we have a convenient way to get a list of supported meta attributes
> and available values for a specified type of object?

No.  It is documented in the configuration pdf though.
We previously discussed changing the configuration so that it was  
possible to validate the meta attributes, but in the end decided  
against it.

> If so, we could
> keep it updated automatically in GUI insdead of do it manually

Re: How to get supported meta attributes?

On Mon, 2008-10-06 at 07:56 +0200, Andrew Beekhof wrote:
> On Oct 6, 2008, at 6:46 AM, Yan Gao wrote:
> 
> > Hi Andrew,
> > Do we have a convenient way to get a list of supported meta attributes
> > and available values for a specified type of object?
> 
> No.  It is documented in the configuration pdf though.
> We previously discussed changing the configuration so that it was  
> possible to validate the meta attributes, but in the end decided  
> against it.
Maybe we could use meta-data instead of schemas to define them ?

> > If so, we could
> > keep it updated automatically in GUI insdead of do it manually
> 
> 
> _______________________________________________
> Pacemaker mailing list
> Pacemaker@...
> http://list.clusterlabs.org/mailman/listinfo/pacemaker
--

-- 
Yan Gao
China R&D Software Engineer
ygao@...

Novell, Inc.
SUSE® Linux Enterprise 10
Your Linux is ready
http://www.novell.com/linux

Re: How to get supported meta attributes?

On Oct 6, 2008, at 8:24 AM, Yan Gao wrote:

> On Mon, 2008-10-06 at 07:56 +0200, Andrew Beekhof wrote:
>> On Oct 6, 2008, at 6:46 AM, Yan Gao wrote:
>>
>>> Hi Andrew,
>>> Do we have a convenient way to get a list of supported meta  
>>> attributes
>>> and available values for a specified type of object?
>>
>> No.  It is documented in the configuration pdf though.
>> We previously discussed changing the configuration so that it was
>> possible to validate the meta attributes, but in the end decided
>> against it.
> Maybe we could use meta-data instead of schemas to define them ?

That just creates one more place to maintain it I'm afraid.
The PE doesn't need it and the CIB wouldn't be using either (since  
validation is done with schemas).

>>> If so, we could
>>> keep it updated automatically in GUI insdead of do it manually
>>
>>
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker@...
>> http://list.clusterlabs.org/mailman/listinfo/pacemaker
> -- 
> Yan Gao
> China R&D Software Engineer
> ygao@...
>
> Novell, Inc.
> SUSE® Linux Enterprise 10
> Your Linux is ready
> http://www.novell.com/linux
>
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker@...
> http://list.clusterlabs.org/mailman/listinfo/pacemaker

Re: Pacemaker 0.7.3: How to use pingd clone resource and constraints

On Fri, Sep 26, 2008 at 22:15, Andrew Beekhof <beekhof@...> wrote:
> On Fri, Sep 26, 2008 at 16:42, Andrew Beekhof <beekhof@...> wrote:
>> On Fri, Sep 26, 2008 at 09:37, Andrew Beekhof <beekhof@...> wrote:
>>> Most likely you've found a bug 
>>> Would you be able to create a bugzilla entry for this?
>>> On Sep 25, 2008, at 9:33 PM, Bruno Voigt wrote:
>>>
>>> Wow.. these warnings are even shown for 127.0.0.1 ?!
>>> Do I need to finetune the IP stack options somewhere like in sysctl.conf
>>> to have these warnings of pingd fixed?
>>
>> I looked into this, and for localhost the cause is me not filtering
>> out the ICMP_ECHO packet.
>> I'll patch that now.
>>
>> For remote hosts, there seems to be something else going on
>
> In short - pingd in 0.7 is/was completely broken on linux (but worked
> great on Darwin).
> Sorry :(
>
> The good news is that I have it basically functioning properly now - I
> just need to clean up the patch before I commit (which I'll do over
> the weekend).
>

Would you be able to verify that pingd in the new packages (0.7.3-2.1)
behaves properly?

Btw. You can also run it from the command line (with no cluster
present) by supplying the -U option.
Instead of trying to update attrd, it will instead output the message
it would have sent.