On 09/08/2014 11:02 AM, David Magda wrote:
On Sat, Sep 06, 2014 at 02:14:29PM -0400, David Magda wrote:
On Sep 6, 2014, at 12:00, Ken Gaillot <kjgai...@gleim.com> wrote:
# This allows slapd to run on both hosts.
clone ldap-daemon-clone ldap-daemon meta globally-unique="false"
interleave="true"
[...]
I'll give it a go.
This worked.
primitive dmn_slapd ocf:work:slapd \
params config="/etc/ldap/slapd.d" user="openldap" \
services="ldap:/// ldapi:///" group="openldap" \
op monitor interval="20s" timeout="5s"
clone dmn_slapd_clone dmn_slapd \
meta globally-unique="false" interleave="true" target-role="Started"
colocation colo-vip_ldap2-with-dmn_slapd +inf: vip_ldap2 dmn_slapd_clone
Since the daemon is managed by Pacemaker on each node, is there a way
to start and stop it on a per-node basis? Doing a "crm resource
<start/stop> dmn_slapd" seems to effect both systems. What if I want to do
stop it on only one?
I find the easiest way is to put the node in standby then online again.
This does mean any other resources on the node get restarted, but that's
acceptable in our setup.
I am curious whether there is a cleaner way to restart a cloned resource
on a single node only.
-- Ken Gaillot <kjgai...@gleim.com>
Network Operations Center, Gleim Publications
_______________________________________________
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
