cookbook 'mysql', '~> 8.3.0', :supermarket
Provides mysql_service, mysql_config, and mysql_client resources
cookbook 'mysql', '~> 8.3.0'
knife cookbook site install mysql
knife cookbook site download mysql
The MySQL Cookbook is a library cookbook that provides resource primitives (LWRPs) for use in recipes. It is designed to be a reference example for creating highly reusable cross-platform cookbooks.
This cookbook is concerned with the "MySQL Community Server", particularly those shipped with F/OSS Unix and Linux distributions. It does not address forks or value-added repackaged MySQL distributions like MariaDB or Percona.
- Chef 12.5 or higher
- Network accessible package repositories
- 'recipe[selinux::disabled]' on RHEL platforms
The following platforms have been tested with Test Kitchen:
|----------------+-----+-----+-----+-----| | | 5.1 | 5.5 | 5.6 | 5.7 | |----------------+-----+-----+-----+-----| | debian-7 | | X | | | |----------------+-----+-----+-----+-----| | debian-8 | | X | | | |----------------+-----+-----+-----+-----| | ubuntu-14.04 | | X | X | | |----------------+-----+-----+-----+-----| | ubuntu-16.04 | | | | X | |----------------+-----+-----+-----+-----| | centos-6 | X | X | X | X | |----------------+-----+-----+-----+-----| | centos-7 | | X | X | X | |----------------+-----+-----+-----+-----| | fedora | | | X | X | |----------------+-----+-----+-----+-----| | openSUSE 13.2 | | | X | | |----------------+-----+-----+-----+-----| | openSUSE Leap | | | X | | |----------------+-----+-----+-----+-----|
There are no hard coupled dependencies. However, there is a loose dependency on
yum-mysql-community for RHEL/CentOS platforms. As of the 8.0 version of this cookbook, configuration of the package repos is now the responsibility of the user.
Place a dependency on the mysql cookbook in your cookbook's metadata.rb
depends 'mysql', '~> 8.0'
Then, in a recipe:
mysql_service 'foo' do port '3306' version '5.5' initial_root_password 'change me' action [:create, :start] end
The service name on the OS is
mysql-foo. You can manually start and stop it with
service mysql-foo start and
service mysql-foo stop.
The configuration file is at
/etc/mysql-foo/my.cnf. It contains the minimum options to get the service running. It looks like this.
# Chef generated my.cnf for instance mysql-foo [client] default-character-set = utf8 port = 3306 socket = /var/run/mysql-foo/mysqld.sock [mysql] default-character-set = utf8 [mysqld] user = mysql pid-file = /var/run/mysql-foo/mysqld.pid socket = /var/run/mysql-foo/mysqld.sock port = 3306 datadir = /var/lib/mysql-foo tmpdir = /tmp log-error = /var/log/mysql-foo/error.log !includedir /etc/mysql-foo/conf.d [mysqld_safe] socket = /var/run/mysql-foo/mysqld.sock
You can put extra configuration into the conf.d directory by using the
mysql_config resource, like this:
mysql_service 'foo' do port '3306' version '5.5' initial_root_password 'change me' action [:create, :start] end mysql_config 'foo' do source 'my_extra_settings.erb' notifies :restart, 'mysql_service[foo]' action :create end
You are responsible for providing
my_extra_settings.erb in your own cookbook's templates folder.
Connecting with the mysql CLI command
Logging into the machine and typing
mysql with no extra arguments will fail. You need to explicitly connect over the socket with
mysql -S /var/run/mysql-foo/mysqld.sock, or over the network with
mysql -h 127.0.0.1
Upgrading from older version of the mysql cookbook
- It is strongly recommended that you rebuild the machine from scratch. This is easy if you have your
data_diron a dedicated mount point. If you must upgrade in-place, follow the instructions below.
- The 6.x series supports multiple service instances on a single machine. It dynamically names the support directories and service names.
/etc/mysql becomes /etc/mysql-instance_name. Other support directories in
/runetc work the same way. Make sure to specify the
data_dirproperty on the
mysql_serviceresource to point to the old
mysql_service resource manages the basic plumbing needed to get a MySQL server instance running with minimal configuration.
:create action handles package installation, support directories, socket files, and other operating system level concerns. The internal configuration file contains just enough to get the service up and running, then loads extra configuration from a conf.d directory. Further configurations are managed with the
- If the
data_diris empty, a database will be initialized, and a
- root user will be set up with
initial_root_password. If this
- directory already contains database files, no action will be taken.
:start action starts the service on the machine using the appropriate provider for the platform. The
:start action should be omitted when used in recipes designed to build containers.
mysql_service 'default' do version '5.7' bind_address '0.0.0.0' port '3306' data_dir '/data' initial_root_password 'Ch4ng3me' action [:create, :start] end
Please note that when using
subscribes, the resource to reference is
charset- specifies the default character set. Defaults to
data_dir- determines where the actual data files are kept on the machine. This is useful when mounting external storage. When omitted, it will default to the platform's native location.
error_log- Tunable location of the error_log
initial_root_password- allows the user to specify the initial root password for mysql when initializing new databases. This can be set explicitly in a recipe, driven from a node attribute, or from data_bags. When omitted, it defaults to
ilikerandompasswords. Please be sure to change it.
instance- A string to identify the MySQL service. By convention, to allow for multiple instances of the
mysql_service, directories and files on disk are named
mysql-<instance_name>. Defaults to the resource name.
package_action- Defaults to
package_name- Defaults to a value looked up in an internal map.
package_version- Specific version of the package to install,passed onto the underlying package manager. Defaults to
bind_address- determines the listen IP address for the mysqld service. When omitted, it will be determined by MySQL. If the address is "regular" IPv4/IPv6address (e.g 127.0.0.1 or ::1), the server accepts TCP/IP connections only for that particular address. If the address is "0.0.0.0" (IPv4) or "::" (IPv6), the server accepts TCP/IP connections on all IPv4 or IPv6 interfaces.
mysqld_options- A key value hash of options to be rendered into the main my.cnf. WARNING - It is highly recommended that you use the
mysql_configresource instead of sending extra config into a
mysql_serviceresource. This will allow you to set up notifications and subscriptions between the service and its configuration. That being said, this can be useful for adding extra options needed for database initialization at first run.
port- determines the listen port for the mysqld service. When omitted, it will default to '3306'.
run_group- The name of the system group the
mysql_serviceshould run as. Defaults to 'mysql'.
run_user- The name of the system user the
mysql_serviceshould run as. Defaults to 'mysql'.
pid_file- Tunable location of the pid file.
socket- determines where to write the socket file for the
mysql_serviceinstance. Useful when configuring clients on the same machine to talk over socket and skip the networking stack. Defaults to a calculated value based on platform and instance name.
tmp_dir- Tunable location of the tmp_dir
version- allows the user to select from the versions available for the platform, where applicable. When omitted, it will install the default MySQL version for the target platform. Available version numbers are
5.7, depending on platform.
:create- Configures everything but the underlying operating system service.
:delete- Removes everything but the package and data_dir.
:start- Starts the underlying operating system service
:stop- Stops the underlying operating system service
:restart- Restarts the underlying operating system service
:reload- Reloads the underlying operating system service
Chef selects the appropriate provider based on platform and version, but you can specify one if your platform support it.
mysql_service[instance-1] do port '1234' data_dir '/mnt/lottadisk' provider Chef::Provider::MysqlServiceSysvinit action [:create, :start] end
Chef::Provider::MysqlServiceBase- Configures everything needed to run a MySQL service except the platform service facility. This provider should never be used directly. The
:reloadactions are stubs meant to be overridden by the providers below.
Chef::Provider::MysqlServiceSmf- Starts a
mysql_serviceusing the Service Management Facility, used by Solaris and Illumos. Manages the FMRI and method script.
Chef::Provider::MysqlServiceSystemd- Starts a
mysql_serviceusing SystemD. Manages the unit file and activation state
Chef::Provider::MysqlServiceSysvinit- Starts a
mysql_serviceusing SysVinit. Manages the init script and status.
Chef::Provider::MysqlServiceUpstart- Starts a
mysql_serviceusing Upstart. Manages job definitions and status.
mysql_config resource is a wrapper around the core Chef
template resource. Instead of a
path parameter, it uses the
instance parameter to calculate the path on the filesystem where file is rendered.
mysql_config[default] do source 'site.cnf.erb' action :create end
config_name- The base name of the configuration file to be rendered into the conf.d directory on disk. Defaults to the resource name.
cookbook- The name of the cookbook to look for the template source. Defaults to nil
group- System group for file ownership. Defaults to 'mysql'.
instance- Name of the
mysql_serviceinstance the config is meant for. Defaults to 'default'.
owner- System user for file ownership. Defaults to 'mysql'.
source- Template in cookbook to be rendered.
variables- Variables to be passed to the underlying
version- Version of the
mysql_serviceinstance the config is meant for. Used to calculate path. Only necessary when using packages with unique configuration paths, such as RHEL Software Collections or OmniOS. Defaults to 'nil'
:create- Renders the template to disk at a path calculated using the instance parameter.
:delete- Deletes the file from the conf.d directory calculated using the instance parameter.
mysql_service 'instance-1' do action [:create, :start] end mysql_service 'instance-2' do action [:create, :start] end mysql_config 'logging' do instance 'instance-1' source 'logging.cnf.erb' action :create notifies :restart, 'mysql_service[instance-1]' end mysql_config 'security settings for instance-2' do config_name 'security' instance 'instance-2' source 'security_stuff.cnf.erb' variables(:foo => 'bar') action :create notifies :restart, 'mysql_service[instance-2]' end
mysql_client resource manages the MySQL client binaries and development libraries.
It is an example of a "singleton" resource. Declaring two
mysql_client resources on a machine usually won't yield two separate copies of the client binaries, except for platforms that support multiple versions (RHEL SCL, OmniOS).
mysql_client 'default' do action :create end
package_name- An array of packages to be installed. Defaults to a value looked up in an internal map.
package_version- Specific versions of the package to install, passed onto the underlying package manager. Defaults to
version- Major MySQL version number of client packages. Only valid on for platforms that support multiple versions, such as RHEL via Software Collections and OmniOS.
:create- Installs the client software
:delete- Removes the client software
Advanced Usage Examples
There are a number of configuration scenarios supported by the use of resource primitives in recipes. For example, you might want to run multiple MySQL services, as different users, and mount block devices that contain pre-existing databases.
Multiple Instances as Different Users
# instance-1 user 'alice' do action :create end directory '/mnt/data/mysql/instance-1' do owner 'alice' action :create end mount '/mnt/data/mysql/instance-1' do device '/dev/sdb1' fstype 'ext4' action [:mount, :enable] end mysql_service 'instance-1' do port '3307' run_user 'alice' data_dir '/mnt/data/mysql/instance-1' action [:create, :start] end mysql_config 'site config for instance-1' do instance 'instance-1' source 'instance-1.cnf.erb' notifies :restart, 'mysql_service[instance-1]' end # instance-2 user 'bob' do action :create end directory '/mnt/data/mysql/instance-2' do owner 'bob' action :create end mount '/mnt/data/mysql/instance-2' do device '/dev/sdc1' fstype 'ext3' action [:mount, :enable] end mysql_service 'instance-2' do port '3308' run_user 'bob' data_dir '/mnt/data/mysql/instance-2' action [:create, :start] end mysql_config 'site config for instance-2' do instance 'instance-2' source 'instance-2.cnf.erb' notifies :restart, 'mysql_service[instance-2]' end
mysql_service instances to test a replication setup. This particular example serves as a smoke test in Test Kitchen because it exercises different resources and requires service restarts.
Frequently Asked Questions
How do I run this behind my firewall?
On Linux, the
mysql_service resource uses the platform's underlying package manager to install software. For this to work behind firewalls, you'll need to either:
- Configure the system yum/apt utilities to use a proxy server that
- can reach the Internet
- Host a package repository on a network that the machine can talk to
On the RHEL platform_family, applying the
yum::default recipe will allow you to drive the
yum_globalconfig resource with attributes to change the global yum proxy settings.
If hosting repository mirrors, applying one of the following recipes and adjust the settings with node attributes.
recipe[yum-centos::default]from the Supermarket
recipe[yum-mysql-community::default]from the Supermarket
The mysql command line doesn't work
If you log into the machine and type
mysql, you may see an error like this one:
Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'
This is because MySQL is hardcoded to read the defined default my.cnf file, typically at /etc/my.cnf, and this LWRP deletes it to prevent overlap among multiple MySQL configurations.
To connect to the socket from the command line, check the socket in the relevant my.cnf file and use something like this:
mysql -S /var/run/mysql-foo/mysqld.sock -Pwhatever
Or to connect over the network, use something like this: connect over the network..
mysql -h 127.0.0.1 -Pwhatever
These network or socket ssettings can also be put in you $HOME/.my.cnf, if preferred.
What about MariaDB, Percona, etc.
MySQL forks are purposefully out of scope for this cookbook. This is mostly to reduce the testing matrix to a manageable size. Cookbooks for these technologies can easily be created by copying and adapting this cookbook. However, there will be differences.
Package repository locations, package version names, software major version numbers, supported platform matrices, and the availability of software such as XtraDB and Galera are the main reasons that creating multiple cookbooks to make sense.
Copyright:: 2009-2017 Chef Software, Inc Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
This cookbook has no specified dependencies.
mysql Cookbook CHANGELOG
This file is used to list changes made in each version of the mysql cookbook.
- Refactor mysql_service_manager_upstart.rb to eliminate use of cloned resource
- Include client development packages on RHEL/SUSE platforms
- Fixing CVE-2016-6662 - Reverting execure bit on mysql config
- Drop hardcoded, specific package version logic that broke many users
- Bump debian version
- Updated packages for 12.04 and 14.04 too
- Add chef_version metadata
- Update platforms in the kitchen file
- Add selinux to the Berksfile for testing
- Make sure yum repos are setup in local Test Kitchen
- [GH-390] Fix #390 incorrect escaping of initial_root_password
- Updated package versions for Ubuntu 16.04
- Testing updates
- Various bug fixed and updates to package version strings
- Fixed a regression in the mysql_client resource where the action was changed from create to install in the 8.0 release
- Added oracle, opensuse, and opensuseleap as supported platforms in the metadata
- Converting from LWRP to custom resources
- Removing yum-mysql and other dependencies.
- ^ BREAKING CHANGE: RHELish users are now responsible for including a recipe from the "yum-mysql" or equivalent cookbook before utilizing the mysql_* resources.
- More thoughtful ChefSpec
- Renaming "replication" test suite to "smoke"
- Moving to Inspec
- Support openeSUSE leap
- Support Fedora 24
- Avoid deprecation warnings on the upcoming Chef 12.12 release
- Fix apparmor blocking writes to non-default tmp_dirs
- Updated apparmor config to allow read & write to sock.lock file
- Use cookstyle instead of Rubocop directly
- Added support for Ubuntu 16.04
- Removed support for legacy distros: Ubuntu 10.04/13.04/14.10/15.04, Fedora 20/21, OmniOS r151006, opensuse 11.3/12.0
- Added support for Fedora 23, suse 13.X, and Ubuntu 16.04
- Updated the systemd support to create unit files in /etc/systemd and not /usr/lib/systemd
- Adding umask to bash resource that sets root password PR #386 @gziskind
- Cleaned up the Test Kitchen config to test the right platform version + mysql pairings
- Added Travis CI Test Kitchen testing on Fedora 22/23 and removed Fedora 21
- Updated the platforms used in the specs
- Added support for Ubuntu 15.10
- Added support for Amazon Linux 2016-03
- Updated Kitchen testing configs
- Added support for Amazon Linux 2015.09
- Completing ChefSpec matchers
- Adding tunables for tmp_dir, error_log, and pid_file
- Adding mysqld_options hash interface for main my.cnf template
- Reverting create_stop_system_service checks
- Ubuntu 15.04 support
- Check for scripts and unit files during create_stop_system_service
- Patch to allow blank root password
- Adding package information for Suse 12.0
- Fixes for 12.4.x
- Allowing integer value for port number
- Reverting breaking changes introduced in 6.0.25
- Fixes for 12.4.1
- 341 - Changing default GRANT for root from '%' to 'localhost' and '127.0.0.1'
- 354 Better handling of long MySQL startup times
- Debian 8 (Jessie) support
- Fix to Upstart prestart script when using custom socket
- Adding --explicit_defaults_for_timestamp mysql_install_db_cmd for
- 5.6 and above
- 318 - Fixing Upstart pre-start script to handle custom socket paths
- Adding support for Amazon Linux 2015.03
- Adding support for 5.6 and 5.7 packages from dotdeb repos on Debian 7
- Updated for MySQL 5.7.6.
- Handing removal of mysql_install_db and mysqld_safe
- Moved --defaults-file as first option to mysql_install_db_script
- Updating docker detection fix to pass specs
- Fixed debian system service :disable action. Now survives reboot
- Fixing centos-7 instance :enable action. Now survives
- Not applying Apparmor policy if running in a Docker container
- Adding support for special characters in initial_root_password
- Fixing failure status bug in sysvinit script
- No changes. Released a 6.0.11 that was identical to 6.0.10.
- Git before coffee.
- Adding support for configurable socket files
- Fix #282 - Fixing up data_dir template variable
- Fix #282 - undefined method `parsed_data_dir' bug
- Refactoring helper methods out of resource classes
- Fixing timing issue with Upstart provider :restart and :reload
- actions where service returns before being available
- Fixing subtle bug where MysqlCookbook::Helper methods were polluting Chef::Resource
- Using 'include_recipe' instead of 'recipe_eval' in LWRP
- Fixing type checking on package_name attribute in mysql_client resource.
- Suggest available versions if current is not available for current platform.
- Adding bind_address parameter to mysql_service resource
- Fixing sysvinit provider to survive reboots
- Fixing Upstart template to survive reboots
- Major version update
- Cookbook now provides LWRPs instead of recipes
- Platform providers re-factored into init system providers
- Separated :create and :start actions for use in recipes that build containers
- mysql_service now supports multiple instances on the same machine
- mysql_service no longer attempts to manage user records
- Removal of debian-sys-maint
- Unified Sysvinit script that works on all platforms
- mysql_config resource introduced
- mysql_client fixed up
- Refactored acceptance tests
- Temporarily dropped FreeBSD support
- Use Gem::Version instead of Chef::Version
- Changing default charset to utf8
- Quoting passwords in debian.cnf.erb
- Amazon 2014.09 support
- Ubuntu 14.10 support
- Only hide passwords from STDOUT via "sensitive true" in chef-client higher than 11.14
- Updating test harness
- Adding sensitive flag to execute resources to protect passwords from logs
- Reverting back to Upstart on Ubuntu 14.04
- Reverting commit that broke Debian pass_string
- Switching Ubuntu service provider to use SysVinit instead of Upstart
- Adding package version and action parameters to mysql_service resource
- Fixing Debian pass_string
- Changing module namespace to MysqlCookbook
- More refactoring. Moving helper function bits into resource parsed_parameters
- Moving provider local variables into definitions for RHEL provider
- Refactoring resources into the LWRP style with parsed parameters
- Moving provider local variables into definitions
- 212 - support for centos-7 (mysql55 and mysql56)
- Adding (untested) Debian-6 support
- Adding Suse support to metadata.rb
- Adding ability to change MySQL root password
- Added libmysqlclient-devel package to SuSE client provider
- Appeasing AppArmor
- Reducing duplication in client provider
- Fixing pid path location. Updating tests to include real RHEL
- Fixing specs for Amazon Linux server package names
- Fixing Amazon Linux support
- 189 - Fix server_repl_password description
- 191 - Adding support for server55 and server56 on el-6
- 193 - Fix syntax in mysql_service example
- 199 - Adding Suse support
PR #192 - recipes/server.rb should honor parameter node['mysql']['version']
- COOK-4394 - restore freebsd support
- [COOK-4653] - Missing mySQL 5.6 support for Ubuntu 14.04
- [COOK-4625] - Fix password resource parameter consumption on Debian and Ubuntu
- Fix up typos and version numbers in PLATFORMS.md
- Fix up specs from COOK-4613 changes
- [COOK-4613] - Fix permissions on mysql data_dir to allow global access to mysql.sock
- [COOK-4564] - Using positive tests for datadir move
- [COOK-4551] - power grants.sql from resource parameters
- [COOK-4554] - Support for Debian Sid
- [COOK-4565] Support for Ubuntu 14.04
- [COOK-4565] Adding Specs and TK platform
- Removing non-LTS 13.10 specs and TK platform
Adding Ubuntu 13.04 to Platforminfo
- [COOK-4548] - Add template[/etc/mysql/debian.cnf] to Ubuntu provider
- [COOK-4547] - Shellescape server_root_password
- [COOK-4519] - Fix error in run_dir for Ubuntu
- [COOK-4531] - Fix pid and run_dir for Debian
[COOK-4523] - Allow for both :restart and :reload
- [COOK-4519] - Updating specs to reflect pid file change on Ubuntu
- [COOK-4519] - Fix path to pid file on Ubuntu
- Moving server_deprecated into recipes directory
- Rewriting as a library cookbook
- Exposing mysql_service and mysql_client resources
- User now needs to supply configuration
- Moving attribute driven recipe to server-deprecated
- [COOK-4349] - Fix invalid platform check
- [COOK-4184] - Better handling of Ubuntu upstart service
- [COOK-2100] - Changing innodb_log_file_size tunable results in inability to start MySQL
- **[COOK-2966] - Address foodcritic failures'
- **[COOK-4182] - Template parse failure in /etc/init/mysql.conf (data_dir)'
- **[COOK-4198] - Added missing tunable'
- **[COOK-4206] - create firstname.lastname@example.org, as well as root@localhost'
- [COOK-3931] - MySQL Server Recipe Regression for Non-LTS Ubuntu Versions
- [COOK-3945] - MySQL cookbook fails on Ubuntu 13.04/13.10
- [COOK-3966] - mysql::server recipe can't find a template with debian 7.x
- [COOK-3985] - Missing /etc/mysql/debian.cnf template on mysql::_server_debian.rb recipe (mysql 4.0.4)
- [COOK-3974] - debian.cnf not updated
- [COOK-4001] - Pull request: Fixes for broken mysql::server on Debian
- [COOK-4071] - Mysql cookbook doesn't work on debian 7.2
Fixing style cops
- COOK-4068 - rework MySQL Windows recipe
- COOK-3801 - Add innodb_adaptive_flushing_method and innodb_adaptive_checkpoint
fixing metadata version error. locking to 3.0
Locking yum dependency to '< 3'
- [COOK-3943] Notifying service restart on grants update
[COOK-3952] - Adding 'recursive true' to directory resources
- Adding support for Amazon Linux in attributes/server_rhel.rb
- Fixing bug where unprivileged users cannot connect over a local socket. Adding integration test.
- Fixing bug in mysql_grants_cmd generation
- [COOK-3928] Heavily refactoring for readability. Moving platform implementation into separate recipes
- Moving integration tests from minitest to serverspec, removing "improper" tests
- Moving many attributes into the ['mysql']['server']['whatever'] namespace
- [COOK-3481] - Merged Lucas Welsh's Windows bits and moved into own recipe
- [COOK-3697] - Adding security hardening attributes
- [COOK-3780] - Fixing data_dir on Debian and Ubuntu
- [COOK-3807] - Don't use execute[assign-root-password] on Debian and Ubuntu
- [COOK-3881] - Fixing /etc being owned by mysql user
- COOK-3752 - mysql service fails to start in mysql::server recipe
- Fix a failed release attempt for v3.0.8
- COOK-3749 - Fix a regression with Chef 11-specific features
- COOK-3674 - Fix an issue where the MySQL server fails to set the root password correctly when
data_diris a non-default value
- COOK-3647 - Fix README typo (databas => database)
- COOK-3477 - Fix log-queries-not-using-indexes not working
- COOK-3436 - Pull percona repo in compilation phase
- COOK-3208 - Fix README typo (LitenPort => ListenPort)
- COOK-3149 - Create my.cnf before installing
- COOK-2681 - Fix log_slow_queries for 5.5+
- COOK-2606 - Use proper bind address on cloud providers
- COOK-3498 - Add support for replicate_* variables in my.cnf
- COOK-3310 - Fix missing
- COOK-3233 - Fix escaping special characters
- COOK-3156 - Fix GRANTS file when
- COOK-3134 - Fix Chef 11 support
- COOK-2318 - Remove redundant
- [COOK-2158]: apt-get update is run twice at compile time
- [COOK-2832]: mysql grants.sql file has errors depending on attrs
- [COOK-2995]: server.rb is missing a platform_family comparison value
innodb_flush_log_at_trx_commitvalue is incorrectly set based on CPU count
Note This is a backwards incompatible version with previous versions of the cookbook. Tickets that introduce incompatibility are COOK-2615 and COOK-2617.
- [COOK-2478] - Duplicate 'read_only' server attribute in base and tunable
- [COOK-2471] - Add tunable to set slave_compressed_protocol for reduced network traffic
- [COOK-1059] - Update attributes in mysql cookbook to support missing options for my.cnf usable by Percona
- [COOK-2590] - Typo in server recipe to do with conf_dir and confd_dir
- [COOK-2602] - Add
- [COOK-2430] - Add a tunable to create a network ACL when allowing
- [COOK-2619] - mysql: isamchk deprecated
- [COOK-2515] - Better support for SUSE distribution for mysql cookbook
- [COOK-2557] - mysql::percona_repo attributes missing and key server typo
- [COOK-2614] - Duplicate
- [COOK-2145] - MySQL cookbook should remove anonymous and password less accounts
- [COOK-2553] - Enable include directory in my.cnf template for any platform
- [COOK-2615] - Rename
- [COOK-2626] - Percona repo URL is being constructed incorrectly
- [COOK-2616] - Unneeded attribute thread_cache
- [COOK-2618] - myisam-recover not using attribute value
- [COOK-2617] - open-files is a duplicate of open-files-limit
- [COOK-2172] - Mysql cookbook duplicates
- [COOK-1669] - Using platform("ubuntu") in default attributes always returns true
- [COOK-1694] - Added additional my.cnf fields and reorganized cookbook to avoid race conditions with mysql startup and sql script execution
- [COOK-1851] - Support server-id and binlog_format settings
- [COOK-1929] - Update msyql server attributes file because setting attributes without specifying a precedence is deprecated
- [COOK-1999] - Add read_only tunable useful for replication slave servers
- [COOK-1967] - mysql: trailing comma in server.rb platform family
Important note for this release
Under Chef Solo, you must set the node attributes for the root, debian and repl passwords or the run will completely fail. See COOK-1737 for background on this.
- [COOK-1390] - MySQL service cannot start after reboot
- [COOK-1610] - Set root password outside preseed (blocker for drop-in mysql replacements)
- [COOK-1624] - Mysql cookbook fails to even compile on windows
- [COOK-1669] - Using platform("ubuntu") in default attributes always returns true
- [COOK-1686] - Add mysql service start
- [COOK-1687] - duplicate
- [COOK-1704] - mysql cookbook fails spec tests when minitest-handler cookbook enabled
- [COOK-1737] - Fail a chef-solo run when
server_repl_passwordis not set
- [COOK-1769] - link to database recipe in mysql README goes to old chef/cookbooks repo instead of chef-cookbook organization
- [COOK-1963] - use
Important note for this release
This version no longer installs Ruby bindings in the client recipe by default. Use the ruby recipe if you'd like the RubyGem. If you'd like packages from your distribution, use them in your application's specific cookbook/recipe, or modify the client packages attribute. This resolves the following tickets:
Additionally, this cookbook now has tests (COOK-1439) for use under test-kitchen.
The following issues are also addressed in this release.
- [COOK-1443] - MySQL (>= 5.1.24) does not support
- [COOK-1175] - Add Mac OS X support
- [COOK-1289] - handle additional tunable attributes
- [COOK-1305] - add auto-increment-increment and auto-increment-offset attributes
- [COOK-1397] - make the port an attribute
- [COOK-1439] - Add MySQL cookbook tests for test-kitchen support
- [COOK-1236] - Move package names into attributes to allow percona to free-ride
- [COOK-934] - remove deprecated mysql/libraries/database.rb, use the database cookbook instead.
- [COOK-1475] - fix restart on config change
- [COOK-1113] - Use an attribute to determine if upstart is used
- [COOK-1121] - Add support for Windows
- [COOK-1140] - Fix conf.d on Debian
- [COOK-1151] - Fix server_ec2 handling /var/lib/mysql bind mount
- [COOK-1321] - Document setting password attributes for solo
- [COOK-992] - fix FATAL nameerror
- [COOK-827] -
mysql:server_ec2recipe can't mount
- [COOK-945] - FreeBSD support
- [COOK-826] mysql::server recipe doesn't quote password string
- [COOK-834] Add 'scientific' and 'amazon' platforms to mysql cookbook
- [COOK-644] Mysql client cookbook 'package missing' error message is confusing
- [COOK-645] RHEL6/CentOS6 - mysql cookbook contains 'skip-federated' directive which is unsupported on MySQL 5.1
- [COOK-684] remove mysql_database LWRP
- [COOK-633] ensure "cloud" attribute is available
- [COOK-614] expose all mysql tunable settings in config
- [COOK-617] bind to private IP if available
- [COOK-605] install mysql-client package on ubuntu/debian
- [COOK-465] allow optional remote root connections to mysql
- [COOK-455] improve platform version handling
- externalize conf_dir attribute for easier cross platform support
- change datadir attribute to data_dir for consistency
- fix regressions on debian platform
- [COOK-578] wrap root password in quotes
- [COOK-562] expose all tunables in my.cnf
8.3.0 passed this metric
Collaborator Number Metric
8.3.0 passed this metric
8.3.0 passed this metric
8.3.0 passed this metric