[Linux-ha-dev] 3.0.0: cts?

[Lars Marowsky-Bree]

On 2008-08-21T20:43:55, Andrew Beekhof <beekhof at gmail.com> wrote:

> > 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"
> > it needs.
> wont work as you'd have multiple packages with the same files.
> CTStests.py, CTSaudits.py etc which are very specific to pacemaker

Hm, that means that in the past there's been a bad divergence from clean
engineering then ;-) But that doesn't mean it would be rational to try
and clean it up.

> > 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?
> not me

That's what I'd like, but if noone volunteers, we'll end up dropping in
heartbeat and moving it to pacemaker-cts instead.


Regards,
    Lars

-- 
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