Hi!
I think it depend where the agents originate from. "heartbeat" is not the
"product", but the "vendor". Unfortunately some tools like crm don't care a lot
about exact matching which may make a difference if there is an agent with the
same name from differend vendors ("drbd", maybe).
So my proposal would be if all agents come from one source, give them some name
describing the source. Use different names for others.
For my own agents and local modifications I use different "vendors" to avoid
confusion.
Besides the "vendor" name in agents, there's also some "heartbeat" stuff that
isn't related to "heartbeat", like "ocf-shellfuncs" in
"/usr/lib/ocf/lib/heartbeat" (SLES11).
Basically any new structure should emphasize "OCF != heartbeat".
Regards,
Ulrich
>>> David Vossel <[email protected]> schrieb am 30.07.2013 um 00:19 in
>>> Nachricht
<[email protected]>:
> hey,
>
> Historically the ocf resource agents have been shipped under the 'heartbeat'
> provider alias. Now that pacemaker exists, the legacy name "heartbeat" is
> slightly confusing since it refers to another project. We should change
> this.
>
> How would you all feel about moving all the 'heartbeat' provider agents into
> a new provider called 'core', and then for legacy purposes create a
> 'heartbeat' symlink that points to the 'core' directory so no one's
> configuration breaks... Eventually some day we could move in the direction of
> depreciating the use of the 'heartbeat' provider entirely.
>
> good plan? any thoughts?
>
> -- Vossel
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
