[openstack-dev] [metering] add self- enable/disable check on plugin load

Julien Danjou julien at danjou.info
Tue Sep 11 08:35:12 UTC 2012

On Mon, Sep 10 2012, Doug Hellmann wrote:


> The config options are meant to handle the case where a deployer wants to
> change which counters are being measured. We should use the
> openstack.common.cfg configuration code we're already using elsewhere,
> rather than add a new file. I think we just need a single option for each
> type of plugin ("disabled_pollsters", "disabled_listeners", etc.) where the
> value of the configuration setting would be a comma-separated list of
> plugin names. The name of each plugin would be checked against the list
> from the config option before it is loaded, and disabled plugins would not
> be loaded (the code might be imported, but the plugin wouldn't be
> instantiated).

So to sum up, IIUC:
- some code check the config to see if the plugin should be disabled
- some code is run to check that the plugin is able to be functionnal
  (e.g. you are running with libvirt)

That's fine with me.

Julien Danjou
/* Free Software hacker & freelance
   http://julien.danjou.info */
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20120911/d4c96812/attachment.pgp>

More information about the OpenStack-dev mailing list