This module manages a MariaDB Galera cluster on Linux (RedHat/Debian) distros. A native mysql provider implements database resource type to handle database, database user, and database permission.

Pluginsync needs to be enabled for this module to function properly. Read more about pluginsync in our docs

NOTE: This is basically a copy of the PuppetLabs MySQL module, modified for use with MariaDB and supporting the galera cluster functions.

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

• Christian G. Warden
• Daniel Black
• Justin Ellison
• Lowe Schmidt
• Matthias Pigulla
• William Van Hevelingen
• Michael Arnold

Installs the mariadb-client package.

class { 'mariadb': }

Installs mariadb-server packages, configures my.cnf and starts mariadb service:

class { 'mariadb::server':
  config_hash => { 'root_password' => 'foo' }
}

Database login information stored in /root/.my.cnf.

Installs the mariadb and supporting galera packages for a cluster.

class { 'mariadb::cluster':
    cluster_servers => $mariadb_cluster_servers,
    config_hash     => {
      'root_password' => 'foo',
      'bind_address'  => '0.0.0.0',
      'restart'       => false,     # manually manage service with galera
    },
    build_stage     => 'peer'
}

Bootstrapping a cluster can be done using the build_stage parameter. The build_stage parameter can take three values: bootstrap, which configures the node with a bootstrap config, with the galera cluster address set to gcomm://; peer, which configures the cluster address to point to other nodes in the cluster (as specified by the cluster_servers paramter); and standalone, which configures the node without any clustering support.

The process for bootstrapping a cluster is as follows:

1. select a bootstrap node, set the build_stage value to bootstrap for this node, and run puppet to bring up the bootstrap mariadb instance

2. on the other nodes, set the build_stage value to peer and run puppet (puppet may need to be run a few times as the process of joining the cluster can take a little bit of time)

3. on the bootstrap node, set the build_stage value to peer and run puppet to finalise the cluster configuration

Note that the build_stage parameter defaults to 'standalone' - it must be set to a non-default value to enable clustering support.

Creates a local haproxy instance which can be used to connect to the cluster. In this mode clients connect to 127.0.0.1:3306 and haproxy forwards the connections through to one of the nodes, with the other nodes available as backups if the first node is unavailable. Note that the list of servers must be manually specified - it is not read from the mariadb::cluster::cluster_servers parameter.

By default a random node from the list of servers is selected as the primary. This can be overridden by specifying the primary directly.

By default haproxy uses the cluster status check service created by the mariadb::cluster::status module (typically by setting mariadb::cluster::manage_status to true). This can be modified using the check_state parameter.

Note that this can be used with a server in standalone mode, but some care needs to be taken when switching between standalone and clustered modes, as the standalone and clustered check scripts are incompatible.

This adds an optional dependency on puppetlabs/haproxy version 3.0.0 or greater.

Creates a database with a user and assign some privileges.

mariadb::db { 'mydb':
  user     => 'myuser',
  password => 'mypass',
  host     => 'localhost',
  grant    => ['all'],
}

Installs a mysql backup script, cronjob, and priviledged backup user.

class { 'mariadb::backup':
  backupuser     => 'myuser',
  backuppassword => 'mypassword',
  backupdir      => '/tmp/backups',
}

MySQL provider supports puppet resources command:

$ puppet resource database
database { 'information_schema':
  ensure  => 'present',
  charset => 'utf8',
}
database { 'mysql':
  ensure  => 'present',
  charset => 'latin1',
}

The custom resources can be used in any other manifests:

database { 'mydb':
  charset => 'latin1',
}

database_user { 'bob@localhost':
  password_hash => mysql_password('foo')
}

database_grant { 'user@localhost/database':
  privileges => ['all'] ,
  # Or specify individual privileges with columns from the mysql.db table:
  # privileges => ['Select_priv', 'Insert_priv', 'Update_priv', 'Delete_priv']
}

A resource default can be specified to handle dependency:

Database {
  require => Class['mariadb::server'],
}