[openstack-dev] "bad" default values in conf files

David Kranz dkranz at redhat.com
Thu Feb 13 14:38:52 UTC 2014


I was recently bitten by a case where some defaults in keystone.conf 
were not appropriate for real deployment, and our puppet modules were 
not providing better values 
https://bugzilla.redhat.com/show_bug.cgi?id=1064061. Since there are 
hundreds (thousands?) of options across all the services. I am wondering 
whether there are other similar issues lurking and if we have done what 
we can to flush them out.

Defaults in conf files seem to be one of the following:

- Generic, appropriate for most situations
- Appropriate for devstack
- Appropriate for small, distro-based deployment
- Approprate for large deployment

Upstream, I don't think there is a shared view of how defaults should be 
chosen.

Keeping bad defaults can have a huge impact on performance and when a 
system falls over but the problems may not be visible until some time 
after a system gets into real use. Have the folks creating our puppet 
modules and install recommendations taken a close look at all the 
options and determined
that the defaults are appropriate for deploying RHEL OSP in the 
configurations we are recommending?

  -David



More information about the OpenStack-dev mailing list