Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1688385

Summary: RFE: allow custom MySQL configs/tuning
Product: Red Hat OpenStack Reporter: Federico Iezzi <fiezzi>
Component: puppet-tripleoAssignee: Michele Baldessari <michele>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: low Docs Contact:
Priority: low    
Version: 13.0 (Queens)CC: abeekhof, abishop, afariasa, aschultz, chjones, dgurtner, emacchi, jjoyce, jschluet, mburns, michele, nchandek, pkomarov, sisadoun, slinaber, tvignaud
Target Milestone: z8Keywords: FutureFeature, Reopened, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-tripleo-8.4.1-21.el7ost Doc Type: Enhancement
Doc Text:
With this enhancement, you can pass arbitrary mysql config options to the mysql cluster on the overcloud with the `tripleo::profile::base::database::mysql::mysql_server_options` hiera hash key.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-03 16:55:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Federico Iezzi 2019-03-13 16:32:01 UTC 
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:
Comment 1 Alex Schultz 2019-03-13 21:09:16 UTC 
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
Comment 4 David Gurtner 2019-03-21 10:58:53 UTC 
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.
Comment 24 errata-xmlrpc 2019-09-03 16:55:32 UTC 
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