Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


mariadb (81) Versions 0.2.11

Installs/Configures MariaDB

cookbook 'mariadb', '= 0.2.11', :supermarket
cookbook 'mariadb', '= 0.2.11'
knife supermarket install mariadb
knife supermarket download mariadb
Quality 0%

MariaDB Cookbook

Build Status


This cookbook contains all the stuffs to install and configure a mariadb server on a dpkg/apt compliant system (typically debian), or a rpm/yum compliant system (typically centos)



  • mariadb - This cookbook need that you have a valid apt repository installed with the mariadb official packages


  • percona-xtrabackup - if you want to use the xtrabckup SST Auth for galera cluster.
  • socat - if you want to use the xtrabckup SST Auth for galera cluster.
  • rsync - if you want to use the rsync SST Auth for galera cluster.
  • debconf-utils - if you use debian platform family.

operating system

  • debian - this cookbook is fully tested on debian
  • ubuntu - not fully tested on ubuntu, but should work
  • centos - not fully tested on centos, but should work



<td>Version to install (currently 10.0 et 5.5)</td>
<td>Wether to install MariaDB default repository or not. If you don't have a local repo containing packages, put it to true</td>
<td>local root password</td>
<td>Wether to activate root remote access</td>
<td>Wether to allow the recipe to change root password after the first install</td>
<td>Wether to install development files in client recipe</td>
<td>The http base url to use when installing from default repository</td>


To install a default server for mariadb choose the version you want (MariaDB 5.5 or 10, galera or not), then call the recipe accordingly.

List of availables recipes:

  • mariadb::default (just call server recipe with default options)
  • mariadb::server
  • mariadb::galera
  • mariadb::client

Please be ware that by default, the root password is empty! If you want have changed it use the node['mariadb']['server_root_password'] attribute to put a correct value. And by default the remote root access is not activated. Use node['mariadb']['forbid_remote_root'] attribute to change it.

Sometimes, the default apt repository used for apt does not work (see issue #6). In this case, you need to choose another mirror which worki (pick it from mariadb website), and put the http base url in the attribute node['mariadb']['apt_repository']['base_url'].


When installing the mariadb::galera on debian recipe, You have to take care of one specific attribute:
node['mariadb']['debian']['password'] which default to 'please-change-me'
As wee need to have the same password for this user on the whole cluster nodes... We will change the default install one by the content of this attribute.


By default this recipe install the client, and all needed packages to develop client application. If you do not want to install development files when installing client package,
set the attribute node['mariadb']['client']['development_files'] to false.


This recipe define 2 providers:
- Chef::Provider::Mariadb::Configuration shortcut resource mariadb_configuration
- Chef::Provider::Mariadb::Replication shortcut resource mariadb_replication


Mainly use for internal purpose. You can use it to create a new configuration file into configuration dir. You have to define 2 variables section and option.
Where section is the configuration section, and option is a hash of key/value. The name of the resource is used as base for the filename.

mariadb_configuration 'fake' do
section 'mysqld'
option {foo: 'bar'}

will become the file fake.cnf in the include dir (depend on your platform), which contain:


If the value start with a '#', then it's considered as a comment, and the value is printed as is (without the key)

mariadb_configuration 'fake' do
section 'mysqld'
option {comment1: '# Here i am', foo: bar}

will become the file fake.cnf in the include dir (depend on your platform), which contain:

Here i am



This LWRP is used to manage replication setup on a host. To use this LWRP, the node need to have the mysql binary installed (via the mariadb::client or mariadb::server or mariadb::galera recipe).
It have 4 actions:
- add - to add a new replication setup (become a slave)
- stop - to stop the slave replication
- start - to start the slave replication
- remove - to remove the slave replication configuration

The resource name need to be 'default' if your don't want to use a named connection (multi source replication in MariaDB 10).

So by default the provider try to use the local instance of mysql, with the current user and no password. If you want to change, you have to define host, port, user or password

mariadb_replication 'default' do
  user 'root'
  password 'fakepass'
  host 'fakehost'
  action :stop

will stop the replication on the host fakehost using the user root and password fakepass to connect to.

When you add a replication configuration, you have to define at least 4 values master_host, master_user, master_password and master_use_gtid. And if you don't want the GTID support, you have to define also master_log_file and master_log_pos

mariadb_replication 'usefull_conn_name' do
master_host 'server1'
master_user 'slave_user'
master_password 'slave_password'
master_use_gtid 'current_pos'
action :add


  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

License and Authors

Nicolas Blanc

Dependent cookbooks

apt >= 0.0.0
yum >= 0.0.0
yum-epel >= 0.0.0

Contingent cookbooks

abiquo Applicable Versions
database_application Applicable Versions
dvwa Applicable Versions
fivem Applicable Versions
kloudspeaker Applicable Versions
letsencrypt-boulder-server Applicable Versions
mysql2_chef_gem Applicable Versions
mysql_chef_gem Applicable Versions
openstack-common Applicable Versions
openstack-ops-database Applicable Versions
slurm Applicable Versions


This file is used to list changes made in each version of the mariadb cookbook.


  • [ENH #38] - Add CentOS support
  • [ENH #40] - Add sensitive flag to resource that deal with passwords
  • [BUG #43] - Fix convert TypeError in the replication provider


  • [BUG] - Audit Plugin test and installation - Correct bad notifies, and stdout test


  • [BUG #36] - Audit plugin installation can crash mariadb server


  • [BUG #30] - When using galera, nodes were not sorted, applying configuration change too often
  • [BUG #31] - ChefSpec coverage was not 100%
  • [BUG #28] - Remove the only_if to mysql service
  • [BUG #29] - Add a switch to not launch audit plugin install, when already installed
  • [ENH] - Add a switch to separate server install and audit install when needed
  • [ENH] - Add a rule to authorize line length to be 120 characters long


  • [BUG #24] - Fix convert TypeError in the replication provider
  • [BUG #25] - Data are now moved when default datadir is changed
  • [ENH #21] - Add audit_plugin management


  • [BUG #18] - Fix provider mariadb_replication compilation error
  • [DOCS] - Complete Changelog, and correct README


  • [ENH #16] - Add a LWRP to manage replication slave
  • [ENH #17] - Be able to not install development files within client recipe
  • [ENH #11] - Fix the galera root password preseed
  • [BUG #12] - Fix the debian-sys-maint user creation/password change
  • [BUG #6] - Can change the apt repository base_url when the default one fail
  • [TEST] - Add new tests for the new features (galera,development files install,replication LWRP)
  • [DOCS] - Complete Changelog, and add new features explanations into README


  • [BUG #10] - Correct a FC004 broken rule
  • [BUG #9] - Correct foodcritic tests (add --epic-fail any to be sure it fails when a broken rule is detected)


  • [BUG #4] - Add a real management of mysql root password
  • [ENH #5] - Now restart mysql service when port is changed
  • [ENH #7] - Remove or add root remote access via attribute
  • [DOCS] - Complete documentations
  • [TEST] - Add a lot of chefspec and kitchen/serverspec tests


  • [sinfomicien] - Correct repository install under debian family
  • [sinfomicien] - Correct client install to add dev files
  • [sinfomicien] - Correct and add multiples tests


  • [sinfomicien] - Use stove to package (remove PaxHeaders.*)


  • [sinfomicien] - Add rpm/yum management
  • [sinfomicien] - Refactor the whole recipes list and management to ease it
  • [sinfomicien] - Correct the Documentation
  • [sinfomicien] - Rename the provider (from extraconf to configuration), and add matchers to it
  • [sinfomicien] - Add a recipe to manage client only installation
  • [sinfomicien] - Refactor all tests to manage new platform (centos/redhat/fedora)


  • [sinfomicien] - Add ignore-failure to debian grants correct, as it can break on initial setup


  • [sinfomicien] - Correct a typo (unnecessary call to run_command)


  • [sinfomicien] - improve Galera configuration management
  • [sinfomicien] - Add new rspec tests
  • [sinfomicien] - Create Kitchen test suite


  • [sinfomicien] - improve attributes management


  • [sinfomicien] - adapt galera55 recipe to use a generic galera recipe
  • [sinfomicien] - use a generic galera recipe to create the galera10 recipe
  • [sinfomicien] - Improve documentation


  • [sinfomicien] - Initial release of mariadb

Foodcritic Metric

0.2.11 failed this metric

FC031: Cookbook without metadata file: /tmp/cook/6702cfb2ae5c4fa63898d165/mariadb/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/6702cfb2ae5c4fa63898d165/mariadb/metadata.rb:1