In oslo.db, I'd like to rename the option "idle_timeout" to
"connection_recycle_time".
Following the pattern of using DeprecatedOpt, we get this:
cfg.IntOpt('connection_recycle_time',
default=3600,
deprecated_opts=[cfg.DeprecatedOpt('idle_timeout',
group="DATABASE"),
cfg.DeprecatedOpt('idle_timeout',
group="database"),
cfg.DeprecatedOpt('sql_idle_timeout',
group='DEFAULT'),
cfg.DeprecatedOpt('sql_idle_timeout',
group='DATABASE'),
cfg.DeprecatedOpt('idle_timeout',
group='sql')],
However, Nova is accessing "conf.idle_timeout" directly in
nova/db/sqlalcemy/api.py -> _get_db_conf. Tempest run fails.
Per the oslo.config documentation, the "deprecated_name" flag would
create an alias on the conf. namespace. However, this has no effect,
even if I remove the other deprecated parameters completely:
cfg.IntOpt('connection_recycle_time',
default=3600,
deprecated_name='idle_timeout',
a simple unit test fails to see a value for
conf.connection_recycle_time, including if I add
"deprecated_group='DATABASE'" which is the group that's in this
specific test (however this would not be a solution anyway because
projects use different group names).
From this, it would appear that oslo.config has made it impossible to
deprecate the name of an option because DeprecatedOpt() has no means
of providing the value as an alias on the conf. object. There's not
even a way I could have projects like nova make a forwards-compatible
change here.
Is this a bug in oslo.config or in oslo.db's usage of oslo.confg?
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
