On Wed, Feb 9, 2011 at 3:35 PM, Lars Ellenberg <lars.ellenb...@linbit.com> wrote: > On Wed, Feb 09, 2011 at 02:43:17PM +0100, Andrew Beekhof wrote: >> >> Are you going to change the name of every agent that gets a rewrite? >> >> >> >> IPaddr2-ng-ng-again-and-one-more-plus-one >> > >> > I don't think it is going to happen that often. >> >> It happens often enough - its just normally by a core developer. >> And realistically, almost every RA is going to get similar treatment >> (over time) as they're merged with the Red Hat ones. >> >> > >> >> Solicit feedback, like was done for kliend's new agent, and replace >> >> the existing one it if/when people respond positively. > > >> >> Its not like the old one disappears from the face of the earth after >> >> you merge the new one. >> >> >> >> wget -o /usr/lib/ocf/resource.d/heartbeat/db2 >> >> http://hg.linux-ha.org/agents/file/agents-1.0.3/heartbeat/db2 >> > >> > What do you suggest? That we add to the release announcement: >> > >> > The db2 RA has been rewritten and didn't get yet a lot of >> > field testing. Please help test it. >> >> So don't do that :-) >> Put up a wiki page with instructions for how to download+use the new >> agent and give feedback. > > How about a staging area? > /usr/lib/ocf/resource.d/staging/
I was thinking along the same lines when I said "testing". Either name works for me :-) > > we can also add a > /usr/lib/ocf/resource.d/deprecated/ > > The thing in .../heartbeat/ can become a symlink, > and be given "config file status" by the package manager? > Something like that. > > So we have it bundled with the release, > it is readily available without much "go to that web page and download > and save to there and make executable and then blah". > > It would simply pop up in crm shell and DRBD-MC and so on. > > We can add "please give feedback" to the description, > and "this will replace the current RA with release + 2 > unless we get veto-ing feedback" to the release notes. > > Once settled, we copy over the staging one to the "real" directory, > replacing the "original" one, and add a "please fix your config" to the > thing that remains in staging/, so we will be able to start a further > rewrite with the next "merge window". > > * does not break existing setups > * new RAs and rewrites are readily available > > > -- > : Lars Ellenberg > : LINBIT | Your Way to High Availability > : DRBD/HA support and consulting http://www.linbit.com > > DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. > _______________________________________________________ > Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev > Home Page: http://linux-ha.org/ > _______________________________________________________ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/