On Tue, Apr 20, 2010 at 03:24:45PM +0200, Lars Marowsky-Bree wrote: > On 2010-04-19T23:03:23, Tim Serong <tser...@novell.com> wrote: > > > 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"> > > ... > > That'd make sense, and possibly include a "obsoleted-by" field.
In that case the shell could try to prevent users to make new configurations with the deprecated resource agents. Dejan > Actually, if the transition is possible in a 1:1 form, this calls for an > XSLT to rewrite the configuration to the new format. > > In fact, in case of "dropped" RAs, it might make more sense to tag the > replacement accordingly. > > > Regards, > Lars > > -- > Architect Storage/HA, OPS Engineering, Novell, Inc. > SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > _______________________________________________________ > 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/
