On Fri, Aug 8, 2014 at 12:41 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > That’s right. The preferred approach is to put the register_opt() in > *runtime* code somewhere before the option will be used. That might be in > the constructor for a class that uses an option, for example, as described > in > http://docs.openstack.org/developer/oslo.config/cfg.html#registering-options > > Doug
Interesting. I've been following the prevailing example in Nova, which is to register opts at the top of a module, immediately after defining them. Is there a situation in which one approach is better than the other? Thanks, Devananda _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
