On Wed, Aug 18, 2010 at 5:09 PM, Aaron Cline <[email protected]> wrote: > Hi: > > Hopefully these are a couple of easy questions, but I haven't really found a > good way to do what I'm looking for. I'm using heartbeat 3.0.3 and > pacemaker 1.0.9. Below is my config. I have 4 IPaddr2 resources that are > grouped with an nginx resource in a colocation group. > > What's the best way (hopefully also the simplest way) to shutdown all of the > resources?
crm resource stop nginx or crm resource stop ClusterIP1 > > Also, how can I just reload nginx after a config change? Do you mean nginx's configuration in the cib? http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-reload.html > primitive ClusterIP1 ocf:heartbeat:IPaddr2 \ > params ip="174.143.208.90" cidr_netmask="32" \ > meta is-managed="true" \ > op monitor interval="30s" > primitive ClusterIP2 ocf:heartbeat:IPaddr2 \ > params ip="174.143.213.216" cidr_netmask="32" \ > meta is-managed="true" \ > op monitor interval="30s" > primitive ClusterIP3 ocf:heartbeat:IPaddr2 \ > params ip="174.143.213.142" cidr_netmask="32" \ > meta is-managed="true" \ > op monitor interval="30s" > primitive ClusterIP4 ocf:heartbeat:IPaddr2 \ > params ip="174.143.213.109" cidr_netmask="32" \ > meta is-managed="true" \ > op monitor interval="30s" > primitive nginx lsb:nginx \ > meta is-managed="true" \ > op monitor interval="30s" > colocation nginx-with-ips inf: nginx ClusterIP1 ClusterIP2 ClusterIP3 > ClusterIP4 > order nginx-after-ips inf: ClusterIP1 ClusterIP2 ClusterIP3 ClusterIP4 nginx > > Thanks. > > Aaron > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
