<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 18, 2015 at 11:31 AM, Chris Friesen <span dir="ltr"><<a href="mailto:chris.friesen@windriver.com" target="_blank">chris.friesen@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 09/18/2015 11:01 AM, John Griffith wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
<br>
On Fri, Sep 18, 2015 at 9:06 AM, Chris Friesen <<a href="mailto:chris.friesen@windriver.com" target="_blank">chris.friesen@windriver.com</a><br></span><span class="">
<mailto:<a href="mailto:chris.friesen@windriver.com" target="_blank">chris.friesen@windriver.com</a>>> wrote:<br>
<br>
On 09/18/2015 06:57 AM, Eric Harney wrote:<br>
<br>
On 09/17/2015 06:06 PM, John Griffith wrote:<br>
<br>
<br>
Having the "global conf" settings intermixed with the backend sections<br>
caused a number of issues when we first started working on this. That's<br>
part of why we require the "self.configuration" usage all over in the<br>
drivers. Each driver instantiation is it's own independent entity.<br>
<br>
<br>
Yes, each driver instantiation is independent, but that would still be<br>
the case if these settings inherited values set in [DEFAULT] when they<br>
aren't set in the backend section.<br>
<br>
<br>
Agreed. If I explicitly set something in the [DEFAULT] section, that should<br>
carry through and apply to all the backends unless overridden in the<br>
backend-specific section.<br>
</span></blockquote>
<br><span class="">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bottom line "yes", ideally in the case of drivers we would check global/default<br>
setting, and then override it if something was provided in the driver specific<br>
setting, or if the driver itself set a different default. That seems like the<br>
right way to be doing it anyway. I've looked at that a bit this morning, the<br>
issue is that currently we don't even pass any of those higher level conf<br>
settings in to the drivers init methods anywhere. Need to figure out how to<br>
change that, then it should be a relatively simple fix.<br>
</blockquote>
<br></span>
Actually, I think it should be slightly different. If I set a variable in the global/default section of the config file, then that should override any defaults in the code for a driver.<br></blockquote><div> </div><div><font face="monospace, monospace"><div class="gmail_default" style="font-family:monospace,monospace;display:inline">Hmm... well, on the bright side that might be easier to implement at least :). I guess I don't agree on the meaning of "DEFAULT", to me a "DEFAULT" section means, "these are the defaults if you don't specify something else", no? Your proposal seems really counter-intuitive to me.</div></font></div><div><br></div><div><div class="gmail_default" style="font-family:monospace,monospace">Anyway, I've come up with a way to read the DEFAULT section of CONF on init in the driver so that's good. The trick now though is when there's a difference in value between the driver section and the default section; knowing what was set explicitly and what wasn't. In other words I don't have any way of knowing for sure if the setting came from reading in the defaults in the declaration options or if it was explicitly set in the config file.</div><br></div><div><div class="gmail_default" style="font-family:monospace,monospace">Still working on it, but curious if anybody might know how to get around this little sticking point.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Thanks,</div><div class="gmail_default" style="font-family:monospace,monospace">John</div><br></div><div><font face="monospace, monospace"><div class="gmail_default" style="font-family:monospace,monospace;display:inline"><br></div></font></div><div><font face="monospace, monospace"><div class="gmail_default" style="font-family:monospace,monospace;display:inline"><br></div></font></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
So the order of descending precedence would go:<br>
<br>
1) setting specified in driver-specific section of config file<br>
2) setting specified in global/default section of config file<br>
3) setting specified in driver-specific code<br>
4) setting specified in global/default code (not sure if this exists)<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
Chris<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div><div class="h5"><br></div></div></blockquote></div><br></div></div>