[openstack-dev] [quantum] Ensuring plugin agent configs are present for server (bug-1059923)

Paul Michali pcm at cisco.com
Fri Feb 1 18:51:23 UTC 2013


Seeking some suggestions/comments/guidance on this…

Issue was that user started quantum server with the core config file specified, but not any plugin config file. As a result, it used sqlite, though the setup was using mysql.  The goal is to try to prevent this issue.  From some discussion already, it appears that the approach should be to "validate" the plugin config options, rather than checking for any file, as a user could aggregate config settings into one file, with both core and plugin config settings.

I've got a few questions for plugin agent developers (this is my first bug, so I'm trying to get up to speed).

Would we be able to identify a set of plugin configuration options that all plugins must contain, or will they vary per plugin?
If there is a single set of config options that can be considered "mandatory" would we be able to change their definition and mark them as "required" so that exclusion of them is automatically detected by cfg, or will that cause issues (it seems like the cfg is shared by the server and  plugin agents)?
If the "required" configuration options vary per plugin, is it possible to push the validation of config down to the plugin (agent)?
If we do push down the validation, though, is there a way that this can be checked at the quantum server? IOW does the server invoke the agent(s) validator function?
Is this bug even worth pursuing, or should the proper configuration inclusion be something handled by provisioning tools? IOW rely on tooling to make sure the right files are included and "expect" that the user knows what they are doing, if they do this manually? Guess I need to ask that "is it worth fixing this" question :)

Thanks in advance for any guidance!


PCM (Paul Michali)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130201/2c0f1741/attachment.html>


More information about the OpenStack-dev mailing list