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. On Fri, Jun 14, 2013 at 12:41 PM, Chris Behrens <cbehrens at codestud.com>wrote: > > On Jun 13, 2013, at 11:26 PM, Mark McLoughlin <markmc at redhat.com> wrote: > > > Is there any reason not to just put it in nova.conf as transport URLs? > > > > (By nova.conf, I mean cfg.CONF for nova which means you could happily do > > e.g. --config-file nova-cells.conf too) > > 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. :) > > - Chris > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130614/33baaf9b/attachment.html>