That's a good idea. Why not put all OCF library stuff into one package
(ocf-base) and add a package for each resource agent (e.g.
ocfs-ra-drbd). Thus the agents can be updated indipendently, custom RA
modifications can be eqasily maintained (just not update the package in
question.) Also application developeers can provide the RA agent scripts
with the application and say "depend on OCF 2.0.something".
Another cluster manager uses that sceme, however one thing I found
difficult to maintain when working with that cluster manager is to align
all the releases of the RA's to avoid confusion (what is "heartbeat
3.1.4" ?). However pacemaker and heartbeat are not version aligned
currently, so confusion is probably guaranteed :)
Robert
But yes, clearly we hope to have more independently packaged resource
agents one day; it would be so cool if they were instead shipped with
the service package (and not our problem to maintain! ;-). That's a bit
beyond of what we can do with our package layout though.
Regards,
Lars
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
