----- Original Message ----- > From: "David Vossel" <dvos...@redhat.com> > To: "The Pacemaker cluster resource manager" <pacemaker@oss.clusterlabs.org> > Sent: Monday, July 15, 2013 5:16:11 PM > Subject: Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes > > ----- Original Message ----- > > From: "Lindsay Todd" <rltodd....@gmail.com> > > To: "The Pacemaker cluster resource manager" > > <pacemaker@oss.clusterlabs.org> > > Sent: Thursday, July 11, 2013 12:09:52 PM > > Subject: Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes > > > > So I've switched my cluster to be asymmetric... > > > > The remote nodes don't appear (although the VMs start, and pacemaker_remote > > runs on them). This is a problem. > > > > Temporarily switch to symmetric without restarting everything, and the > > remote > > nodes appear in the cluster status. (But I'd have to do more > > reconfiguration > > here.) Seems like the "remote node" resource won't start on the VM without > > some imaginary location constraint to help it? > > ha, yep that's exactly what is going on. I can fix that. I'll post a patch > soon.
Both the crash and the problem with remote-nodes in asymmetrical clusters should be fixed upstream now. https://github.com/ClusterLabs/pacemaker/commit/1b2e3ead42340ce0cae41a96dd32c44ffb5acb7d https://github.com/ClusterLabs/pacemaker/commit/5fb95fbfb7ef8cb899633bdcb9d515f02272a417 Thanks again for your continued involvement with helping stabilize this feature. This has been very valuable feedback. -- Vossel _______________________________________________ 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://bugs.clusterlabs.org
