[Linux-ha-dev] 3.0.0: cts?
lmb at suse.de
Thu Aug 21 10:21:40 MDT 2008
where should we maintain CTS?
Pacemaker has it's own fork of it, at this point in time.
But I think CTS makes sense for heartbeat to have too, as _someone_
might still care for the v1 functionality, and it might make sense to
test just the cluster layer w/o resources.
My preferred approach would be to create heartbeat-cts as a package, and
put CTS in there; and then, Pacemaker would just drop in the "overlays"
That might require some cleanups to CTS, to make the CRM (as a generic
term) independent of the infrastructure layer; then, RHT could also use
the CTS-openAIS plugin below RHCS, for example. And the Pacemaker plugin
would remain unchanged, whether running on top of openAIS or heartbeat.
Yet: who would do the work?
But then, is there a future in heartbeat's _cluster infrastructure_ as
opposed to some of the supporting code? I'm not sure I see it, and then
it might make more sense to move CTS over to Pacemaker completely.
I'd hate to see losing the ability to test heartbeat by itself though.
Any comments or thoughts?
Any takers for doing it the proper way?
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
More information about the Linux-HA-Dev