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


galera-platform (5) Versions 3.0.0

Install and configure a Galera Cluster

cookbook 'galera-platform', '= 3.0.0', :supermarket
cookbook 'galera-platform', '= 3.0.0'
knife supermarket install galera-platform
knife supermarket download galera-platform
Quality 50%

Galera Platform


Galera is a true multi-masters database based on synchronous replication. It is
now an official mode of MariaDB.

This cookbook is designed to install and configure a Galera Cluster using
MariaDB. It can also be used to install a standard MariaDB environment.


Cookbooks and gems

Declared in [metadata.rb](metadata.rb) and in [Gemfile](Gemfile).


A systemd managed distribution:
- RHEL Family 7, tested on Centos


First Setup

The recommended way to use this cookbook is through the creation of a role
per galera cluster. This enables the search by role feature, allowing a
simple service discovery.

In fact, there are two ways to configure the search:
1. with a static configuration through a list of hostnames (attributes hosts
that is ['galera-platform']['hosts'])
2. with a real search, performed on a role (attributes role and size
like in ['galera-platform']['role']). The role should be in the run-list
of all nodes of the cluster. The size is a safety and should be the number
of nodes in the cluster.

If hosts is configured, role and size are ignored

See [roles](test/integration/roles) for some examples and
[Cluster Search][cluster-search] documentation for more information.


This cookbook is fully tested through the installation of the full platform
in docker hosts. This uses kitchen, docker and some monkey-patching.

If you run kitchen list, you will see 4 suites:

  • galera-platform-1-centos-7
  • galera-platform-2-centos-7
  • galera-platform-3-centos-7

Each corresponds to a different node in the cluster. They are connected through
a bridge network named kitchen, which is created if necessary.

For more information, see [.kitchen.yml](.kitchen.yml) and [test](test)

Local cluster

The cluster installed with kitchen converge is fully working and can thus be
used as a local cluster for developments tests.

You can access it by using internal DNS of the docker network named kitchen
or by declaring each node in your hosts file. You can get each IP by

docker inspect --format \
  '{{}}' container_name


Configuration is done by overriding default attributes. All configuration keys
have a default defined in [attributes/default.rb](attributes/default.rb).
Please read it to have a comprehensive view of what and how you can configure
this cookbook behavior.



Include other recipes, that is:

  1. repository
  2. package
  3. config
  4. service


Configure YUM repositories.


Install MariaDB and MariaDB-backup.


Configure MariaDB in Galera mode, searching for other cluster members if
available. By default, cluster bootstrap is done by mariabackup which is
provided by MariaDB.


Enable and start services.




Available in [](


Please read carefully []( before making a merge

License and Author

Copyright (c) 2016 Sam4Mobile, 2018

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

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

cluster-search >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.




  • feat: allow generic config, remove percona support
    • allow other configuration sections than 'galera' to be configurable
    • move 'datadir' in 'mysqld' to fix sync/startup in latest version
    • replace xtrabackup by mariabackup (which is better supported by mariadb) and remove percona support
  • chore: handover maintenance to
  • fix: do not set retries if package_retries is nil (Chef 13)
  • refactor: remove templates


  • test: run tests on all nodes
  • test: use kitchen_command.rb from test-cookbook
  • test: include .gitlab-ci.yml from test-cookbook
  • test: move driver config, set build_pull and replace require_chef_omnibus


  • chore: set new contributing guide with karma style
  • chore: add foodcritic & rubocop in Gemfile
  • style: use cookbook_name macro everywhere
  • style(rubocop): fix heredoc & misc offenses
  • doc: update README on new sync mode



  • Support mariadb 10.2 and do not support older version
  • Add auto-restart option: restart if config changes (false by default)


  • Set docker seccomp policy to undefined
  • Use template 20160914 of .gitlab-ci.yml


  • Initial version for RHEL Family 7 (tested on Centos 7) supporting MariaDB by default (should be able to support MySQL too).

Collaborator Number Metric

3.0.0 passed this metric

Contributing File Metric

3.0.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Foodcritic Metric

3.0.0 passed this metric

No Binaries Metric

3.0.0 passed this metric

Testing File Metric

3.0.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Version Tag Metric

3.0.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must include a tag that matches this cookbook version number