On 09/16/2015 04:25 PM, Duncan Thomas wrote: > On 16 Sep 2015 20:42, "yang, xing" <xing.y...@emc.com> wrote: > >> On 9/16/15, 1:20 PM, "Eric Harney" <ehar...@redhat.com> wrote: > >>> This sounds like a good idea, I'm just not sure how to structure it yet >>> without creating a very confusing set of config options. >> >> I’m thinking we could have a prefix with vendor name for this and it also >> requires documentation by driver maintainers if they are using a different >> config option. I proposed a topic to discuss about this at the summit. > > We already have per-backend config values in cinder.conf. I'm not sure how > the config code will need to be structured to achieve it, but ideally I'd > like a single config option that can be: > > (i) set in the default section if desired > (in) overridden in the per driver section, and (iii) have a default set in > each driver. > > I don't think oslo.config lets us do (I'll) yet though. >
I think there may be other issues to sort through to do that. Currently, at least some options set in [DEFAULT] don't apply to per-driver sections, and require you to set them in the driver section as well. If we keep that behavior (which I think is broken, personally), then trying to do option (iii) may be pretty confusing, because the deployer won't know which of the global vs. driver defaults are actually going to be applied. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
