<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
<b>Background</b>: The quantum service makes use of the
configuration file quantum.conf. In addition to this there is a
common configuration file shared between the plugin and the agent
(plugin.ini). The aforementioned files are loaded by the common
configuration files.<br>
<br>
<b>Current developments</b>: A number of current developments, for
example notifications (<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/9835/">https://review.openstack.org/#/c/9835/</a>) and
scalable agents (<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/9591/">https://review.openstack.org/#/c/9591/</a>) require RPC
configurations. <br>
<br>
From the discussion last night the community the consensus is to
have the common configuration items that may be relevant to one or
more agent/plugin in the quantum configuration file. This change
will require the agents to also load the quantum.conf configuration
files.<br>
<br>
<b>Open issues</b>:<br>
1. I do not think that the common configuration supports mapping of
name spaces to configuration files.<br>
2. Configuration file loading. With the plugins the configuration
files are loaded in two stages. If possible it would be great that
the files could be loaded at once - this can be done by listing the
plugin/agent ini file(s) in the quantum.conf. When this is loaded
then the other files will be loaded. <br>
<br>
Please let me know if you have any comments or objections. I would
like to move ahead and start to work on this.<br>
<br>
Thanks<br>
Gary<br>
<br>
</body>
</html>