I +1 what Mark and Gary agreed on the IRC.<div>That's exactly what I meant by 'namespaces' on yesterday's meeting.</div><div><br></div><div>Cheers,</div><div>Salvatore<br><br><div class="gmail_quote">On 24 July 2012 16:30, Sumit Naiksatam (snaiksat) <span dir="ltr"><<a href="mailto:snaiksat@cisco.com" target="_blank">snaiksat@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Gary,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Are you asking this just in the context of the RPC related configurations, or also for moving all the existing configuration from the plugin-specific configuration
files (the ones under etc/quantum/plugins) to a single configuration file?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Moving plugin-independent common configuration to a common file makes sense to me (including the agent and/or RPC related configurations as discussed in the
IRC meeting yesterday). However, I am not in favor of moving all plugin-specific configurations to a single/common file.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">~Sumit.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> Gary Kotton [mailto:<a href="mailto:gkotton@redhat.com" target="_blank">gkotton@redhat.com</a>]
<br>
<b>Sent:</b> Tuesday, July 24, 2012 6:03 AM<br>
<b>To:</b> <a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><br>
<b>Subject:</b> Re: [openstack-dev] [Quantum] Agents and configuration files<u></u><u></u></span></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Hi,<br>
Can people please raise their concerns about moving all of the plugin.ini files into quantum.conf.<br>
This will solve us a number of problems. Please let me know if you have any reservations.<br>
Thanks<br>
Gary<br>
<br>
On 07/24/2012 09:17 AM, Gary Kotton wrote: <u></u><u></u></p>
<p class="MsoNormal">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 href="https://review.openstack.org/#/c/9835/" target="_blank">https://review.openstack.org/#/c/9835/</a>) and scalable agents (<a href="https://review.openstack.org/#/c/9591/" target="_blank">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>
<br>
<u></u><u></u></p>
<pre><u></u> <u></u></pre>
<pre><u></u> <u></u></pre>
<pre>_______________________________________________<u></u><u></u></pre>
<pre>OpenStack-dev mailing list<u></u><u></u></pre>
<pre><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><u></u><u></u></pre>
<pre><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><u></u><u></u></pre>
<p class="MsoNormal"><u></u> <u></u></p>
</div></div></div>
</div>
</div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>