<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 29, 2013 at 10:06 AM, Mark McLoughlin <span dir="ltr"><<a href="mailto:markmc@redhat.com" target="_blank">markmc@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mon, 2013-04-29 at 09:28 -0400, Doug Hellmann wrote:<br>
><br>
><br>
><br>
> On Mon, Apr 29, 2013 at 6:47 AM, Mark McLoughlin <<a href="mailto:markmc@redhat.com">markmc@redhat.com</a>> wrote:<br>
<br>
><br>
</div><div class="im">> * There are probably reasonable use cases (like a ceilometer<br>
> notifications plugin used by nova, but also cells) for a service to<br>
> connect to another broker and/or use a different exchange. Even<br>
> without those use cases, though, I think it would be lame for the<br>
> API to only allow such things to be specified through global<br>
> configuration ... global configuration should be a convenience<br>
> default only.<br>
><br>
><br>
> Agreed. I would prefer it if we could establish an API that didn't use<br>
> the global configuration object at all.<br>
<br>
</div>I guess I'm thinking that this is the only place it's used:<br>
<br>
def get_transport_driver(url=None, conf=None):<br>
conf = conf or cfg.CONF<br>
<br>
i.e. the entry point into the library is to construct a transport<br>
driver. If that has optional support for using the global object, I<br>
don't think it's a big deal.<br></blockquote><div><br></div><div style>I'd rather we just have the caller pass it in. Unless we're going to have a handle to it already?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When I said "global configuration", though, I actually more meant that<br>
it would be lame if transport configuration could only come from a cfg<br>
object - e.g. if ceilometer had to construct a cfg object with the<br>
configuration required to connect to glance notifications.<br></blockquote><div><br></div><div style>Yes, we should *definitely* avoid that.</div><div style><br></div><div style>Doug</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers,<br>
Mark.<br>
<br>
<br>
</blockquote></div><br></div></div>