MySQL Puppet Module / Manifests + Types & Providers
Ruby Puppet HTML
Latest commit a19d600 Aug 29, 2016 @eputnam eputnam committed on GitHub Merge pull request #879 from puppetlabs/modulesync
Update modulesync_config [a3fe424]
Permalink
Failed to load latest commit information.
examples Fix lint warnings and ensure lint fails on warnings Feb 12, 2015
lib Add limit to mysql server ID generated value Aug 10, 2016
manifests Fix syntax issue Jul 20, 2016
spec Update modulesync_config [a3fe424] Aug 26, 2016
templates Merge pull request #856 from cfasnacht/ticket/6404-new_maxallowedpack… Jun 22, 2016
.fixtures.yml (maint) Switches nanliu-staging dependency to puppet-staging May 25, 2016
.geppetto-rc.json Update for using Geppetto plugin in CI Dec 2, 2014
.gitattributes (FM-4046) Update to current msync configs [006831f] Feb 16, 2016
.gitignore (MAINT) Update for modulesync_config 72d19f184 Jul 27, 2016
.nodeset.yml Add rspec-system / serverspec tests Jul 5, 2013
.rspec (FM-4049) Update to current msync configs [2c99161] Jan 27, 2016
.rubocop.yml Update modulesync_config [a3fe424] Aug 26, 2016
.sync.yml (FM-4049) Update to current msync configs [2c99161] Jan 27, 2016
.travis.yml Update modulesync_config [a3fe424] Aug 26, 2016
CHANGELOG.md Release prep for 3.8.0 May 26, 2016
CONTRIBUTING.md {maint} modulesync 0794b2c Jun 30, 2016
Gemfile Update modulesync_config [a3fe424] Aug 26, 2016
LICENSE (FM-4046) Update to current msync configs [006831f] Feb 16, 2016
NOTICE (FM-4046) Update to current msync configs [006831f] Feb 16, 2016
README.md Merge pull request #857 from aerostitch/add_mariadb_ex_doc Jun 28, 2016
Rakefile Update modulesync_config [a3fe424] Aug 26, 2016
TODO added some additional TODOS Jun 3, 2011
metadata.json Support for puppet/staging 2.0.0 Jun 17, 2016

README.md

mysql

Table of Contents

  1. Module Description - What the module does and why it is useful
  2. Setup - The basics of getting started with mysql
  3. Usage - Configuration options and additional functionality
  4. Reference - An under-the-hood peek at what the module is doing and how
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module

Module Description

The mysql module installs, configures, and manages the MySQL service.

This module manages both the installation and configuration of MySQL, as well as extending Puppet to allow management of MySQL resources, such as databases, users, and grants.

Setup

Beginning with mysql

To install a server with the default options:

include '::mysql::server'.

To customize options, such as the root password or /etc/my.cnf settings, you must also pass in an override hash:

class { '::mysql::server':
  root_password           => 'strongpassword',
  remove_default_accounts => true,
  override_options        => $override_options
}

See Customize Server Options below for examples of the hash structure for $override_options`.

Usage

All interaction for the server is done via mysql::server. To install the client, use mysql::client. To install bindings, use mysql::bindings.

Customize server options

To define server options, structure a hash structure of overrides in mysql::server. This hash resembles a hash in the my.cnf file:

$override_options = {
  'section' => {
    'item' => 'thing',
  }
}

For options that you would traditionally represent in this format:

[section]
thing = X

...you can make an entry like thing => true, thing => value, or thing => " in the hash. Alternatively, you can pass an array, as thing => ['value', 'value2'], or list each thing => value separately on separate lines.

You can pass a variable in the hash without setting a value for it; the variable would then use MySQL's default settings. To exclude an option from the my.cnf file --- for example, when using override_options to revert to a default value --- pass thing => undef.

If an option needs multiple instances, pass an array. For example,

$override_options = {
  'mysqld' => {
    'replicate-do-db' => ['base1', 'base2'],
  }
}

produces

[mysqld]
replicate-do-db = base1
replicate-do-db = base2

To implement version specific parameters, specify the version, such as [mysqld-5.5]. This allows one config for different versions of MySQL.

Create a database

To create a database with a user and some assigned privileges:

mysql::db { 'mydb':
  user     => 'myuser',
  password => 'mypass',
  host     => 'localhost',
  grant    => ['SELECT', 'UPDATE'],
}

To use a different resource name with exported resources:

 @@mysql::db { "mydb_${fqdn}":
  user     => 'myuser',
  password => 'mypass',
  dbname   => 'mydb',
  host     => ${fqdn},
  grant    => ['SELECT', 'UPDATE'],
  tag      => $domain,
}

Then you can collect it on the remote DB server:

Mysql::Db <<| tag == $domain |>>

If you set the sql parameter to a file when creating a database, the file is imported into the new database.

For large sql files, increase the import_timeout parameter, which defaults to 300 seconds.

mysql::db { 'mydb':
  user     => 'myuser',
  password => 'mypass',
  host     => 'localhost',
  grant    => ['SELECT', 'UPDATE'],
  sql      => '/path/to/sqlfile',
  import_timeout => 900,
}

Customize configuration

To add custom MySQL configuration, place additional files into includedir. This allows you to override settings or add additional ones, which is helpful if you don't use override_options in mysql::server. The includedir location is by default set to /etc/mysql/conf.d.

Work with an existing server

To instantiate databases and users on an existing MySQL server, you need a .my.cnf file in root's home directory. This file must specify the remote server address and credentials. For example:

[client]
user=root
host=localhost
password=secret

This module uses the mysqld_version fact to discover the server version being used. By default, this is set to the output of mysqld -V. If you're working with a remote MySQL server, you may need to set a custom fact for mysqld_version to ensure correct behaviour.

When working with a remote server, do not use the mysql::server class in your Puppet manifests.

Specify passwords

In addition to passing passwords as plain text, you can input them as hashes. For example:

mysql::db { 'mydb':
  user     => 'myuser',
  password => '*6C8989366EAF75BB670AD8EA7A7FC1176A95CEF4',
  host     => 'localhost',
  grant    => ['SELECT', 'UPDATE'],
}

Install Percona server on CentOS

This example shows how to do a minimal installation of a Percona server on a CentOS system. This sets up the Percona server, client, and bindings (including Perl and Python bindings). You can customize this usage and update the version as needed.

This usage has been tested on Puppet 4.4 / CentOS 7 / Percona Server 5.7.

Note: The installation of the yum repository is not part of this package and is here only to show a full example of how you can install.

yumrepo { 'percona':
  descr    => 'CentOS $releasever - Percona',
  baseurl  => 'http://repo.percona.com/centos/$releasever/os/$basearch/',
  gpgkey   => 'http://www.percona.com/downloads/percona-release/RPM-GPG-KEY-percona',
  enabled  => 1,
  gpgcheck => 1,
}

class {'mysql::server':
  package_name     => 'Percona-Server-server-57',
  package_ensure   => '5.7.11-4.1.el7',
  service_name     => 'mysql',
  config_file      => '/etc/my.cnf',
  includedir       => '/etc/my.cnf.d',
  root_password    => 'PutYourOwnPwdHere',
  override_options => {
    mysqld => {
      log-error => '/var/log/mysqld.log',
      pid-file  => '/var/run/mysqld/mysqld.pid',
    },
    mysqld_safe => {
      log-error => '/var/log/mysqld.log',
    },
  }
}

# Note: Installing Percona-Server-server-57 also installs Percona-Server-client-57.
# This shows how to install the Percona MySQL client on its own
class {'mysql::client':
  package_name   => 'Percona-Server-client-57',
  package_ensure => '5.7.11-4.1.el7',
}

# These packages are normally installed along with Percona-Server-server-57
# If you needed to install the bindings, however, you could do so with this code
class { 'mysql::bindings':
  client_dev_package_name   => 'Percona-Server-shared-57',
  client_dev_package_ensure => '5.7.11-4.1.el7',
  client_dev                => true,
  daemon_dev_package_name   => 'Percona-Server-devel-57',
  daemon_dev_package_ensure => '5.7.11-4.1.el7',
  daemon_dev                => true,
  perl_enable               => true,
  perl_package_name         => 'perl-DBD-MySQL',
  python_enable             => true,
  python_package_name       => 'MySQL-python',
}

# Dependencies definition
Yumrepo['percona']->
Class['mysql::server']

Yumrepo['percona']->
Class['mysql::client']

Yumrepo['percona']->
Class['mysql::bindings']

Install MariaDB on Ubuntu

Preliminary step: Install the MariaDB official repo (optionnal)

In this example, we want the latest stable (currently 10.1) from the official MariaDB repository, not the one from the distro repository. Note that this part is totally optionnal. You can also use the package from the Ubuntu repository.

Note: sfo1.mirrors.digitalocean.com is just one of the many mirrors available. You can use any other official mirror for better performance.

Important: this example is using a MariaDB 10.1 repository. Make sure you are using the repository corresponding to the version you want.

include apt

apt::source { 'mariadb':
  location => 'http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu',
  release  => $::lsbdistcodename,
  repos    => 'main',
  key      => { 
    id     => '199369E5404BD5FC7D2FE43BCBCB082A1BB943DB',
    server => 'hkp://keyserver.ubuntu.com:80',
  },
  include => {
    src   => false,
    deb   => true,
  },
}

Installing the MariaDB server

This part of the example shows how to install a MariaDB server on Ubuntu (trusty here). You will probably want to tweak the version and the parameters of the my.cnf.

As a reminder, all the parameters of the my.cnf can be defined using the override_options parmeter.

Of course, you need to make sure that all the custom folders you are setting your files into do exist as prerequisites of this code! :) Note that /var/log/mysql and /var/run/mysqld are created automatically.

All the values set here are an example of a working minimal configuration. You can tweak them all! ;)

Note: it is not mandatory to specify the version of the package you want (using the package_ensure parameter) but it's always a good practice to do so as it avoids some surprises...

class {'::mysql::server':
  package_name     => 'mariadb-server',
  package_ensure   => '10.1.14+maria-1~trusty',
  service_name     => 'mysql',
  root_password    => 'AVeryStrongPasswordUShouldEncrypt!',
  override_options => {
    mysqld => {
      'log-error' => '/var/log/mysql/mariadb.log',
      'pid-file'  => '/var/run/mysqld/mysqld.pid',
    },
    mysqld_safe => {
      'log-error' => '/var/log/mysql/mariadb.log',
    },
  }
}

# Dependency management. Only use that part if you are installing the repository
# as shown in the Preliminary step of this example.
Apt::Source['mariadb'] ~>
Class['apt::update'] ->
Class['::mysql::server']

Installing the MariaDB client (can be done separately)

This part of the example shows how to install the MariaDB client and use the bindings_enable to get all the bindings installed in 1 shot.

This part can be used totally individually from the server installation part.

Note: it is not mandatory to specify the version of the package you want (using the package_ensure parameter) but it's always a good practice to do so as it avoids some surprises...

class {'::mysql::client':
  package_name    => 'mariadb-client',
  package_ensure  => '10.1.14+maria-1~trusty',
  bindings_enable => true,
}

# Dependency management. Only use that part if you are installing the repository
# as shown in the Preliminary step of this example.
Apt::Source['mariadb'] ~>
Class['apt::update'] ->
Class['::mysql::client']

Reference

Classes

Public classes

Private classes

  • mysql::server::install: Installs packages.
  • mysql::server::installdb: Implements setup of mysqld data directory (e.g. /var/lib/mysql)
  • mysql::server::config: Configures MYSQL.
  • mysql::server::service: Manages service.
  • mysql::server::account_security: Deletes default MySQL accounts.
  • mysql::server::root_password: Sets MySQL root password.
  • mysql::server::providers: Creates users, grants, and databases.
  • mysql::bindings::client_dev: Installs MySQL client development package.
  • mysql::bindings::daemon_dev: Installs MySQL daemon development package.
  • mysql::bindings::java: Installs Java bindings.
  • mysql::bindings::perl: Installs Perl bindings.
  • mysql::bindings::php: Installs PHP bindings.
  • mysql::bindings::python: Installs Python bindings.
  • mysql::bindings::ruby: Installs Ruby bindings.
  • mysql::client::install: Installs MySQL client.
  • mysql::backup::mysqldump: Implements mysqldump backups.
  • mysql::backup::mysqlbackup: Implements backups with Oracle MySQL Enterprise Backup.
  • mysql::backup::xtrabackup: Implements backups with XtraBackup from Percona.

Parameters

mysql::server

create_root_user

Whether root user should be created. Valid values are true, false. Defaults to true.

This is useful for a cluster setup with Galera. The root user has to be created only once. You can set this parameter true on one node and set it to false on the remaining nodes.

create_root_my_cnf

Whether to create /root/.my.cnf. Valid values are true, false. Defaults to true.

create_root_my_cnf allows creation of /root/.my.cnf independently of create_root_user. You can use this for a cluster setup with Galera where you want /root/.my.cnf to exist on all nodes.

root_password

The MySQL root password. Puppet attempts to set the root password and update /root/.my.cnf with it.

This is required if create_root_user or create_root_my_cnf are true. If root_password is 'UNSET', then create_root_user and create_root_my_cnf are assumed to be false --- that is, the MySQL root user and /root/.my.cnf are not created.

Password changes are supported; however, the old password must be set in /root/.my.cnf. Effectively, Puppet uses the old password, configured in /root/my.cnf, to set the new password in MySQL, and then updates /root/.my.cnf with the new password.

old_root_password

This parameter no longer does anything. It exists only for backwards compatibility. See the root_password parameter above for details on changing the root password.

override_options

Specifies override options to pass into MySQL. Structured like a hash in the my.cnf file:

$override_options = {
  'section' => {
    'item'             => 'thing',
  }
}

See Customize Server Options above for usage details.

config_file

The location, as a path, of the MySQL configuration file.

manage_config_file

Whether the MySQL configuration file should be managed. Valid values are true, false. Defaults to true.

includedir

The location, as a path, of !includedir for custom configuration overrides.

install_options

Passes install_options array to managed package resources. You must pass the appropriate options for the specified package manager.

purge_conf_dir

Whether the includedir directory should be purged. Valid values are true, false. Defaults to false.

restart

Whether the service should be restarted when things change. Valid values are true, false. Defaults to false.

root_group

The name of the group used for root. Can be a group name or a group ID. See more about the group file attribute.

mysql_group

The name of the group of the MySQL daemon user. Can be a group name or a group ID. See more about the group file attribute.

package_ensure

Whether the package exists or should be a specific version. Valid values are 'present', 'absent', or 'x.y.z'. Defaults to 'present'.

package_manage

Whether to manage the MySQL server package. Defaults to true.

package_name

The name of the MySQL server package to install.

remove_default_accounts

Specifies whether to automatically include mysql::server::account_security. Valid values are true, false. Defaults to false.

service_enabled

Specifies whether the service should be enabled. Valid values are true, false. Defaults to true.

service_manage

Specifies whether the service should be managed. Valid values are true, false. Defaults to true.

service_name

The name of the MySQL server service. Defaults are OS dependent, defined in params.pp.

service_provider

The provider to use to manage the service. For Ubuntu, defaults to 'upstart'; otherwise, default is undefined.

users

Optional hash of users to create, which are passed to mysql_user.

users => {
  'someuser@localhost' => {
    ensure                   => 'present',
    max_connections_per_hour => '0',
    max_queries_per_hour     => '0',
    max_updates_per_hour     => '0',
    max_user_connections     => '0',
    password_hash            => '*F3A2A51A9B0F2BE2468926B4132313728C250DBF',
  },
}
grants

Optional hash of grants, which are passed to mysql_grant.

grants => {
  'someuser@localhost/somedb.*' => {
    ensure     => 'present',
    options    => ['GRANT'],
    privileges => ['SELECT', 'INSERT', 'UPDATE', 'DELETE'],
    table      => 'somedb.*',
    user       => 'someuser@localhost',
  },
}
databases

Optional hash of databases to create, which are passed to mysql_database.

databases   => {
  'somedb'  => {
    ensure  => 'present',
    charset => 'utf8',
  },
}

mysql::server::backup

backupuser

MySQL user to create for backups.

backuppassword

MySQL user password for backups.

backupdir

Directory in which to store backups.

backupdirmode

Permissions applied to the backup directory. This parameter is passed directly to the file resource.

backupdirowner

Owner for the backup directory. This parameter is passed directly to the file resource.

backupdirgroup

Group owner for the backup directory. This parameter is passed directly to the file resource.

backupcompress

Whether backups should be compressed. Valid values are true, false. Defaults to true.

backuprotate

How many days to keep backups. Valid value is an integer. Defaults to '30'.

delete_before_dump

Whether to delete old .sql files before backing up. Setting to true deletes old files before backing up, while setting to false deletes them after backup. Valid values are true, false. Defaults to false.

backupdatabases

Specifies an array of databases to back up.

file_per_database

Whether a separate file be used per database. Valid values are true, false. Defaults to false.

include_routines

Whether or not to include routines for each database when doing a file_per_database backup. Defaults to false.

include_triggers

Whether or not to include triggers for each database when doing a file_per_database backup. Defaults to false.

ensure

Allows you to remove the backup scripts. Valid values are 'present', 'absent'. Defaults to 'present'.

execpath

Allows you to set a custom PATH should your MySQL installation be non-standard places. Defaults to /usr/bin:/usr/sbin:/bin:/sbin.

time

An array of two elements to set the backup time. Allows '23', '5' or '3', '45' for HH:MM times.

postscript

A script that is executed when the backup is finished. This could be used to (r)sync the backup to a central store. This script can be either a single line that is directly executed or a number of lines supplied as an array. It could also be one or more externally managed (executable) files.

prescript

A script that is executed before the backup begins.

provider

Sets the server backup implementation. Valid values are:

  • mysqldump: Implements backups with mysqldump. Backup type: Logical. This is the default value.
  • mysqlbackup: Implements backups with MySQL Enterprise Backup from Oracle. Backup type: Physical. To use this type of backup, you'll need the meb package, which is available in RPM and TAR formats from Oracle. For Ubuntu, you can use meb-deb to create a package from an official tarball.
  • xtrabackup: Implements backups with XtraBackup from Percona. Backup type: Physical.
maxallowedpacket

Define the maximum SQL statement size for the backup dump script. The default value is 1MB as this is the default Mysql Server value.

mysql::server::monitor

mysql_monitor_username

The username to create for MySQL monitoring.

mysql_monitor_password

The password to create for MySQL monitoring.

mysql_monitor_hostname

The hostname from which the monitoring user requests are allowed access.

mysql::server::mysqltuner

Note: If you're using this class on a non-network-connected system, you must download the mysqltuner.pl script and have it hosted somewhere accessible via http(s)://, puppet://, ftp://, or a fully qualified file path.

ensure

Ensures that the resource exists. Valid values are present, absent. Defaults to present.

version

The version to install from the major/MySQLTuner-perl github repository. Must be a valid tag. Defaults to 'v1.3.0'.

source

Specifies the source. If not specified, defaults to https://github.com/major/MySQLTuner-perl/raw/${version}/mysqltuner.pl

mysql::bindings

client_dev

Specifies whether ::mysql::bindings::client_dev should be included. Valid values are true', false. Defaults to false.

daemon_dev

Specifies whether ::mysql::bindings::daemon_dev should be included. Valid values are true, false. Defaults to false.

java_enable

Specifies whether ::mysql::bindings::java should be included. Valid values are true, false. Defaults to false.

perl_enable

Specifies whether mysql::bindings::perl should be included. Valid values are true, false. Defaults to false.

php_enable

Specifies whether mysql::bindings::php should be included. Valid values are true, false. Defaults to false.

python_enable

Specifies whether mysql::bindings::python should be included. Valid values are true, false. Defaults to false.

ruby_enable

Specifies whether mysql::bindings::ruby should be included. Valid values are true, false. Defaults to false.

install_options

Passes install_options array to managed package resources. You must pass the appropriate options for the package manager(s).

client_dev_package_ensure

Whether the package should be present, absent, or a specific version. Valid values are 'present', 'absent', or 'x.y.z'. Only applies if client_dev => true.

client_dev_package_name

The name of the client_dev package to install. Only applies if client_dev => true.

client_dev_package_provider

The provider to use to install the client_dev package. Only applies if client_dev => true.

daemon_dev_package_ensure

Whether the package should be present, absent, or a specific version. Valid values are 'present', 'absent', or 'x.y.z'. Only applies if daemon_dev => true.

daemon_dev_package_name

The name of the daemon_dev package to install. Only applies if daemon_dev => true.

daemon_dev_package_provider

The provider to use to install the daemon_dev package. Only applies if daemon_dev => true.

java_package_ensure

Whether the package should be present, absent, or a specific version. Valid values are 'present', 'absent', or 'x.y.z'. Only applies if java_enable => true.

java_package_name

The name of the Java package to install. Only applies if java_enable => true.

java_package_provider

The provider to use to install the Java package. Only applies if java_enable => true.

perl_package_ensure

Whether the package should be present, absent, or a specific version. Valid values are 'present', 'absent', or 'x.y.z'. Only applies if perl_enable => true.

perl_package_name

The name of the Perl package to install. Only applies if perl_enable => true.

perl_package_provider

The provider to use to install the Perl package. Only applies if perl_enable => true.

php_package_ensure

Whether the package should be present, absent, or a specific version. Valid values are 'present', 'absent', or 'x.y.z'. Only applies if php_enable => true.

php_package_name

The name of the PHP package to install. Only applies if php_enable => true.

python_package_ensure

Whether the package should be present, absent, or a specific version. Valid values are 'present', 'absent', or 'x.y.z'. Only applies if python_enable => true.

python_package_name

The name of the Python package to install. Only applies if python_enable => true.

python_package_provider

The provider to use to install the PHP package. Only applies if python_enable => true.

ruby_package_ensure

Whether the package should be present, absent, or a specific version. Valid values are 'present', 'absent', or 'x.y.z'. Only applies if ruby_enable => true.

ruby_package_name

The name of the Ruby package to install. Only applies if ruby_enable => true.

ruby_package_provider

What provider should be used to install the package.

mysql::client

bindings_enable

Whether to automatically install all bindings. Valid values are true, false. Default to false.

install_options

Array of install options for managed package resources. You must pass the appropriate options for the package manager.

package_ensure

Whether the MySQL package should be present, absent, or a specific version. Valid values are 'present', 'absent', or 'x.y.z'.

package_manage

Whether to manage the MySQL client package. Defaults to true.

package_name

The name of the MySQL client package to install.

Defines

mysql::db

mysql_database { 'information_schema':
  ensure  => 'present',
  charset => 'utf8',
  collate => 'utf8_swedish_ci',
}
mysql_database { 'mysql':
  ensure  => 'present',
  charset => 'latin1',
  collate => 'latin1_swedish_ci',
}
user

The user for the database you're creating.

password

The password for $user for the database you're creating.

dbname

The name of the database to create. Defaults to $name.

charset

The character set for the database. Defaults to 'utf8'.

collate

The collation for the database. Defaults to 'utf8_general_ci'.

host

The host to use as part of user@host for grants. Defaults to 'localhost'.

grant

The privileges to be granted for user@host on the database. Defaults to 'ALL'.

sql

The path to the sqlfile you want to execute. This can be single file specified as string, or it can be an array of strings. Defaults to undef.

enforce_sql

Specifies whether executing the sqlfiles should happen on every run. If set to false, sqlfiles only run once. Valid values are true, false. Defaults to false.

ensure

Specifies whether to create the database. Valid values are 'present', 'absent'. Defaults to 'present'.

import_timeout

Timeout, in seconds, for loading the sqlfiles. Defaults to '300'.

Types

mysql_database

mysql_database creates and manages databases within MySQL.

ensure

Whether the resource is present. Valid values are 'present', 'absent'. Defaults to 'present'.

name

The name of the MySQL database to manage.

charset

The CHARACTER SET setting for the database. Defaults to ':utf8'.

collate

The COLLATE setting for the database. Defaults to ':utf8_general_ci'.

mysql_user

Creates and manages user grants within MySQL.

mysql_user { 'root@127.0.0.1':
  ensure                   => 'present',
  max_connections_per_hour => '0',
  max_queries_per_hour     => '0',
  max_updates_per_hour     => '0',
  max_user_connections     => '0',
}

You can also specify an authentication plugin.

mysql_user{ 'myuser'@'localhost':
  ensure                   => 'present',
  plugin                   => 'unix_socket',
}
name

The name of the user, as 'username@hostname' or username@hostname.

password_hash

The user's password hash of the user. Use mysql_password() for creating such a hash.

max_user_connections

Maximum concurrent connections for the user. Must be an integer value. A value of '0' specifies no (or global) limit.

max_connections_per_hour

Maximum connections per hour for the user. Must be an integer value. A value of '0' specifies no (or global) limit.

max_queries_per_hour

Maximum queries per hour for the user. Must be an integer value. A value of '0' specifies no (or global) limit.

max_updates_per_hour

Maximum updates per hour for the user. Must be an integer value. A value of '0' specifies no (or global) limit.

mysql_grant

mysql_grant creates grant permissions to access databases within MySQL. To create grant permissions to access databases with MySQL, use it you must create the title of the resource as shown below, following the pattern of username@hostname/database.table:

mysql_grant { 'root@localhost/*.*':
  ensure     => 'present',
  options    => ['GRANT'],
  privileges => ['ALL'],
  table      => '*.*',
  user       => 'root@localhost',
}

It is possible to specify privileges down to the column level:

mysql_grant { 'root@localhost/mysql.user':
  ensure     => 'present',
  privileges => ['SELECT (Host, User)'],
  table      => 'mysql.user',
  user       => 'root@localhost',
}
ensure

Whether the resource is present. Valid values are 'present', 'absent'. Defaults to 'present'.

name

Name to describe the grant. Must in a 'user/table' format.

privileges

Privileges to grant the user.

table

The table to which privileges are applied.

user

User to whom privileges are granted.

options

MySQL options to grant. Optional.

mysql_plugin

mysql_plugin can be used to load plugins into the MySQL Server.

mysql_plugin { 'auth_socket':
  ensure     => 'present',
  soname     => 'auth_socket.so',
}
ensure

Whether the resource is present. Valid values are 'present', 'absent'. Defaults to 'present'.

name

The name of the MySQL plugin to manage.

soname

The library file name.

mysql_datadir

Initializes the MySQL data directory with version specific code. Pre MySQL 5.7.6 it uses mysql_install_db. After MySQL 5.7.6 it uses mysqld --initialize-insecure.

Insecure initialization is needed, as mysqld version 5.7 introduced "secure by default" mode. This means MySQL generates a random password and writes it to STDOUT. This means puppet can never accesss the database server afterwards, as no credencials are available.

This type is an internal type and should not be called directly.

Facts

mysql_version

Determines the MySQL version by parsing the output from mysql --version

mysql_server_id

Generates a unique id, based on the node's MAC address, which can be used as server_id. This fact will always return 0 on nodes that have only loopback interfaces. Because those nodes aren't connected to the outside world, this shouldn't cause any conflicts.

Limitations

This module has been tested on:

  • RedHat Enterprise Linux 5, 6, 7
  • Debian 6, 7, 8
  • CentOS 5, 6, 7
  • Ubuntu 10.04, 12.04, 14.04, 16.04
  • Scientific Linux 5, 6
  • SLES 11

Testing on other platforms has been minimal and cannot be guaranteed.

Note: The mysqlbackup.sh does not work and is not supported on MySQL 5.7 and greater.

Development

Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can't access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.

We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

Check out our the complete module contribution guide.

Authors

This module is based on work by David Schmitt. The following contributors have contributed to this module (beyond Puppet Labs):

  • Larry Ludwig
  • Christian G. Warden
  • Daniel Black
  • Justin Ellison
  • Lowe Schmidt
  • Matthias Pigulla
  • William Van Hevelingen
  • Michael Arnold
  • Chris Weyl
  • Daniël van Eeden