AlexanderKrauth/resource-agents — comment on commit 9ded560e14dde4590c9f88fc065611e660a1ae56
File: heartbeat/SAPDatabase line 94
By AlexanderKrauth:

> That's kind of contradictory :) Note that most often we push the
> latest upstream with the maintenance update, so this change may
> appear earlier. Of course, only in case it is considered safe.
Ok, sorry. Here I was completely wrong.

> > How is the
> > "normal" way to handle this ? I would dislike something like
> > "SAPDatabase2".
> Yes, it was done for IPaddr and that didn't turn out to be such a
> good choice. The best way is to detect if the required capability
> is installed and if not to use the old method. Would that be
> possible?
Agree.

> How probable it is that "old" installations may break? And how
> old are those installations?
I'm just in a discussion with some SuSE consultants and
supporters to get a better feeling about this point. I don't know
how many people did setup a SAP system with pacemaker
by themself. I expect the most systems have been setup by
consultants.

So, if I got you correct. You think about an agent that has both,
the new and the old code in it. If we find the executable of the
required daemon, we use the new functions, otherwise the
old once.
I think that is doable. In that case I would separate the old
funcionality into specific functions. So there would be functions
like:
start
start_old
stop
stop_old
...
That would it make easier to remove it in the future.

Is this a valid solution ?