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

RSS

mariadb (30) Versions 0.2.4

Installs/Configures MariaDB

Berkshelf/Librarian
Policyfile
Knife
cookbook 'mariadb', '= 0.2.4'
cookbook 'mariadb', '= 0.2.4', :supermarket
knife cookbook site install mariadb
knife cookbook site download mariadb
README
Dependencies
Changelog
Quality

MariaDB Cookbook

Build Status

Description

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)

Requirements

repository

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

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

Attributes

mariadb::default

<table> <tr> <th>Key</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> <tr> <td><tt>['mariadb']['install']['version']</tt></td> <td>String</td> <td>Version to install (currently 10.0 et 5.5)</td> <td><tt>10.0</tt></td> </tr> <tr> <td><tt>['mariadb']['use_default_repository']</tt></td> <td>Boolean</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><tt>false</tt></td> </tr> <tr> <td><tt>['mariadb']['server_root_password']</tt></td> <td>String</td> <td>local root password</td> <td><tt></tt></td> </tr> <tr> <td><tt>['mariadb']['forbid_remote_root']</tt></td> <td>Boolean</td> <td>Wether to activate root remote access</td> <td><tt>true</tt></td> </tr> <tr> <td><tt>['mariadb']['allow_root_pass_change']</tt></td> <td>Boolean</td> <td>Wether to allow the recipe to change root password after the first install</td> <td><tt>false</tt></td> </tr> </table>

Usage

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.

mariadb::galera

When installing the mariadb::galera on debian recipe, You have to take care of one specific attribute: default['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.

Contributing

  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

Authors: Nicolas Blanc sinfomicien@gmail.com

mariadb CHANGELOG

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

0.2.4

  • [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)

0.2.3

  • [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

0.2.2

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

0.2.1

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

0.2.0

  • [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)

0.1.8

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

0.1.7

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

0.1.6

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

0.1.5

  • [sinfomicien] - improve attributes management

0.1.4

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

0.1.0

  • [sinfomicien] - Initial release of mariadb

Foodcritic Metric
            

0.2.4 passed this metric