[Pacemaker] why use ocf::linbit:drbd instead of ocf::heartbeat:drbd?
Florian Haas
florian.haas at linbit.com
Mon Oct 12 12:21:52 UTC 2009
On 2009-10-12 14:08, Andrew Beekhof wrote:
> On Mon, Oct 12, 2009 at 1:49 PM, Florian Haas <florian.haas at linbit.com> wrote:
>> On 2009-10-12 09:06, Andrew Beekhof wrote:
>>> On Mon, Oct 12, 2009 at 8:43 AM, Florian Haas <florian.haas at linbit.com> wrote:
>>>> Andrew, Dejan: as we consider the ocf:linbit:drbd RA stable as of the
>>>> DRBD 8.3.4 release, is it acceptable to remove the legacy RA from the
>>>> agents repository?
>>> I think rather than remove it (which would break existing clusters),
>>> i'd rewrite it to look for the linbit one and re-exec that.
>>> If the linbit one isn't present, log an error with a URL and return
>>> OCF_NOT_INSTALLED.
>> We can do that; however we would also have to check for
>> clone_overrides_hostname and return OCF_ERR_CONFIGURED even if the
>> linbit RA is installed.
>
> well the linbit RA would do that wouldn't it? no need to repeat the logic.
No that linbit RA does not check for clone_overrides_hostname. Is it
customary for RAs to warn or error out in case the user has set an
unsupported parameter? I hadn't thought so.
Cheers,
Florian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091012/df80f623/attachment-0004.sig>
More information about the Pacemaker
mailing list