On 11/04/2013, at 7:24 PM, Kazunori INOUE <inouek...@intellilink.co.jp> wrote:
> Hi Andrew, > > (13.03.01 11:10), Andrew Beekhof wrote: >> On Wed, Feb 13, 2013 at 8:14 PM, Kazunori INOUE >> <inouek...@intellilink.co.jp> wrote: >>> Hi Andrew, >>> >>> Yes, please see attached pacemaker.conf. It controls only pacemakerd. >> >> I've pushed up the basic one in >> https://github.com/beekhof/pacemaker/commit/4bd8ac3 >> >> Once you're happy with the pacemaker-corosync.conf version, let me >> know and we can update it. >> > > I attached two upstart job files for pacemaker. > > - pacemaker.conf.in > It's basic job. I reviewed setting. > Please replace it with mcp/pacemaker.upstart. > > - pacemaker-corosync.conf.in > Since jobs were added to Corosycn(*), this job uses them. > > * > https://github.com/corosync/corosync/commit/ca389c3c598105223f30e2e760f92aa105e1c9b3 I've pushed both of these up. The second one i called pacemaker.combined.upstart The packagers can then install whicheveer one they prefer. > > ---- > Best regards, > Kazunori INOUE > > >>> >>> Furthermore, I'm examining pacemaker-corosync.conf (it's a prototype) which >>> also controls corosync now. >>> This job starts corosync service before starting of pacemakerd, and stops >>> corosync service after the stop of pacemakerd. [1] >>> >>> - pacemaker-corosync.conf >>> 17 >>> 18 pre-start script >>> 19 modprobe softdog soft_margin=60 >>> 20 service corosync start [1] >>> 21 end script >>> 22 >>> 23 post-start script >>> 24 touch $LOCK_FILE >>> 25 pidof $prog > /var/run/$prog.pid >>> 26 end script >>> 27 >>> 28 post-stop script >>> 29 rm -f $LOCK_FILE >>> 30 rm -f /var/run/$prog.pid >>> 31 >>> 32 pidof crmd && killall -q -9 corosync >>> 33 pidof crmd || service corosync stop [1] >>> 34 end script >>> >>> Line 32 is a somewhat tricky design. >>> When only pacemakerd disappeared, corosync is terminated immediately. >>> By doing so, the machine reboots by watchdog of corosync. (since we >>> want to poweroff/reset the machine *certainly* in this case.) >>> >>> Best Regards, >>> Kazunori INOUE >>> >>> >>> (13.02.08 10:03), Andrew Beekhof wrote: >>>> On Tue, Jan 22, 2013 at 9:09 PM, Kazunori INOUE >>>> <inouek...@intellilink.co.jp> wrote: >>>>> >>>>> Hi Andrew, >>>>> >>>>> I understood that pacemakerd was not killed by OOM Killer. >>>>> However, because process failure may occur under the unexpected >>>>> circumstances, we let Upstart manage pacemakerd. >>>> >>>> This is an excellent idea. >>>> Do you have an upstart job for pacemaker that we can include in the source? >>>> >>>> _______________________________________________ >>>> 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 >>> >>> _______________________________________________ >>> 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 >>> >> >> _______________________________________________ >> 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 > <pacemaker.conf.in><pacemaker-corosync.conf.in>_______________________________________________ > 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 _______________________________________________ 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
