On 2013-08-13T20:53:13, Andrew Beekhof <[email protected]> wrote:
> > I'd:
> > - Rename the provider to "core"
> > - Rework our own documentation and as we find it
> > - Transparently support references to "ocf:heartbeat" forever:
> > - Re-map s/heartbeat/core/ in the LRM (silently, or it'd get really
> > bloody annoying)
>
> Why not just create a symlink? It doesn't even really matter in which
> direction.
> Then crmsh/pcs just needs to filter whatever they choose to.
> No mapping needed.
Right, that counts as "mapping", I guess. I'm fine with that too.
> > - When a new resource created with that provider, rewrite it to "core"
> > with an LOG_INFO message given to the user
> > - Hide "ocf:heartbeat" from the normal list (or show it as
> > "depreciated, use "core" instead"); but when someone types
> > "ocf:heart<TAB>", auto-complete to it and of course auto-complete
> > all parameters.
Same here, those are just UI issues.
> > So in short: Rename, but remain backwards-compatible (since the price is
> > low).
> Was anyone proposing anything different?
I wasn't sure and thus wanted to make sure we weren't looking at a "hard
rename" situation. So all in all, I'm fine with renaming it.
(I've not had a large number of inquiries as to why something in the
stack is called "heartbeat", though; and if, a "It's history" was always
sufficient. So my feelings aren't very strong about it, either. I guess
the rename will trade them for "so are these different from the
heartbeat ones? Which one do I have to use?" questions.)
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
