On Mon, May 5, 2014 at 10:18 AM, Jay Pipes <[email protected]> wrote: > On 05/04/2014 01:13 PM, John Dickinson wrote: >> >> To add some color, Swift supports both single conf files and conf.d >> directory-based configs. See >> http://docs.openstack.org/developer/swift/deployment_guide.html#general-service-configuration. > > > +1 > > >> The "single config file" pattern is quite useful for simpler >> configurations, but the directory-based ones becomes especially useful when >> looking at cluster configuration management tools--stuff that auto-generates >> and composes config settings (ie non hand-curated configs). For example, the >> conf.d configs can support each middleware config or background daemon >> process in a separate file. Or server settings in one file and common >> logging settings in another. > > > Also +1 > > >> (Also, to answer before it's asked [but I don't want to derail the current >> thread], I'd be happy to look at oslo config parsing if it supports the same >> functionality.) > > > And a final +1. :)
oslo.config includes a --config-dir option for this. When "--config-dir dirname" is used with an app, oslo.config parses "dirname/*.conf" and adds the settings to the configuration being built. Doug > > -jay > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
