<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 07/25/2012 11:02 PM, Sumit Naiksatam (snaiksat) wrote:
<blockquote
cite="mid:EB132BBECF89D84389712203CAA37C5707C77E@xmb-rcd-x02.cisco.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Thanks Bob for bringing this up. The following
option you stated sounds good to me:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">“to have a variable in quantum.conf specify which
plugin-specific .ini file(s) need(s)”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">To take it one step further, could this variable
be pointed to a directory name? That way it would require a
single configuration in the quantum.conf, and all the ini
files in that directory could be loaded.</span></p>
</div>
</blockquote>
<br>
Sadly this is not supported by the common config code at the moment.
The fact that we are using the common configuration code enables the
application to pass a number of different configuration files via
the command line options.<br>
<br>
In my opinion one of the nice things about the common configuration
is that it give the user a lot of flexibility. There may be some who
want to have all of the information in one configuration file - for
example quantum.conf. Others may want to preserve the same format as
today. Both of these are supported. By default we will be using the
latter to support backward compatibility.<br>
<br>
<span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31, 73,
125);"><o:p> </o:p></span>
<blockquote
cite="mid:EB132BBECF89D84389712203CAA37C5707C77E@xmb-rcd-x02.cisco.com"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">~Sumit.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div style="border-width: medium medium medium 1.5pt;
border-style: none none none solid; border-color:
-moz-use-text-color -moz-use-text-color -moz-use-text-color
blue; padding: 0in 0in 0in 4pt;">
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none;
border-color: rgb(181, 196, 223) -moz-use-text-color
-moz-use-text-color; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family:
"Tahoma","sans-serif";"> Dan
Wendlandt [<a class="moz-txt-link-freetext" href="mailto:dan@nicira.com">mailto:dan@nicira.com</a>]
<br>
<b>Sent:</b> Wednesday, July 25, 2012 12:46 PM<br>
<b>To:</b> OpenStack Development Mailing List<br>
<b>Subject:</b> Re: [openstack-dev] [Quantum] Agents
and configuration files<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom: 12pt;"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Jul 25, 2012 at 12:23 PM,
Robert Kukura <<a moz-do-not-send="true"
href="mailto:rkukura@redhat.com" target="_blank">rkukura@redhat.com</a>>
wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">On 07/24/2012 01:24 PM, Gary Kotton
wrote:<br>
> Hi,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;">> I
have made a first patch - <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/10234"
target="_blank">
https://review.openstack.org/#/c/10234</a>. It<br>
> was actually simpler than I had expected. By a
fluke the change also<br>
> imported better logging for the agents. This should
also move to the<br>
> openstack-common logging.<br>
> I still need to do some additional work:<br>
> 1. ensure agent tests are OK<br>
> 2. update devstack to support the configurations<o:p></o:p></p>
</div>
<p class="MsoNormal">I have begun reviewing patch set 5, and
so far it looks good. I'd like<br>
to see this merged quickly to resolve the plugin unit test
issues<br>
currently on master.<br>
<br>
But I do have one significant concern about the direction
the quantum<br>
configuration has taken. My understanding is that with
this patch,<br>
neither the quantum-server nor the agents are intended to
load the<br>
plugin-specific .ini file unless a second --config-file
option<br>
referencing it is passed in the command line. Unless I am
missing<br>
something, this means that the quantum-server command line
will now need<br>
to be plugin-specific in order for the plugin-specific
.ini file to be<br>
loaded. Although this can be handled in devstack, it seems
to be<br>
problematic for downstream systemd/init/upstart scripts
which should<br>
generally not require customization once they are
installed.<br>
<br>
I'm not very familiar with the common config mechanisms
yet, but would<br>
it be possible for both the quantum-server/plugin and the
agent to<br>
automatically load their .ini file(s), to have the
quantum.conf file<br>
somehow include the .ini file(s), or to have a variable in
quantum.conf<br>
specify which plugin-specific .ini file(s) need(s) to be
loaded? This<br>
way, the quantum-server command line in the
systemd/init/upstart scripts<br>
would only need to reference quantum.conf, and would not
need to be<br>
customized based on which plugin is chosen.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jumping into this thread late, so
please ignore this if the ideas I'm suggesting have
already been considered and rejected. Bob, I tend to
share your viewpoint on this. I do think its nice to be
able to specify a particular config file for the plugin
(currently, this is impossible, the plugin will just
search a set of paths), however, I wonder if this could
be achieved either by putting all plugin config into
separate sections of the quantum.conf, or by having an
entry of quantum.conf point to plugin config in some
way. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">dan<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border-width: medium medium medium 1pt;
border-style: none none none solid; border-color:
-moz-use-text-color -moz-use-text-color
-moz-use-text-color rgb(204, 204, 204); padding: 0in 0in
0in 6pt; margin-left: 4.8pt; margin-right: 0in;">
<p class="MsoNormal"><br>
-Bob<o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
> Thanks<br>
> Gary<br>
><br>
> On 07/24/2012 08:15 PM, Gary Kotton wrote:<br>
>> Hi,<br>
>> Please see my inline below.<br>
>> Thanks<br>
>> Gary<br>
>><br>
>> On 07/24/2012 07:47 PM, Salvatore Orlando
wrote:<br>
>>> I +1 what Mark and Gary agreed on the
IRC.<br>
>>> That's exactly what I meant by
'namespaces' on yesterday's meeting.<br>
>>><br>
>>> Cheers,<br>
>>> Salvatore<br>
>>><br>
>>> On 24 July 2012 16:30, Sumit Naiksatam
(snaiksat) <<a moz-do-not-send="true"
href="mailto:snaiksat@cisco.com">snaiksat@cisco.com</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">>>> <mailto:<a
moz-do-not-send="true"
href="mailto:snaiksat@cisco.com">snaiksat@cisco.com</a>>>
wrote:<br>
>>><br>
>>> Hi Gary,<br>
>>><br>
>>><br>
>>><br>
>>> Are you asking this just in the
context of the RPC related<br>
>>> configurations, or also for moving
all the existing configuration<br>
>>> from the plugin-specific
configuration files (the ones under<br>
>>> etc/quantum/plugins) to a single
configuration file?<br>
>>><br>
>><br>
>> The RPC was the motivation for this. This is
information that is<br>
>> required by both the agents and the plugins.
In addition to this due<br>
>> to the fact that is is from the
openstack-common (which used the<br>
>> global cfg.CONF) complicates things.<br>
>><br>
>> There is still the option to use multiple
files with input like:<br>
>> --config-file=/etc/quantum.conf
--config-file=/etc/quantum/quantum.conf
--config-dir=/etc/quantum/plugins.d<br>
>><br>
>> Thanks<br>
>> Gary<br>
>><br>
>><br>
>>><br>
>>><br>
>>> Moving plugin-independent common
configuration to a common file<br>
>>> makes sense to me (including the
agent and/or RPC related<br>
>>> configurations as discussed in the
IRC meeting yesterday).<br>
>>> However, I am not in favor of moving
all plugin-specific<br>
>>> configurations to a single/common
file.<br>
>>><br>
>>><br>
>>><br>
>>> Thanks,<br>
>>><br>
>>> ~Sumit.<br>
>>><br>
>>><br>
>>><o:p></o:p></p>
</div>
<p class="MsoNormal">>>> *From:*Gary Kotton
[mailto:<a moz-do-not-send="true"
href="mailto:gkotton@redhat.com">gkotton@redhat.com</a><br>
>>> <mailto:<a moz-do-not-send="true"
href="mailto:gkotton@redhat.com">gkotton@redhat.com</a>>]<br>
>>> *Sent:* Tuesday, July 24, 2012 6:03 AM<br>
>>> *To:* <a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
>>> <mailto:<a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
>>> *Subject:* Re: [openstack-dev]
[Quantum] Agents and configuration<o:p></o:p></p>
<div>
<p class="MsoNormal">>>> files<br>
>>><br>
>>><br>
>>><br>
>>> Hi,<br>
>>> Can people please raise their
concerns about moving all of the<br>
>>> plugin.ini files into quantum.conf.<br>
>>> This will solve us a number of
problems. Please let me know if<br>
>>> you have any reservations.<br>
>>> Thanks<br>
>>> Gary<br>
>>><br>
>>> On 07/24/2012 09:17 AM, Gary Kotton
wrote:<br>
>>><br>
>>> Hi,<br>
>>><o:p></o:p></p>
</div>
<p class="MsoNormal">>>> *Background*: The
quantum service makes use of the configuration<o:p></o:p></p>
<div>
<p class="MsoNormal">>>> file quantum.conf.
In addition to this there is a common<br>
>>> configuration file shared between the
plugin and the agent<br>
>>> (plugin.ini). The aforementioned
files are loaded by the common<br>
>>> configuration files.<br>
>>><o:p></o:p></p>
</div>
<p class="MsoNormal">>>> *Current
developments*: A number of current developments, for<o:p></o:p></p>
<div>
<p class="MsoNormal">>>> example
notifications (<a moz-do-not-send="true"
href="https://review.openstack.org/#/c/9835/"
target="_blank">https://review.openstack.org/#/c/9835/</a>)<br>
>>> and scalable agents (<a
moz-do-not-send="true"
href="https://review.openstack.org/#/c/9591/"
target="_blank">https://review.openstack.org/#/c/9591/</a>)<br>
>>> require RPC configurations.<br>
>>><br>
>>> From the discussion last night the
community the consensus is to<br>
>>> have the common configuration items
that may be relevant to one<br>
>>> or more agent/plugin in the quantum
configuration file. This<br>
>>> change will require the agents to
also load the quantum.conf<br>
>>> configuration files.<br>
>>><o:p></o:p></p>
</div>
<p class="MsoNormal">>>> *Open issues*:<o:p></o:p></p>
<div>
<p class="MsoNormal">>>> 1. I do not think
that the common configuration supports mapping<br>
>>> of name spaces to configuration
files.<br>
>>> 2. Configuration file loading. With
the plugins the configuration<br>
>>> files are loaded in two stages. If
possible it would be great<br>
>>> that the files could be loaded at
once - this can be done by<br>
>>> listing the plugin/agent ini file(s)
in the quantum.conf. When<br>
>>> this is loaded then the other files
will be loaded.<br>
>>><br>
>>> Please let me know if you have any
comments or objections. I<br>
>>> would like to move ahead and start to
work on this.<br>
>>><br>
>>> Thanks<br>
>>> Gary<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>>
_______________________________________________<br>
>>><br>
>>> OpenStack-dev mailing list<br>
>>><o:p></o:p></p>
</div>
<p class="MsoNormal">>>> <a
moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<mailto:<a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>><o:p></o:p></p>
<div>
<p class="MsoNormal">>>><br>
>>> <a moz-do-not-send="true"
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>
>>><br>
>>><br>
>>><br>
>>>
_______________________________________________<br>
>>> OpenStack-dev mailing list<br>
>>> <a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><o:p></o:p></p>
</div>
<p class="MsoNormal">>>> <mailto:<a
moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">>>> <a
moz-do-not-send="true"
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>
>>><br>
>><br>
>><br>
>>
_______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> <a moz-do-not-send="true"
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>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a moz-do-not-send="true"
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>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
Dan Wendlandt <o:p></o:p></p>
<div>
<p class="MsoNormal">Nicira, Inc: <a moz-do-not-send="true"
href="http://www.nicira.com" target="_blank">www.nicira.com</a><o:p></o:p></p>
<div>
<p class="MsoNormal">twitter: danwendlandt<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>