On 4/20/2010 at 06:48 AM, Lars Marowsky-Bree <[email protected]> wrote: > On 2010-04-19T22:22:41, Lars Ellenberg <[email protected]> wrote: > > > > - EvmsSCC and > > > - Evmsd (both apply to EVMS, which is no longer maintained); > > Fine with me, as newer distributions don't ship with EVMS anymore anyways. > > Older distros (read: sles10) can easily keep the latest copy of those. > > Ah, damn ;-) I'd have preferred if it stayed, but yes, we can do that. > In fact, we drop them when building for SLE 11, anyway.
Um... No we don't. > Maybe that's another option: --with-depreciated-ras=yes > > [...] > > > Dejan, Rasto, Tim, Yan: > > Our various user interfaces should probably warn about > > deprecated resource agents, too. > > Agreed, see above. (In a not-to-annoying fashion, because otherwise, > usability will suffer.) > > In general, I think the ability to depreciate functionality is needed, > but shouldn't be slip-streamed into a minor dot release, and we first > need to do some more home work to get our infrastructure right before we > should consider breaking customer configurations. This'd be easiest if the metadata explicitly said an RA was deprecated, for example something like: <?xml version="1.0"?> <!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd"> <resource-agent name="Evmsd" version="0.9" deprecated="true"> ... ATM, the deprecated RAs all seem to follow the same convention of using "(deprecated)" in the shortdesc, e.g.: <shortdesc lang="en">Controls clustered EVMS volume management (deprecated)</shortdesc> ...but grepping arbitrary text out of a description always irks me. It's a little inexact. Regards, Tim -- Tim Serong <[email protected]> Senior Clustering Engineer, OPS Engineering, Novell Inc. _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
