← Back to team overview

openstack team mailing list archive

the right way to deprecate a config option?

 

I'm reworking the virt driver loading so that it's using importutils (and thus looking more like the other driver interfaces), which means eventually connection_type parameter in nova.conf goes away, and computer_driver is used directly (the support is already there, but it's not currently used by default).

Is there a standard mechanism for deprecating a conf option like this? Right now I'm just triggering a LOG.error() with a deprecation message, but it seems like there should be something more standard for that, especially as we get into a deprecate in N, remove in N+1. I'm assuming this is a deprecation in Folsom (where the docs are changed to the new method), then remove the backwards compat in G.

	-Sean

--
Sean Dague
IBM Linux Technology Center
email: sdague@xxxxxxxxxxxxxxxxxx
alt-email: sldague@xxxxxxxxxx



Follow ups