<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Are the group names programmatically computed/accessed? Ie, do you do something like: Figure out what plugins are loaded. Then look at CONF.<plugin_name>.<variable> ?<div><br></div><div>I still think maybe JSON is more what we need for cells… but just curious.</div><div><div><div><br><div><div>On Jun 14, 2013, at 12:57 PM, Jeremy Hanmer <<a href="mailto:jeremy@dreamhost.com">jeremy@dreamhost.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">FWIW, this (config groups for each cell) sounds like how quantum's nicira plugin handles configuration of clusters and that has proven fairly easy to work with.</span><br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 14, 2013 at 12:41 PM, Chris Behrens <span dir="ltr"><<a href="mailto:cbehrens@codestud.com" target="_blank">cbehrens@codestud.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"><br>
On Jun 13, 2013, at 11:26 PM, Mark McLoughlin <<a href="mailto:markmc@redhat.com">markmc@redhat.com</a>> wrote:<br>
<br>
> Is there any reason not to just put it in nova.conf as transport URLs?<br>
><br>
> (By nova.conf, I mean cfg.CONF for nova which means you could happily do<br>
> e.g. --config-file nova-cells.conf too)<br>
<br>
</div>The issue with using cfg.CONF is that we need the same config options for each cell. So, I guess you'd have to dynamically create the config groups with cell name as the group name… and have some sort of global option or an option in a different config group that specifies the list of cells. I think it just gets kinda nasty. But let me know if I'm missing a good way to do it. It seems like JSON is going to be a little more flexible. :)<br>
<span class="HOEnZb"><font color="#888888"><br>
- Chris<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></div></div></div></body></html>