Description of problem: Currently, there isn't any nice way to have a custom MySQL configuration. We should allow operators to apply MySQL DBA recommendations and basic MySQL tuning. For instance, the current tuning is fine for Dev and very small deployments. See innodb_buffer_pool_size at default of 128MB. Version-Release number of selected component (if applicable): Any OSP version How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I believe this is actually already available via hieradata. Technically innodb_buffer_pool_size is already managable via hieradata using 'innodb_buffer_pool_size'. For additional options something like... parameter_defaults: ControllerExtraConfig: tripleo::profile::base::database::mysql::mysql_server_options: mysql: open_files_limit: 1000 max_connections: 12
I'm reopening this. What Alex says is incorrect in my view: > I believe this is actually already available via hieradata. Technically > innodb_buffer_pool_size is already managable via hieradata using > 'innodb_buffer_pool_size'. For additional options something like... > > parameter_defaults: > ControllerExtraConfig: > tripleo::profile::base::database::mysql::mysql_server_options: > mysql: > open_files_limit: 1000 > max_connections: 12 tripleo::profile::base::database::mysql::mysql_server_options cannot be overwritten via Hiera. It is hardcoded in https://github.com/openstack/puppet-tripleo/blob/stable/queens/manifests/profile/pacemaker/database/mysql_bundle.pp#L285-L291 Explicit parameter assignment in Puppet takes precedence over hiera.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2624