On Thu, 2009-02-19 at 12:33 +0100, Rasto Levrinc wrote: > Tuesday 17 February 2009 09:10:13 pm Andrew Beekhof wrote: > > > Is it just mgmtd protocol issues preventing it from being used with > > Pacemaker? (Obviously there is a new syntax available in 1.0 but its > > still > > possible to run 1.0 with the same syntax used in Heartbeat 2.1.3). > > > > I have not tried it with Pacemaker yet, there were some minor changes from > Heartbeat 2.1.3 to 2.1.4, that influence our gui, so I am fixing that and > then I will have a look what's the deal with the Pacemaker. It has been changed a lot from the version in 2.1.4. All of the legacy protocols that could possibly break CIB configuration have been dumped. There are new C/R/U/D protocols for handling CIB. Besides, facilities for invoking crm_*/ptest commands are provided
> > I have a question as well. The gui needs to talk to the mgmtd via command > line locally. It does that through TCP over TLS, instead of "via command line locally" > At the moment it uses python library from heartbeat-gui for > that, which is only a temporary solution. It's a python wrapper instead of a python library. You could also use the "libhbmgmtclient" > Could we include a small C > program to the Pacemaker, that passes command line arguments to the mgmtd or > is there some better way? It would be possible not to use mgmtd, but is the > only way to obtain events as far as I know. As Andrew said, a client could talk to cib directly if you don't need other facilities provided by mgmtd -- Regards, Yan Gao China R&D Software Engineer [email protected] Novell, Inc. Making IT Work As One?6?4 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
