date:20110531

Re: [Pacemaker] Bug in compiling pacemaker-pygui: CRM_DAEMON_DIR not defined

2011-05-31 Thread Gao,Yan

On 05/31/11 04:13, Andrew Beekhof wrote:
 On Mon, May 30, 2011 at 2:23 PM, Gao,Yan y...@novell.com wrote:
 On 05/30/11 17:31, Andrew Beekhof wrote:
 It used to be in crm_config.h but I had to remove it because it
 interfered with multilib (not that I've ever seen anyone make use of
 that particular feature).
 Mgmtd uses it for invoking pengine/crmd to retrieve the metadata. Is
 there a replacement of it? I don't seem to find one.
 
 You can now use pkg-config. We supply the .pc files
Fine! How about to install the pc files like the attached?

Regards,
  Yan
-- 
Gao,Yan y...@novell.com
Software Engineer
China Server Team, SUSE.
# HG changeset patch
# User Gao,Yan y...@novell.com
# Date 1306831076 -28800
# Node ID c86cb93c5a57c1f507a21be69d24fd28dee85397
# Parent  e872eeb39a5f6e1fdb57c3108551a5353648c4f4
Low: Build: Install pkg-config files

diff -r e872eeb39a5f -r c86cb93c5a57 lib/Makefile.am
--- a/lib/Makefile.am	Fri May 06 11:01:44 2011 +0200
+++ b/lib/Makefile.am	Tue May 31 16:37:56 2011 +0800
@@ -17,6 +17,27 @@
 #
 MAINTAINERCLEANFILES= Makefile.in
 
+EXTRA_DIST		= pcmk.pc.in pcmk-cib.pc.in pcmk-pe.pc.in
+
+LIBS			= cib pe
+
+target_LIBS		= $(LIBS:%=pcmk-%.pc)
+
+target_PACKAGE		= pcmk.pc
+
+all-local: $(target_LIBS) $(target_PACKAGE)
+
+install-exec-local: $(target_LIBS) $(target_PACKAGE)
+	$(INSTALL) -d $(DESTDIR)/$(libdir)/pkgconfig
+	$(INSTALL) -m 644 $(target_LIBS) $(target_PACKAGE) $(DESTDIR)/$(libdir)/pkgconfig
+
+uninstall-local:
+	cd $(DESTDIR)/$(libdir)/pkgconfig  rm -f $(target_LIBS) $(target_PACKAGE)
+	rmdir $(DESTDIR)/$(libdir)/pkgconfig 2 /dev/null || :
+
+clean-local:
+	rm -f *.pc
+
 ## Subdirectories...
 SUBDIRS	= common pengine transition cib fencing plugins
 DIST_SUBDIRS =  $(SUBDIRS) ais
diff -r e872eeb39a5f -r c86cb93c5a57 pacemaker.spec.in
--- a/pacemaker.spec.in	Fri May 06 11:01:44 2011 +0200
+++ b/pacemaker.spec.in	Tue May 31 16:37:56 2011 +0800
@@ -158,6 +158,7 @@ License:	GPLv2+ and LGPLv2+
 Summary:	Pacemaker development package
 Group:		Development/Libraries
 Requires:	pacemaker-libs = %{version}-%{release}
+Requires:	pkgconfig
 Requires:	cluster-glue-libs-devel
 Requires:	libxml2-devel libxslt-devel bzip2-devel glib2-devel 
 %if %{with ais}
@@ -374,6 +375,7 @@ fi
 %dir %{_var}/lib/pacemaker
 %{_var}/lib/pacemaker
 %endif
+%{_libdir}/pkgconfig/*.pc
 %doc COPYING.LIB
 %doc AUTHORS
 
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] Node removal in corosync-based cluster

2011-05-31 Thread Dejan Muhamedagic

On Mon, May 30, 2011 at 05:27:41PM +0300, Vladislav Bogdanov wrote:
 Hi,
 
 30.05.2011 17:12, Dejan Muhamedagic wrote:
  Hi,
  
  On Sun, May 29, 2011 at 11:58:17PM +0300, Vladislav Bogdanov wrote:
  Hi all.
 
  I've got a task to remove some nodes from cluster to save some power and
  found that it is not sufficient to follow
  http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-node-delete.html#s-del-ais
  
  Did you try just crm node delete ...? That should do whatever's
  necessary to remove a node (on which pacemaker be down).
 
 What extra commands does it run comparing to Pacemaker Explained?

I must say that I don't know, easy to check in the code, but it
should do whatever's necessary. If it doesn't then we need to fix
it. The idea is that users don't need to know about cibadmin,
crm_node, and such stuff.

Thanks,

Dejan

  I can vaguely recall this case, but cannot remember anymore what
  was the outcome.
  
  Thanks,
  
  Dejan
  
  After pacemaker is then restarted on any another remaining node, removed
  node comes back in a CIB (with OFFLINE status). Even removal of that
  node from corosync's objdb with
  corosync-objctl -d runtime.totem.pg.mrp.srp.members.COROSYNC_ID
  does not help.
 
  The only way to completely remove node I found is to stop pacemaker on
  all cluster nodes and start it again then. So there should be some
  'ghost' data in a running pacemaker instance which is not deleted after
  removal of node data and status from a CIB.
 
  I hope this could be easily fixed, just a note that it does not fully
  work now (1.1.5 with some patches from both 1.1 and devel).
 
  Best,
  Vladislav
 
  ___
  Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
  http://oss.clusterlabs.org/mailman/listinfo/pacemaker
 
  Project Home: http://www.clusterlabs.org
  Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
  Bugs: 
  http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
  
  ___
  Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
  http://oss.clusterlabs.org/mailman/listinfo/pacemaker
  
  Project Home: http://www.clusterlabs.org
  Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
  Bugs: 
  http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
 
 
 ___
 Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
 http://oss.clusterlabs.org/mailman/listinfo/pacemaker
 
 Project Home: http://www.clusterlabs.org
 Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
 Bugs: 
 http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

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

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] Automating Pacemaker Setup

2011-05-31 Thread Dejan Muhamedagic

On Mon, May 30, 2011 at 10:16:12PM +0200, Andrew Beekhof wrote:
 On Mon, May 30, 2011 at 3:59 PM, Dejan Muhamedagic deja...@fastmail.fm 
 wrote:
  Hi,
 
  On Fri, May 27, 2011 at 08:21:08PM +, veghead wrote:
  veghead sean@... writes:
   Todd Nine todd@... writes:
   Wow. The example pacemaker config and the trick of starting
   heartbeat before
 
  Bah. So close. But I still don't have it completely automated.
 
  If I start heatbeat on the first node and then run:
 
  crm configure  myconfigure.txt
 
  That fails. If I start heartbeat on the second node and wait for the
  two nodes to connect to each other (so that we have a quorum), then I
  can run crm configure and it works.
 
  So that leaves me with couple questions:
 
  1) Is there a way to force crm to accept my configuration request
  ~before~ starting the second node?
 
  No before the DC is elected.
 
 Isn't there a force option?  I thought that set the cib_quorum_override flag.

Actually no, the force option only overrides the shell. Of
course, we could add that.

Thanks,

Dejan

  There are two settings: dc-deadtime
  and startup-fencing which can reduce the time for DC election.
  Note that disabling startup fencing is not recommended. But I
  don't know what's your use case. YMMV.
 
  2) Is there a way to tell Pacemaker to ignore quorum requirements
  ~before~ starting additional nodes?
 
  2) Is there an alternate way to configure Pacemaker?
 
  Yes, you can modify the CIB _before_ starting pacemaker. Sth
  like:
 
  CIB_file=/var/lib/heartbeat/crm/cib.xml crm configure ...
 
  But in that case you need to remove cib.xml.sig. Then you have to
  make sure that pacemaker starts first on this node. Consider this
  only if everything else fails.
 
  Thanks,
 
  Dejan
 
  -Sean
 
 
  ___
  Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
  http://oss.clusterlabs.org/mailman/listinfo/pacemaker
 
  Project Home: http://www.clusterlabs.org
  Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
  Bugs: 
  http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
 
  ___
  Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
  http://oss.clusterlabs.org/mailman/listinfo/pacemaker
 
  Project Home: http://www.clusterlabs.org
  Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
  Bugs: 
  http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
 
 
 ___
 Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
 http://oss.clusterlabs.org/mailman/listinfo/pacemaker
 
 Project Home: http://www.clusterlabs.org
 Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
 Bugs: 
 http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

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

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] Node removal in corosync-based cluster

2011-05-31 Thread Vladislav Bogdanov

31.05.2011 12:32, Dejan Muhamedagic wrote:
On Mon, May 30, 2011 at 05:27:41PM +0300, Vladislav Bogdanov wrote:
Hi,

30.05.2011 17:12, Dejan Muhamedagic wrote:
Hi,

On Sun, May 29, 2011 at 11:58:17PM +0300, Vladislav Bogdanov wrote:
Hi all.

I've got a task to remove some nodes from cluster to save some power and
found that it is not sufficient to follow
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-node-delete.html#s-del-ais

Did you try just crm node delete ...? That should do whatever's
necessary to remove a node (on which pacemaker be down).

What extra commands does it run comparing to Pacemaker Explained?

I must say that I don't know, easy to check in the code, but it
should do whatever's necessary. If it doesn't then we need to fix
it. The idea is that users don't need to know about cibadmin,
crm_node, and such stuff.

The problem is not how to delete node, this works with cibadmin, and
should work with crm shell too. Node is deleted and everything is fine
until pacemaker restart on any remaining node. But after such restart
node re-appears in cib. That should be some artifact in pacemaker (e.g.
not all node-specific data is deleted from some list and that list is
then consulted for a list of nodes). qourum-votes are not touched btw,
they show correct number. Hm. Not sure if clone instances are allocated.
Probably not.
Problem is quite minor, I wrote that just to note that it exists.

Best,
Vladislav

Thanks,

Dejan

I can vaguely recall this case, but cannot remember anymore what
was the outcome.

Thanks,

Dejan

After pacemaker is then restarted on any another remaining node, removed
node comes back in a CIB (with OFFLINE status). Even removal of that
node from corosync's objdb with
corosync-objctl -d runtime.totem.pg.mrp.srp.members.COROSYNC_ID
does not help.

The only way to completely remove node I found is to stop pacemaker on
all cluster nodes and start it again then. So there should be some
'ghost' data in a running pacemaker instance which is not deleted after
removal of node data and status from a CIB.

I hope this could be easily fixed, just a note that it does not fully
work now (1.1.5 with some patches from both 1.1 and devel).

Best,
Vladislav